From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: florian.vaussard@epfl.ch, Benoit Cousson <b-cousson@ti.com>,
devicetree-discuss@lists.ozlabs.org,
Daniel Mack <zonque@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: OMAP3: Add GPMC controller
Date: Mon, 4 Feb 2013 09:32:52 -0800 [thread overview]
Message-ID: <20130204173252.GN22517@atomide.com> (raw)
In-Reply-To: <CABxcv==7KiBbkTyr7VLVw82F=9vVWRftpbyZWub_CVp3pQW0tQ@mail.gmail.com>
* Javier Martinez Canillas <javier@dowhile0.org> [130204 04:00]:
> On Mon, Feb 4, 2013 at 11:36 AM, Florian Vaussard
> > Great, the smsc911x was on my TODO list, I can cross it out :) BTW,
> > do you have a public git for this, so I can test your work on my setup?
> >
>
> Yes, it is the gpmc-smsc911x-wip branch on my github linux tree [1]
>
> That branch is Linus master tree + linux-omap/omap-for-v3.9/gpmc +
> linux-omap-dt/for_3.9/dts
>
> plus these patches:
>
> Javier Martinez Canillas (4):
> ARM: OMAP: gpmc-smsc911x: add DT dev node init function
> ARM: OMAP: gpmc: add support for gpmc-smsc911x child nodes
> ARM: dts: OMAP: Add an GPMC node for OMAP3
> ARM: dts: omap3-igep0020: Add SMSC911x LAN chip support
>
> You can browse these patches here [2].
>
> With these patches I have ethernet working on my IGEPv2 but this board
> uses an OMAP GPIO pin as the smsc911x IRQ line, so it needs to set a
> mux pin (mcspi1_cs2.gpio_176 INPUT | MODE4) or it will fallback on
> poll mode.
Great, that's good news :)
> For some reasons I still couldn't figure out (I'm still learning about
> Device Trees) adding:
>
> pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
>
> to the gpmc-smsc911x child node parse function (gpmc_smsc911x_init_dt)
> didn't have a functional effect and I had to initialize the defined
> pinctrl-single pins for the smsc911x in the omap3_pmx_core device node
> instead of pmc_smsc911x@0 as I do for other devices (mmc, uarts, etc).
Maybe this is related to the initcall ordering..
> So I just removed the devm_pinctrl_get_select_default() call in
> gpmc_smsc911x_init_dt() in for this RFC.
>
> I don't know if this is because arch/arm/mach-omap2/gpmc-smsc911x.c is
> not a real platform driver (is just a wrapper/helper function) and
> doesn't have a probe function.
..that function just initializes the pdata for smsc911x driver, and
should not be a driver. You need to add devm_pinctrl_get_select_default()
to the probe of smsc911x or the GPMC probe.
> Which brings me to the question if my approach of adding a binding for
> gpmc-smsc911x is correct or if we should extend/use the binding that
> already exist for smsc911x
> (Documentation/devicetree/bindings/net/smsc911x.txt).
We should use the existing smsc911x binding, then have a separate GPMC
binding for the GPMC driver.
Regards,
Tony
> [1]: git://github.com/martinezjavier/linux.git
> [2]: https://github.com/martinezjavier/linux/commits/gpmc-smsc911x-wip
> [3]: http://omappedia.org/wiki/Bootloader_Project#SYSBOOT_Pins
next prev parent reply other threads:[~2013-02-04 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 17:54 [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo Florian Vaussard
2013-01-28 17:54 ` [PATCH 1/2] ARM: dts: OMAP3: Add GPMC controller Florian Vaussard
2013-02-04 9:27 ` Javier Martinez Canillas
2013-02-04 10:36 ` Florian Vaussard
[not found] ` <510F8F49.9020800-p8DiymsW2f8@public.gmane.org>
2013-02-04 11:57 ` Javier Martinez Canillas
2013-02-04 17:32 ` Tony Lindgren [this message]
2013-02-04 18:15 ` Javier Martinez Canillas
2013-02-05 17:23 ` Florian Vaussard
2013-02-05 19:40 ` Javier Martinez Canillas
2013-02-16 13:09 ` Anil Kumar
2013-02-16 16:44 ` Javier Martinez Canillas
2013-02-18 12:26 ` Cousson, Benoit
2013-02-19 1:00 ` Jon Hunter
2013-03-14 16:01 ` Benoit Cousson
2013-01-28 17:54 ` [PATCH 2/2] ARM: dts: OMAP3: Add NAND memory for Overo products Florian Vaussard
2013-02-01 22:16 ` [PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo Tony Lindgren
2013-02-04 8:58 ` Florian Vaussard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130204173252.GN22517@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian.vaussard@epfl.ch \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=zonque@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).