On Mon, Aug 28, 2017 at 04:32:53PM +0200, Maciej S. Szmigiero wrote:
> Hi Johan,
>
> On 28.08.2017 12:19, Johan Hovold wrote:
> > On Mon, Aug 21, 2017 at 05:43:46PM +0200, Maciej S. Szmigiero wrote:
> >> This commit adds support (IDs, really) for D-Link DWM-157 hardware version
> >> C1 USB modem t
Johan Hovold writes:
> On Mon, Aug 28, 2017 at 04:32:53PM +0200, Maciej S. Szmigiero wrote:
>
>> Also, three other D-Link modems few lines above are using the same
>> USB_DEVICE_AND_INTERFACE_INFO() selectors.
>
> Yeah, I noticed those, and I'm not sure why they're not using
> class-matching only
On Tue, Aug 29, 2017 at 10:08:13AM +0200, Bjørn Mork wrote:
> Johan Hovold writes:
> > On Mon, Aug 28, 2017 at 04:32:53PM +0200, Maciej S. Szmigiero wrote:
> >
> >> Also, three other D-Link modems few lines above are using the same
> >> USB_DEVICE_AND_INTERFACE_INFO() selectors.
> >
> > Yeah, I no
All the vendor specific interfaces on these devices are serial
functions handled by this driver, so we can use a single class
match entry for each.
P: Vendor=2001 ProdID=7d01 Rev= 3.00
S: Manufacturer=D-Link,Inc
S: Product=D-Link DWM-156
C:* #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=500mA
A: FirstIf#=
On Mon, 2017-08-28 at 17:37 +0200, Oliver Neukum wrote:
> Sorry, wrong patch. Attached corrected version.
Thanks for the patch. I applied that to 4.12.0-pf7:
# rmmod uas
# patch -p1 < 0001-USB-uas-force-UAS-probing-for-ASMedia-1153.patch
patching file drivers/usb/storage/uas-detect.h
# make
# ma
Hi Ryan,
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 16/03/17 21:41, Ryan Stowell wrote:
> Hello,
>
> I'm having an issue with a pcie connected Texas Instruments TUSB7340
> host controller. I've been stress
On Tue, 2017-08-29 at 07:35 +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 28 Aug 2017 22:46:30 +0200
>
> Fix a word in this description.
>
> Signed-off-by: Markus Elfring
> ---
> drivers/media/usb/zr364xx/zr364xx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
The mt8173-mtu3.txt actually holds the bindings for all mediatek
SoCs with usb3 DRD IP, so add a generic compatible and change the
name to mediatek,mtu3.txt.
Signed-off-by: Chunfeng Yun
Acked-by: Rob Herring
---
.../usb/{mt8173-mtu3.txt => mediatek,mtu3.txt} |6 +-
1 file changed, 5
The xhci-mtk driver is a generic driver for MediaTek xHCI IP, add
a generic compatible to avoid confusion when support new SoCs but
use a compatible with specific SoC's name "mt8173".
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c |1 +
1 file changed, 1 insertion(+)
diff --git
The mt8173-xhci.txt actually holds the bindings for all mediatek
SoCs with xHCI controller, so add a generic compatible and change
the name to mediatek,mtk-xhci.txt to reflect that.
Signed-off-by: Chunfeng Yun
---
.../usb/{mt8173-xhci.txt => mediatek,mtk-xhci.txt} | 14 +++---
.../devi
Hello!
On 8/29/2017 12:20 PM, 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
name to mediatek,mtu3.txt.
Signed-off-by: Chunfeng Yun
Acked-by: Rob Herring
---
.../usb/{mt8173-mtu3.txt =>
On 28.08.2017 17:40, Mason wrote:
On 28/08/2017 10:39, Mathias Nyman wrote:
Could you take a log with the following added debug, without
your extra delays, It should show a bit more about the state
of the controller when we read 0x
I applied the following patch on top of v4.12-rc1
di
On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> Then again it might be a bit too drastic to kill xhci just because
> we read 0x once from a mmio xhci register. Maybe we should
> return an error a couple times before actually tearing down xhci.
>
> This tight check was orig
On 08/28/2017 08:13 PM, Nobuo Iwata wrote:
> This patch adds recovery from false busy state on concurrent attach
> operation.
>
> The procedure of attach operation is as below.
> 1) Find an unused port in /sys/devices/platform/vhci_hcd/status.
> (userspace)
> 2) Request attach found port to driv
On Tue, Aug 29, 2017 at 10:45:13AM +0200, Bjørn Mork wrote:
> All the vendor specific interfaces on these devices are serial
> functions handled by this driver, so we can use a single class
> match entry for each.
>
> P: Vendor=2001 ProdID=7d01 Rev= 3.00
> S: Manufacturer=D-Link,Inc
> S: Pro
On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote:
> On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> > Then again it might be a bit too drastic to kill xhci just because
> > we read 0x once from a mmio xhci register. Maybe we should
> > return an error a couple t
On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote:
> > On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> > > Then again it might be a bit too drastic to kill xhci just because
> > > we read 0x on
On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote:
> On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote:
> > > On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> > > > Then again it might be a
This commit adds support (an ID, really) for D-Link DWM-157 hardware
version C1 USB modem to option driver.
According to manufacturer-provided Windows INF file the device has four
serial ports:
"D-Link HSPA+DataCard Diagnostics Interface" (interface 2; modem port),
"D-Link HSPA+DataCard NMEA Devic
On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> This tight check was originally done to detect pci hotplug removed
> hosts as soon as possible.
In Mason's case, the parent of the XHCI controller isn't a hotplug port,
see this lspci output:
https://www.spinics.net/lists/linux-usb/
On Tue, 2017-08-29 at 13:08 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 8/29/2017 12:20 PM, 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
> > name to mediatek,mtu3.txt.
> >
> > Si
On Wed, Aug 30, 2017 at 01:53:10AM +0200, Lukas Wunner wrote:
> On Tue, Aug 29, 2017 at 04:28:53PM +0300, Mathias Nyman wrote:
> > This tight check was originally done to detect pci hotplug removed
> > hosts as soon as possible.
>
> In Mason's case, the parent of the XHCI controller isn't a hotplu
On Tue, Aug 29, 2017 at 05:51:38PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote:
> > On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote:
> > > On Tue, Aug 29, 2017 at 03:38:52PM +0200, Lukas Wunner wrote:
> > Is 0x not a val
On Wed, Aug 30, 2017 at 08:36:23AM +0200, Lukas Wunner wrote:
> On Tue, Aug 29, 2017 at 05:51:38PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Aug 29, 2017 at 05:34:56PM +0200, Lukas Wunner wrote:
> > > On Tue, Aug 29, 2017 at 04:47:25PM +0200, Greg Kroah-Hartman wrote:
> > > > On Tue, Aug 29, 201
24 matches
Mail list logo
