Hi,
Alan Stern writes:
> Felipe:
>
> On Thu, 29 Jun 2017, kernel test robot wrote:
>
>> FYI, we noticed the following commit:
>>
>> commit: f16443a034c7aa359ddf6f0f9bc40d01ca31faea ("USB: gadgetfs, dummy-hcd,
>> net2280: fix locking for callbacks")
>> https://git.kernel.org/cgit/linux/kernel/
On 13 July 2017 at 04:12, Bjorn Helgaas wrote:
> On Mon, Jul 10, 2017 at 04:52:28PM +0100, Marc Zyngier wrote:
>> Ard and myself have just spent quite some time lately trying to pin
>> down an issue in the DMA code which was taking the form of a PCIe USB3
>> controller issuing a DMA access at some
On 12 July 2017 at 16:58, Manu Gautam wrote:
>
>
> On 7/12/2017 2:06 PM, Baolin Wang wrote:
>>
>> Hi,
>>
>> On 12 July 2017 at 15:25, Manu Gautam wrote:
>>>
>>>
>>> On 7/12/2017 12:19 PM, Baolin Wang wrote:
Hi,
On 3 July 2017 at 19:25, Manu Gautam wrote:
>
> Driver po
Hi,
On 13 July 2017 at 07:20, gustavo panizzo wrote:
> Hello Wang
>
> thanks for your response
>
>
> On Wed, Jul 12, 2017 at 02:08:04PM +0800, Baolin Wang wrote:
>>
>> Hi,
>>
>> On 12 July 2017 at 11:52, gustavo panizzo wrote:
>>>
>>> The dwc3 could not release resources when the module is built
On Mon, Jul 10, 2017 at 04:52:28PM +0100, Marc Zyngier wrote:
> Ard and myself have just spent quite some time lately trying to pin
> down an issue in the DMA code which was taking the form of a PCIe USB3
> controller issuing a DMA access at some bizarre address, and being
> caught red-handed by th
Hi,
On 07/13/2017 09:39 AM, Dou Liyang wrote:
> Hi, Lu
>
> At 07/13/2017 09:17 AM, Lu Baolu wrote:
>> Hi,
>>
>> On 07/12/2017 04:02 PM, Dou Liyang wrote:
>>> Hi, Lu
>>>
>>> At 05/05/2017 08:50 PM, Boris Ostrovsky wrote:
On 05/05/2017 01:41 AM, Lu Baolu wrote:
> Hi,
>
> On 05/03/20
Hi, Lu
At 07/13/2017 09:17 AM, Lu Baolu wrote:
Hi,
On 07/12/2017 04:02 PM, Dou Liyang wrote:
Hi, Lu
At 05/05/2017 08:50 PM, Boris Ostrovsky wrote:
On 05/05/2017 01:41 AM, Lu Baolu wrote:
Hi,
On 05/03/2017 06:38 AM, Boris Ostrovsky wrote:
On 03/21/2017 04:01 AM, Lu Baolu wrote:
Add a simp
Hi,
On 07/12/2017 04:02 PM, Dou Liyang wrote:
> Hi, Lu
>
> At 05/05/2017 08:50 PM, Boris Ostrovsky wrote:
>> On 05/05/2017 01:41 AM, Lu Baolu wrote:
>>> Hi,
>>>
>>> On 05/03/2017 06:38 AM, Boris Ostrovsky wrote:
On 03/21/2017 04:01 AM, Lu Baolu wrote:
> Add a simple udelay calibration in
Even though the IO for devices with "always poll" quirk is already running,
we still need to set HID_OPENED bit in usbhid->iofl so the interrupt
handler does not ignore the data coming from the device.
Reported-by: Olof Johansson
Tested-by: Olof Johansson
Fixes: e399396a6b0 ("HID: usbhid: remove
Hello Wang
thanks for your response
On Wed, Jul 12, 2017 at 02:08:04PM +0800, Baolin Wang wrote:
Hi,
On 12 July 2017 at 11:52, gustavo panizzo wrote:
The dwc3 could not release resources when the module is built-in
because this module does not have shutdown method. This causes the USB
3.0 hu
Hi friend
I am a banker in IDB BANK. I want to transfer an abandoned sum of USD15.
6Million to your Bank account. 40/percent will be your share. No risk involved
but keeps it as secret. Contact me for more details. Please reply me through my
alternative email id only (mrsmithawl...@gmail.com) f
On 10 July 2017 at 18:21, Ard Biesheuvel wrote:
> On 10 July 2017 at 16:52, Marc Zyngier wrote:
>> Ard and myself have just spent quite some time lately trying to pin
>> down an issue in the DMA code which was taking the form of a PCIe USB3
>> controller issuing a DMA access at some bizarre addre
On Wed, Jul 12, 2017 at 12:10:02PM -0400, Alan Stern wrote:
> This is pretty conclusive. The problem comes about because
> usb_stor_control_thread() calls scsi_mq_done() while holding
> shost->host_lock, and then scsi_eh_scmd_add() tries to acquire that
> same lock.
>
> I don't know why this didn
On Thu, 13 Jul 2017, Arthur Marsh wrote:
> Thanks for the advice, I've enabled CONFIG_FRAME_POINTER and managed to
> catch 1 more log triggered by issuing a
>
> blkid
>
> command after inserting a USB stick.
>
> The problem is that I can't be certain of triggering the problem when
> testing k
On Wed, Jul 12, 2017 at 11:50:35AM +0200, Johannes Becker wrote:
> On Wed, Jul 12, 2017 at 10:05 AM, Greg KH wrote:
> > If you don't want this new feature enabled, you could disable the
> > loading of the driver to the device by blacklisting it somehow in a
> > modules configuration file somewhere
Alan Stern wrote on 11/07/17 23:30:
For your future tests, it would help to enable CONFIG_FRAME_POINTER.
If it is worthwhile doing a git-bisect on usb-storage I could do that also.
I agree with Matt; it's quite possible that the real bug is somewhere
else and it just shows up in usb-storag
Am Mittwoch, den 12.07.2017, 15:08 +0200 schrieb Johan Hovold:
> Add device-id entry for DATECS FP-2000 fiscal printer needing the
> NO_UNION_NORMAL quirk.
>
> Reported-by: Anton Avramov
> Cc: stable
> Signed-off-by: Johan Hovold
Acked-by: Oliver Neukum
--
To unsubscribe from this list: send t
On Wed, Jul 12, 2017 at 02:51:05PM +0200, Oliver Neukum wrote:
> Am Mittwoch, den 12.07.2017, 15:37 +0300 schrieb Anton Avramov:
> > В 13:35 +0200 на 12.07.2017 (ср), Johan Hovold написа:
> > >
> > > [ Please avoid top-posting. ]
> > >
> > > > Self Powered
> > > It seems you need the NO_UNION_N
Add device-id entry for DATECS FP-2000 fiscal printer needing the
NO_UNION_NORMAL quirk.
Reported-by: Anton Avramov
Cc: stable
Signed-off-by: Johan Hovold
---
drivers/usb/class/cdc-acm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-
Am Mittwoch, den 12.07.2017, 15:37 +0300 schrieb Anton Avramov:
> В 13:35 +0200 на 12.07.2017 (ср), Johan Hovold написа:
> >
> > [ Please avoid top-posting. ]
> >
> > > Self Powered
> > It seems you need the NO_UNION_NORMAL quirk. Does the following work
> > better?
> >
> > echo fff0 0
В 13:35 +0200 на 12.07.2017 (ср), Johan Hovold написа:
> [ Please avoid top-posting. ]
>
> On Wed, Jul 12, 2017 at 01:16:00PM +0300, Anton Avramov wrote:
> >
> > I've tried
> > modprobe cdc-acm
> > echo fff0 0100 > /sys/bus/usb/drivers/cdc_acm/new_id
> >
> > But it didn't show as a device.
>
[ Please avoid top-posting. ]
On Wed, Jul 12, 2017 at 01:16:00PM +0300, Anton Avramov wrote:
> I've tried
> modprobe cdc-acm
> echo fff0 0100 > /sys/bus/usb/drivers/cdc_acm/new_id
>
> But it didn't show as a device.
> Here is the relevant output of dmesg:
> [ 379.300082] cdc_acm 4-2:1.0: Zero
I've tried
modprobe cdc-acm
echo fff0 0100 > /sys/bus/usb/drivers/cdc_acm/new_id
But it didn't show as a device.
Here is the relevant output of dmesg:
[ 379.300082] cdc_acm 4-2:1.0: Zero length descriptor references
[ 379.300112] cdc_acm: probe of 4-2:1.0 failed with error -22
[ 379.300134]
Thanks for your fast reply!
On Wed, Jul 12, 2017 at 10:05 AM, Greg KH wrote:
> On Tue, Jul 11, 2017 at 08:10:06PM +0200, Johannes Becker wrote:
>> Hi,
>>
>> I've upgraded my Distro Ubuntu from 14.04 (Kernel 3.13.0) to 16.04
>> (Kernel 4.4.0).
>
> Note, 4.4.0 is _very_ old for us to be dealing wit
Johan Hovold writes:
> On Tue, Jul 11, 2017 at 08:52:37AM +0200, Anatolij Gustschin wrote:
>
>> For devices with connected EEPROM some modes (including UART) are
>> configurable in the EEPROM. For devices without EEPROM the default
>> mode is always UART, but FIFO-, Bitbang- and MPSSE-mode can be
On 7/12/2017 2:06 PM, Baolin Wang wrote:
Hi,
On 12 July 2017 at 15:25, Manu Gautam wrote:
On 7/12/2017 12:19 PM, Baolin Wang wrote:
Hi,
On 3 July 2017 at 19:25, Manu Gautam wrote:
Driver powers-off PHYs and reinitializes DWC3 core and gadget on
resume. While this works fine for gadget m
On Tue, Jul 11, 2017 at 01:32:00PM +0300, Anton Avramov wrote:
> Hello,
>
> I have a new device in my possession that works with usbserial generic
> driver.
> In order for it to work I execute:
> modprobe usbserial
> echo fff0 0100 > /sys/bus/usb-serial/drivers/generic/new_id
>
> I'm writing
On Tue, Jul 11, 2017 at 08:52:37AM +0200, Anatolij Gustschin wrote:
> On Mon, 10 Jul 2017 14:34:27 +0200
> Johan Hovold jo...@kernel.org wrote:
>
> >On Fri, Jul 07, 2017 at 11:53:29AM +0200, Anatolij Gustschin wrote:
> >> On Fri, 07 Jul 2017 09:48:48 +0200
> >> Bjørn Mork bj...@mork.no wrote:
> >>
Hi,
On 12 July 2017 at 15:25, Manu Gautam wrote:
>
>
> On 7/12/2017 12:19 PM, Baolin Wang wrote:
>>
>> Hi,
>>
>> On 3 July 2017 at 19:25, Manu Gautam wrote:
>>>
>>> Driver powers-off PHYs and reinitializes DWC3 core and gadget on
>>> resume. While this works fine for gadget mode but in host
>>>
On Tue, Jul 11, 2017 at 08:10:06PM +0200, Johannes Becker wrote:
> Hi,
>
> I've upgraded my Distro Ubuntu from 14.04 (Kernel 3.13.0) to 16.04
> (Kernel 4.4.0).
Note, 4.4.0 is _very_ old for us to be dealing with here, I strongly
suggest you file this in your distro's specific bug tracker, as they
XHCI specification 1.1 does not require xHCI-compliant controllers
to always enable hardware USB2 LPM. However, the current xHCI
driver always enable it when seeing HLC=1.
This patch supports an option for users to control disabling
USB2 Hardware LPM via DT/ACPI attribute.
This option is needed in
Hi, Lu
At 05/05/2017 08:50 PM, Boris Ostrovsky wrote:
On 05/05/2017 01:41 AM, Lu Baolu wrote:
Hi,
On 05/03/2017 06:38 AM, Boris Ostrovsky wrote:
On 03/21/2017 04:01 AM, Lu Baolu wrote:
Add a simple udelay calibration in x86 architecture-specific
boot-time initializations. This will get a wor
"udc->regs" is zero here. We don't set it until a couple lines later.
The intent was to test "udc->virt_addr".
Fixes: 1b9f35adb0ff ("usb: gadget: udc: Add Synopsys UDC Platform driver")
Signed-off-by: Dan Carpenter
diff --git a/drivers/usb/gadget/udc/snps_udc_plat.c
b/drivers/usb/gadget/udc/sn
On 7/12/2017 12:19 PM, Baolin Wang wrote:
Hi,
On 3 July 2017 at 19:25, Manu Gautam wrote:
Driver powers-off PHYs and reinitializes DWC3 core and gadget on
resume. While this works fine for gadget mode but in host
mode there is not re-initialization of host stack. Also, resetting
bus as part
34 matches
Mail list logo
