[PATCH 2/4 V2] ARM: mx28: Add USB PHY overcurrent pinmux

[marex@denx.de (Marek Vasut)]

Hello Michael,

> Hi Marek, Peter,
> 
> On Sat, Aug 25, 2012 at 01:51:38AM +0200, Marek Vasut wrote:
> > Add the pinmux settings for USB PHY overcurrent pins.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Chris Ball <cjb@laptop.org>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > 
> >  arch/arm/boot/dts/imx28.dtsi |   30 ++++++++++++++++++++++++++++++
> >  1 file changed, 30 insertions(+)
> > 
> > V2: This is pulled from the M28EVK and SPS1 board files, put it into
> > common
> > 
> >     file.
> > 
> > diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> > index b996c2d..3cba62d 100644
> > --- a/arch/arm/boot/dts/imx28.dtsi
> > +++ b/arch/arm/boot/dts/imx28.dtsi
> > @@ -520,6 +520,36 @@
> > 
> >  					fsl,voltage = <1>;
> >  					fsl,pull-up = <1>;
> >  				
> >  				};
> > 
> > +
> > +				usbphy0_pins_a: usbphy0 at 0 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <
> > +						0x2152 /* 
MX28_PAD_SSP2_SS2__USB0_OVERCURRENT */
> > +					>;
> > +					fsl,drive-strength = <2>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> > +				usbphy0_pins_b: usbphy0 at 1 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <
> > +						0x3061 /* 
MX28_PAD_AUART1_CTS__USB0_OVERCURRENT */
> > +					>;
> > +					fsl,drive-strength = <2>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > +
> > +				usbphy1_pins_a: usbphy1 at 0 {
> > +					reg = <0>;
> > +					fsl,pinmux-ids = <
> > +						0x2142 /* 
MX28_PAD_SSP2_SS1__USB1_OVERCURRENT */
> > +					>;
> > +					fsl,drive-strength = <2>;
> > +					fsl,voltage = <1>;
> > +					fsl,pull-up = <0>;
> > +				};
> > 
> >  			};
> >  			
> >  			digctl at 8001c000 {
> 
> @Marek: Did you test the overcurrent functionality with the MX28 and this
> pinmux?
> 
> I currently can not trigger any overcurrent events and also don't
> see changes in the PORTSC register after pulling the OC pin to 3V3.

Sorry for the late reply, I see Peter already replied. Do you see the changes if 
you configure the pin as a GPIO at least ?

Best regards,