| Message ID | 1342769508-24810-2-git-send-email-anilkumar@ti.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
* AnilKumar Ch <anilkumar@ti.com> [120720 00:36]: > Add basic pinctrl support for AM33XX family of devices by adding DT > data to am33xx dtsi file. These patches are based on pinctrl-single > driver and tested on am335x-evm & am335x-bone devices. > > Signed-off-by: AnilKumar Ch <anilkumar@ti.com> > --- > arch/arm/boot/dts/am33xx.dtsi | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi > index 59509c4..9b974dc 100644 > --- a/arch/arm/boot/dts/am33xx.dtsi > +++ b/arch/arm/boot/dts/am33xx.dtsi > @@ -40,6 +40,15 @@ > }; > }; > > + am3358_pinmux: pinmux@44E10800 { > + compatible = "pinctrl-single"; > + reg = <0x44E10800 0x0338>; > + #address-cells = <1>; > + #size-cells = <0>; > + pinctrl-single,register-width = <32>; > + pinctrl-single,function-mask = <0x7F>; > + }; > + > /* > * XXX: Use a flat representation of the AM33XX interconnect. > * The real AM33XX interconnect network is quite complex.Since Is there only one padconf domain on 33xx instead of separate core and wkup domains like omap3 and omap4 have? Regards, Tony
On Tue, Jul 24, 2012 at 14:02:04, Tony Lindgren wrote: > * AnilKumar Ch <anilkumar@ti.com> [120720 00:36]: > > Add basic pinctrl support for AM33XX family of devices by adding DT > > data to am33xx dtsi file. These patches are based on pinctrl-single > > driver and tested on am335x-evm & am335x-bone devices. > > > > Signed-off-by: AnilKumar Ch <anilkumar@ti.com> > > --- > > arch/arm/boot/dts/am33xx.dtsi | 9 +++++++++ > > 1 files changed, 9 insertions(+), 0 deletions(-) > > > > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi > > index 59509c4..9b974dc 100644 > > --- a/arch/arm/boot/dts/am33xx.dtsi > > +++ b/arch/arm/boot/dts/am33xx.dtsi > > @@ -40,6 +40,15 @@ > > }; > > }; > > > > + am3358_pinmux: pinmux@44E10800 { > > + compatible = "pinctrl-single"; > > + reg = <0x44E10800 0x0338>; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + pinctrl-single,register-width = <32>; > > + pinctrl-single,function-mask = <0x7F>; > > + }; > > + > > /* > > * XXX: Use a flat representation of the AM33XX interconnect. > > * The real AM33XX interconnect network is quite complex.Since > > Is there only one padconf domain on 33xx instead of separate core > and wkup domains like omap3 and omap4 have? > Yes, in case of AM33XX we have only on padconf domain. Regards AnilKumar
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi index 59509c4..9b974dc 100644 --- a/arch/arm/boot/dts/am33xx.dtsi +++ b/arch/arm/boot/dts/am33xx.dtsi @@ -40,6 +40,15 @@ }; }; + am3358_pinmux: pinmux@44E10800 { + compatible = "pinctrl-single"; + reg = <0x44E10800 0x0338>; + #address-cells = <1>; + #size-cells = <0>; + pinctrl-single,register-width = <32>; + pinctrl-single,function-mask = <0x7F>; + }; + /* * XXX: Use a flat representation of the AM33XX interconnect. * The real AM33XX interconnect network is quite complex.Since
Add basic pinctrl support for AM33XX family of devices by adding DT data to am33xx dtsi file. These patches are based on pinctrl-single driver and tested on am335x-evm & am335x-bone devices. Signed-off-by: AnilKumar Ch <anilkumar@ti.com> --- arch/arm/boot/dts/am33xx.dtsi | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-)