The current OC (Over Current) handling does not consider the default
and bootloader OC setting well, in this commit, we reset OC setting
according to dts value:
- If property "disable-over-current" is set, we will disable OC at
code; otherwise, we will enable OC.
- Since most of USB power control
>
> > -Original Message-
> > From: Matthew Starr
> > Sent: 2018年11月30日 23:09
> > To: PETER CHEN ; linux-usb@vger.kernel.org; Jun Li
> >
> > Subject: RE: [PATCH] usb: chipidea: imx: Allow OC polarity active low
> >
> > > -Original Message-
> > > From: PETER CHEN
Hi Peter,
> -Original Message-
> From: Matthew Starr
> Sent: 2018年11月30日 23:09
> To: PETER CHEN ; linux-usb@vger.kernel.org; Jun Li
>
> Subject: RE: [PATCH] usb: chipidea: imx: Allow OC polarity active low
>
> > -Original Message-
> > From: PETER CHEN
On Motorola Mapphone devices such as Droid 4 there are five USB ports
that do not use the same layout as Gobi 1K/2K/etc devices listed in
qcserial.c. So we should use qcaux.c or option.c as noted by
Dan Williams .
The ff/ff/ff interfaces seem to always be UARTs on Motorola devices.
And we should
Up to now the polarity of the over current pin was hard coded to active
high. Use the already defined device tree properties to configure polarity
on i.MX25, too. In difference to i.MX6/7 use active high behavior if the
polarity is unspecified to keep compatibility to existing device trees.
The polarity of the over current detection pin isn't configured on i.MX6/7
if it's unspecified in the device tree. So the actual configuration depends
on bootloader behavior which is bad.
So encourage users to fix their device tree by issuing a warning in this
case.
Signed-off-by: Uwe
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 polarity isn't changed and so the
polarity is kept as setup by the bootloader. Reset default is
active high, so active low can only be used with
On Fri, Nov 30, 2018 at 11:29:13PM +, Matthew Starr wrote:
> The implementation for setting the over current polarity has always been
> the over-current-active-high property. The problem with this is there
> is no way to enable over current active low polarity since the default
> state of the
On 2 Dec 2018, at 12:40, Alexander Theißen wrote:
>>> On 1 Dec 2018, at 13:06, Alexander Theißen wrote:
[...]
>>> How do you use that driver? For me the hid driver always claims the device.
>>> I have to manually bind the driver to the display to have it bound to the
>>> appledisplay driver.
Hi,
thanks for the quick reply! :)
On Sun, Dec 02, 2018 at 03:41:29PM +0100, Hans de Goede wrote:
> Hi,
>
> On 01-12-18 13:22, Stephan Gerhold wrote:
> > Hi,
> >
> > I have been updating my Intel Baytrail tablet from 4.14 to 4.19 and
> > noticed that the tusb1210 PHY driver now fails to probe
Hi,
On 01-12-18 13:22, Stephan Gerhold wrote:
Hi,
I have been updating my Intel Baytrail tablet from 4.14 to 4.19 and
noticed that the tusb1210 PHY driver now fails to probe on 4.19.x and
4.20-rc4:
tusb1210: probe of dwc3.0.auto.ulpi failed with error -16 (EBUSY)
The commit that broke
>> On 1 Dec 2018, at 13:06, Alexander Theißen wrote:
>>
>> Hi Mattias,
>>
>> I am writing you because you edited the drivers/usb/misc/appledisplay.c
>> driver and I am hoping that you are a user of that driver.
>>
>> How do you use that driver? For me the hid driver always claims the device.
>>
12 matches
Mail list logo
