On 11.08.2017 19:01, Kai-Heng Feng wrote:
Hi,
My ASUS PRIME B350M-A uses this XHCI chip:
03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB
3.1 XHCI Controller [1022:43bb] (rev 02)
...which matches to the PCI_DEVICE_ID_AMD_PROMONTORYA_2.
Revert commit dec08194ffeccfa1cf0859
On Mon, 14 Aug 2017, Lee Jones wrote:
> On Sun, 13 Aug 2017, Wolfram Sang wrote:
>
> > On Tue, May 23, 2017 at 08:18:19AM +0100, Lee Jones wrote:
> > > On Mon, 22 May 2017, Wolfram Sang wrote:
> > >
> > > > include/linux/i2c is not for client devices. Move the header file to a
> > > > more appro
> > Given the triviality of the change for non-MFD subsystems, can we apply
> > this for 4.14?
>
> I can't apply anything without Acks for *all* of the subsystems above.
Well, there are cases when you can. Those should be exceptions and well
justified, of course.
> My suggestion would be to col
On 08/11/2017 09:00 AM, Chunfeng Yun wrote:
On Thu, 2017-08-10 at 21:54 -0500, Rob Herring wrote:
On Tue, Aug 08, 2017 at 01:42:51PM +0800, Chunfeng Yun wrote:
The mt8173-mtu3.txt actually holds the bindings for all mediatek
SoCs with usb3 DRD IP, so add a generic compatible and change the
na
Hi,
On Sunday 13 August 2017 05:34 PM, Alexandre Bailon wrote:
> The DA8xx and DSPS platforms don't use the same address for few registers.
> On Da8xx, this is causing some issues (e.g. teardown that doesn't work).
> Configure the address of the register during the init and use them instead
> of c
On Monday 14 August 2017 07:01 PM, Sekhar Nori wrote:
> Hi,
>
> On Sunday 13 August 2017 05:34 PM, Alexandre Bailon wrote:
>> The DA8xx and DSPS platforms don't use the same address for few registers.
>> On Da8xx, this is causing some issues (e.g. teardown that doesn't work).
>> Configure the addr
On Fri, Aug 11 2017, Jerry Zhang wrote:
> Users can apply i/o in the wrong direction on an
> endpoint to stall it. In case there is an error
> that does not allow the endpoint to be stalled,
> we want the user to know.
>
> An operation to stall the endpoint will return
> EBADMSG if successful, EAGA
* Lee Jones [170814 01:44]:
> On Mon, 14 Aug 2017, Lee Jones wrote:
>
> > On Sun, 13 Aug 2017, Wolfram Sang wrote:
> >
> > > On Tue, May 23, 2017 at 08:18:19AM +0100, Lee Jones wrote:
> > > > On Mon, 22 May 2017, Wolfram Sang wrote:
> > > >
> > > > > include/linux/i2c is not for client devices.
* Wolfram Sang [170814 01:43]:
>
> > > Given the triviality of the change for non-MFD subsystems, can we apply
> > > this for 4.14?
> >
> > I can't apply anything without Acks for *all* of the subsystems above.
>
> Well, there are cases when you can. Those should be exceptions and well
> justif
> > Even if it doesn't, it still requires Acks.
>
> As long as this has been compile tested with omap1_defconfig:
>
> Acked-by: Tony Lindgren
Hah, just in time. I was about to send out the new version, thanks! :D
buildbot did test it and I did compile tests, too.
signature.asc
Description:
> Acked-by: Daniel Thompson
Added, thanks!
signature.asc
Description: PGP signature
On 14/08/17 17:22, Tony Lindgren wrote:
* Wolfram Sang [170814 01:43]:
Given the triviality of the change for non-MFD subsystems, can we apply
this for 4.14?
I can't apply anything without Acks for *all* of the subsystems above.
Well, there are cases when you can. Those should be exceptio
udc_stop needs to be called before gadget driver unbind. Otherwise it
might happen that udc drivers still call into the gadget driver (e.g.
to reset gadget after OTG event). If this happens it is likely to get
panics from gadget driver dereferencing NULL ptr, as gadget's drvdata
is set to NULL on u
On Mon, Aug 14, 2017 at 7:26 AM, Michal Nazarewicz wrote:
> On Fri, Aug 11 2017, Jerry Zhang wrote:
>> Users can apply i/o in the wrong direction on an
>> endpoint to stall it. In case there is an error
>> that does not allow the endpoint to be stalled,
>> we want the user to know.
>>
>> An operat
Let me apologize for emailing directly to the list as I'm not one of
the developers and just starting out with USB and UVC. After searching
online for about a week I just couldn't find answers and I hope the
original authors of the uvc-gadget tool are on the list and can help
out.
Needed to test a
Hi Heikki,
While testing with different type-c phones available in the market,
With some phones, I noticed that supports_usb_power_delivery
reports "no" eventhough an explicit pd contract has been
established. After spending sometime debugging, I noticed that
the root cause of this is that the par
Currenly, f_midi_free uses snd_card_free, which will wait
until the user has released the sound card before
returning. However, if the user doesn't release the sound
card, then f_midi_free can block for an arbitrary amount
of time, which also blocks any gadget operations on that
thread.
Instead, w
Add CYPRESS_VID vid and CYPRESS_WICED_BT_USB and CYPRESS_WICED_WL_USB device
IDs to ftdi_sio driver.
Signed-off-by: Jeffrey Chu
---
drivers/usb/serial/ftdi_sio.c | 2 ++
drivers/usb/serial/ftdi_sio_ids.h | 7 +++
2 files changed, 9 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.
On Mon, Aug 14, 2017 at 09:24:51PM +, Jeffrey Chu wrote:
> Add CYPRESS_VID vid and CYPRESS_WICED_BT_USB and CYPRESS_WICED_WL_USB device
> IDs to ftdi_sio driver.
> Signed-off-by: Jeffrey Chu
> ---
> drivers/usb/serial/ftdi_sio.c | 2 ++
> drivers/usb/serial/ftdi_sio_ids.h | 7 +++
>
On Mon, Aug 14 2017, Jerry Zhang wrote:
> On Mon, Aug 14, 2017 at 7:26 AM, Michal Nazarewicz wrote:
>> On Fri, Aug 11 2017, Jerry Zhang wrote:
>>> Users can apply i/o in the wrong direction on an
>>> endpoint to stall it. In case there is an error
>>> that does not allow the endpoint to be stalled
This series is the outcome of a discussion with Felipe Balbi,
see [0] and [1].
The quick-summary of this is:
- dwc3 already takes one USB2 and one USB3 PHY and initializes these
correct
- some other HCI platform drivers (like ehci-platform.c, xhci-mtk.c and
ohci-platform.c) do not have a limita
Many SoC platforms have separate devices for the USB PHY which are
registered through the generic PHY framework. These PHYs have to be
enabled to make the USB controller actually work. They also have to be
disabled again on shutdown/suspend.
Currently (at least) the following HCI platform drivers
A USB root-hub may have several PHYs which need to be configured before
the root-hub starts working.
This adds the documentation for such a USB root-hub.
Signed-off-by: Martin Blumenstingl
---
.../devicetree/bindings/usb/usb-roothub.txt| 46 ++
1 file changed, 46 inse
This enables the platform-roothub for the xhci-plat driver. This allows
specifying a PHY for each port via devicetree. All PHYs will then be
enabled/disabled by the platform-roothub driver.
One example where this is required is the Amlogic GXL and GXM SoCs:
They are using a dwc3 USB controller wit
Add super speed descriptors for f_midi.
Signed-off-by: Badhri Jagan Sridharan
---
drivers/usb/gadget/function/f_midi.c | 42 +---
1 file changed, 39 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_m
On Mon, 2017-08-14 at 13:23 +0200, Matthias Brugger wrote:
>
> On 08/11/2017 09:00 AM, Chunfeng Yun wrote:
> > On Thu, 2017-08-10 at 21:54 -0500, Rob Herring wrote:
> >> On Tue, Aug 08, 2017 at 01:42:51PM +0800, Chunfeng Yun wrote:
> >>> The mt8173-mtu3.txt actually holds the bindings for all medi
26 matches
Mail list logo
