On Sat, Nov 23, 2013 at 02:48:48PM +0000, Peter Chen wrote:
>
>
> > >
> > > 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@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@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@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@8001c000 {
> > > --
> > > 1.7.10.4
> >
> >
> > @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.
> >
>
> I haven't checked pinmux detail, have you enabled oc and
> set oc's polarity (HW_DIGCTL_CTRL - 8001_C000h)?
No, I was not aware those DIG*DEEP*CTL bits exist. :)
Thank you Peter!
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
