Am Mittwoch, den 26.07.2017, 10:05 +0200 schrieb Alan Swanson :
> Similar to commit d595259fbb7a7afed241b1afb2c4fe4b47de47fa for INIC-3169 in
> unusual_devs.h but INIC-3069 already present in unusual_uas.h. Both in same
> controller IC family.
>
> Issue is that MakeMKV fails during key exchange w
Hello!
On 7/26/2017 12:46 AM, Alan Swanson wrote:
Similar to commit d595259fbb7a7afed241b1afb2c4fe4b47de47fa for INIC-3169 in
That's not how you cite a commit -- you should also specify the commit
summary line enclosed in ("") (and 12-digit SHA1 would be enough).
unusual_devs.h but INI
Hi!
> > In v4.9:
> >
> > [ 87.064408] input: Logitech USB Optical Mouse as
> > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1.1/2-1.1.1.1:1.0/0003:046D:C05A.0005/input/input18
> > [ 87.065951] hid-generic 0003:046D:C05A.0005: input,hidraw0: USB HID
> > v1.11 Mouse [Logitech U
Similar to commit d595259fbb7a ("usb-storage: Add ignore-residue quirk for
Initio INIC-3619") for INIC-3169 in unusual_devs.h but INIC-3069 already
present in unusual_uas.h. Both in same controller IC family.
Issue is that MakeMKV fails during key exchange with installed bluray drive
with followin
Hi,
On Wed, Jul 26, 2017 at 11:05:25AM +0800, Baolin Wang wrote:
> On 25 July 2017 at 17:59, Sebastian Reichel
> wrote:
> > On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote:
> >> Integrate with the newly added USB charger interface to limit the current
> >> we draw from the USB input b
On Tue, 25 Jul 2017, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Make usb_hc_died() clear the HCD_FLAG_RH_RUNNING flag for the shared
> HCD and set HCD_FLAG_DEAD for it, in analogy with what is done for
> the primary one.
>
> Among other thigs, this prevents check_root_hub_suspended(
Make sure that the controller is runtime resumed when system suspending
to avoid an external abort when accessing the interrupt registers:
Unhandled fault: external abort on non-linefetch (0x1008) at 0xd025840a
...
[] (musb_default_readb) from []
(musb_disable_interrupts+0x84/0xa8)
[] (mu
This is a v2 of the fix for an external abort during suspend which I submitted
on Monday.
The commit message of patch 1/2 has only been slightly reworded, while
patch 2/2 is new.
Johan
Johan Hovold (2):
USB: musb: fix external abort on suspend
USB: musb: dsps: add explicit runtime resume at
The musb_dsps driver is special in that the parent (glue) device's
driver is accessing registers mapped by the child. The clock is however
shared and is managed by the grandparent device.
Since commit 869c59782981 ("usb: musb: dsps: add support for suspend and
resume") the dsps driver has been acc
On Tue, Jul 25, 2017 at 04:37:00PM +0200, Matthias Holl wrote:
> dear kernel hackers,
>
> with the new kernel 4.13 my optical mouse from pixart dont work
> but i can show it with lsusb
>
> bus 007 device 003: id 093a:2510 pixart imaging,inc optical mouse
>
> i changed nothing in my kernel .conf
On Thu, Jul 13, 2017 at 01:00:29PM -0400, Alan Stern wrote:
> All right. In the meantime, changing usb-storage won't hurt.
> Arthur, can you test the patch below?
Do you plan to send this fix to Greg for 4.13-rc?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body
Christoph Hellwig says that since version 4.12, the kernel switched to
using blk-mq by default. The old code used a softirq for handling
request completions, but blk-mq can handle completions in the caller's
context. This may cause a problem for usb-storage, because it invokes
the ->scsi_done cal
On Wed, 26 Jul 2017, Christoph Hellwig wrote:
> On Thu, Jul 13, 2017 at 01:00:29PM -0400, Alan Stern wrote:
> > All right. In the meantime, changing usb-storage won't hurt.
> > Arthur, can you test the patch below?
>
> Do you plan to send this fix to Greg for 4.13-rc?
I just submitted it.
Alan
On Wednesday, July 26, 2017 10:21:54 AM Alan Stern wrote:
> On Tue, 25 Jul 2017, Rafael J. Wysocki wrote:
>
> > From: Rafael J. Wysocki
> >
> > Make usb_hc_died() clear the HCD_FLAG_RH_RUNNING flag for the shared
> > HCD and set HCD_FLAG_DEAD for it, in analogy with what is done for
> > the prim
[Added linux-usb mailing list to CC:]
Short description of bug: In 4.12 or later, when Zdenek's Western
Digital disk is attached to an EHCI controller, it ends up connecting
at full speed to the companion UHCI controller instead. But when
commit 22547c4cc4fe ("usb: hub: Wait for connection to be
Hey Mathias,
While the oops has been fixed in the latest kernels, as of 4.12.3, I'm
still having issues where USB "stops working" after a while. If I
restart, then after a long while, it stops working again. If I simply
rmmod all the USB-related modules and modprobe xhci_pci, things work
again, bu
xhci_disable_slot() allows the invoker to pass a command pointer
as paramenter. Otherwise, it will allocate one. This will cause
memory leak when a command structure was allocated inside of this
function while queuing command trb fails. Another problem comes up
when the invoker passed a command poi
xhci_disable_slot() is a helper for disabling a slot when a device
goes away or recovers from error situations. Currently, it returns
success when it sees a dead host. This is not the right way to go.
It should return error and let the invoker know that disable slot
command was failed due to a dead
xhci_disable_slot() is a helper for disabling a slot when a device
goes away or recovers from error situations. Currently, it checks
the corespoding virt-dev pointer and returns directly (w/o issuing
disable slot command) if it's null.
This is unnecessary and will cause problems in case where virt
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI specification (section 4.6.5) says: A USB Transaction
Error Completion Code for an Address Device Command may be due
to a Stall response
If xhci_disable_slot() returns success, a disable slot command
trb was queued in the command ring. The command completion
handler will free the virtual device data structure associated
with the slot. On the other hand, when xhci_disable_slot()
returns error, the invokers should take the responsibil
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI specification (section 4.6.5) says: A USB Transaction
Error Completion Code for an Address Device Command may be due
to a Stall response
Hi,
On 26 July 2017 at 20:08, Sebastian Reichel
wrote:
> Hi,
>
> On Wed, Jul 26, 2017 at 11:05:25AM +0800, Baolin Wang wrote:
>> On 25 July 2017 at 17:59, Sebastian Reichel
>> wrote:
>> > On Tue, Jul 25, 2017 at 04:00:01PM +0800, Baolin Wang wrote:
>> >> Integrate with the newly added USB charge
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
This patch introduces the usb charger support based on usb phy that
makes an enhancement to a power driver. The basic conception of the
usb charger is that, when one usb charger is added or removed by
reporting from the extcon device state change, the usb charger will
report to power user to set th
Introducing USB charger type and state definition can help
to support USB charging which will be added in USB phy core.
Signed-off-by: Baolin Wang
---
include/uapi/linux/usb/charger.h | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 include/uapi/linux/
27 matches
Mail list logo
