From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: Query on pinctrl usage for DT nodes
Date: Wed, 3 Apr 2013 11:42:03 -0700 [thread overview]
Message-ID: <20130403184202.GB10155@atomide.com> (raw)
In-Reply-To: <20130403183803.GA10155@atomide.com>
* Tony Lindgren <tony@atomide•com> [130403 11:42]:
> * Stephen Warren <swarren@wwwdotorg•org> [130403 09:49]:
> > On 04/03/2013 03:16 AM, Prabhakar Lad wrote:
> > > Hi Linus/Stephen,
> > >
> > > I am working adding DT nodes for DA850.
> > >
> > > Following is the pin control snippet of da850.dtsi:-
> > >
> > > pmx_core: pinmux at 1c14120 {
> > ...
> > > i2c0_pins: pinmux_i2c0_pins {
> > > pinctrl-single,bits = <
> > > /* I2C0_SDA,I2C0_SCL */
> > > 0x10 0x00002200 0x0000ff00
> > > >;
> > > };
> > > mdio_pins: pinmux_mdio_pins {
> > > pinctrl-single,bits = <
> > > /* MDIO_CLK, MDIO_D */
> > > 0x10 0x00000088 0x000000ff
> > > >;
> > > };
> > > }
> > >
> > > And following is the code snippet for dts:-
> > >
> > > i2c0: i2c at 1c22000 {
> > > status = "okay";
> > > clock-frequency = <100000>;
> > > pinctrl-names = "default";
> > > pinctrl-0 = <&i2c0_pins>;
> > > };
> > > mdio: mdio at 1e24000 {
> > > status = "okay";
> > > bus_freq = <2200000>;
> > > pinctrl-names = "default";
> >
> > I assume there's also the following there:
> >
> > pinctrl-0 = <&mdio_pins>;
> >
> > > };
> > >
> > > But while booting I see the following boot log:-
> > > ...
> > > cpuidle: using governor menu
> > > TCP: cubic registered
> > > NET: Registered protocol family 17
> > > pinctrl-single 1c14120.pinmux: pin 1c14130 already requested by
> > > davinci_mdio.0; cannot claim for i2c_davinci.1
> > > pinctrl-single 1c14120.pinmux: pin-4 (i2c_davinci.1) status -22
> > > pinctrl-single 1c14120.pinmux: could not request pin 4 on device pinctrl-single
> > > console [netcon0] enabled
> > > ....
> > >
> > > This is because the mdio and i2c are using same pin 0x10,
> >
> > How can two devices use the same pin? I mean physically, in hardware?
> >
> > Is this because pinctrl-single uses the register address as the pin
> > number, whereas you have registers which configure multiple pins at
> > once? If so, your hardware isn't something that can be represented by
> > pinctrl-single.
> >
> > > Is there any
> > > alternative way to handle if the two node's are using same pins any
> > > pointers could be very much helpful ?
>
> It could also that the mux register(s) follow the one-mux-per-bit
> mapping.
>
> In that case pinctrl-single,bits option as documented in the
> Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt.
Oh it's already using pinctrl-single,bits option. Maybe there's a
bug, adding Peter to cc.
Regards,
Tony
next prev parent reply other threads:[~2013-04-03 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 9:16 Query on pinctrl usage for DT nodes Prabhakar Lad
2013-04-03 16:44 ` Stephen Warren
2013-04-03 18:38 ` Tony Lindgren
2013-04-03 18:42 ` Tony Lindgren [this message]
2013-04-15 8:19 ` Peter Ujfalusi
2013-04-15 16:40 ` Stephen Warren
2013-04-16 7:18 ` Peter Ujfalusi
2013-04-08 13:12 ` Prabhakar Lad
2013-04-08 17:24 ` Stephen Warren
2013-04-10 8:12 ` Prabhakar Lad
2013-04-10 17:32 ` Stephen Warren
2013-04-10 20:34 ` Tony Lindgren
2013-04-15 5:09 ` Prabhakar Lad
2013-04-15 6:42 ` Prabhakar Lad
2013-04-15 8:26 ` Peter Ujfalusi
2013-04-16 21:32 ` Tony Lindgren
2013-04-23 7:42 ` Peter Ujfalusi
2013-04-23 18:17 ` Tony Lindgren
2013-05-21 14:16 ` Manjunathappa, Prakash
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=20130403184202.GB10155@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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