> -Original Message-
> From: Uwe Kleine-König [mailto:u.kleine-koe...@pengutronix.de]
> Sent: Sunday, December 02, 2018 3:33 PM
>
> The status quo on i.MX6 is that if "over-current-active-high" is
> specified in the device tree this is configured as expected. If
> the property is missing
ity as high explicitly;
> > > > otherwise, we set it as low explicitly.
> > > >
> > > > Cc: stable
> > > > Cc: Peter Chen
> > > > Cc: Uwe Kleine-König
> > > > Cc: Matthew Starr
> > > > Signed-off-by: Peter Chen
&
> -Original Message-
> From: Uwe Kleine-König [mailto:u.kleine-koe...@pengutronix.de]
> Sent: Friday, November 30, 2018 3:35 PM
>
> Hello Fabio,
>
> On Fri, Nov 30, 2018 at 07:16:39PM -0200, Fabio Estevam wrote:
> > [Adding Matt]
> >
> > On Fri, Nov 30, 2018 at 6:53 PM Uwe Kleine-König
>
-current-active-high property with the
over-current-active-low property. Without this property the over
current polarity will be active high by default like it always has been.
With the property the over current polarity will be active low.
Signed-off-by: Matthew Starr
---
.../devicetree/bindings/usb
been missed up till now because the bit next to the
OVER_CUR_POL bit is the PWR_POL which has the exact inverse logic with a value
of 1 meaning high enable and 0 meaning low enable. Also I rarely have seen the
USB interface go into an overcurrent situation so maybe no one ever caught
thi
-current-active-high property with the
over-current-active-low property. Without this property the over
current polarity will be active high by default like it always has been.
With the property the over current polarity will be active low.
Signed-off-by: Matthew Starr
---
Documentation/devicetree
