From: mgr@pengutronix.de (Michael Grzeschik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4 V2] ARM: mx28: Add USB PHY overcurrent pinmux
Date: Sun, 24 Nov 2013 17:05:00 +0100 [thread overview]
Message-ID: <20131124160459.GG24508@pengutronix.de> (raw)
In-Reply-To: <F281D0F91ED19E4D8E63A7504E8A64980411E0AF@039-SN2MPN1-021.039d.mgd.msft.net>
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 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 {
> > > --
> > > 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 |
next prev parent reply other threads:[~2013-11-24 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:51 [PATCH 1/4 V2] ARM: mx28: Add SPI 2 pinmux into imx28.dtsi Marek Vasut
2012-08-24 23:51 ` [PATCH 2/4 V2] ARM: mx28: Add USB PHY overcurrent pinmux Marek Vasut
2012-08-25 7:57 ` Shawn Guo
2013-11-22 15:49 ` Michael Grzeschik
2013-11-23 14:48 ` Peter Chen
2013-11-24 16:05 ` Michael Grzeschik [this message]
2013-11-24 23:58 ` Marek Vasut
2013-11-25 13:42 ` Michael Grzeschik
2013-11-26 12:08 ` Peter Chen
2013-12-06 15:17 ` Michael Grzeschik
2013-12-09 5:12 ` Peter Chen
2012-08-24 23:51 ` [PATCH 3/4 V2] ARM: mxs: Update DENX M28 machine and dts file Marek Vasut
2012-08-25 8:05 ` Shawn Guo
2012-08-26 11:42 ` Marek Vasut
2012-08-24 23:51 ` [PATCH 4/4] ARM: mxs: Add SchulerControl SPS1 DTS file Marek Vasut
2012-08-25 8:30 ` Shawn Guo
2012-08-25 12:35 ` Marek Vasut
2012-08-25 13:03 ` Shawn Guo
2012-08-28 0:28 ` Shawn Guo
2012-08-28 0:44 ` Marek Vasut
2012-08-25 7:56 ` [PATCH 1/4 V2] ARM: mx28: Add SPI 2 pinmux into imx28.dtsi Shawn Guo
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=20131124160459.GG24508@pengutronix.de \
--to=mgr@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).