From: "Thang Q. Nguyen"
For commit 4c39d4b949d3 ("usb: xhci: use bus->sysdev for DMA
configuration"), sysdev points to devices known to the system firmware
or hardware for DMA parameters.
However, the parent of the system firmware/hardware device checking
logic does not work in
If the clock handle is given in the DT, it means the clock is required
for proper operation of the PHY. In that case a failure to obtain the
clock must be propagated to stop the driver from probing. This fixes
working with clocks, which request probe deferral.
Signed-off-by: Lucas Stach
On Fri, Aug 18, 2017 at 12:40:47PM +, Joakim Tjernlund wrote:
> I have two USB head sethead (Logitech Inc Logitech Stereo H650e and
> Jabra Jabra UC VOICE 550a) who both causes lots of:
>
> usb 1-2: 1:1: cannot set freq 44100 to ep 0x81
>
> errors when using them pin pidgin audio chats.
Felipe Balbi wrote at Friday, August 18, 2017 3:30 AM:
> Hi,
>
> kbuild test robot writes:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> > testing/next
> > head: 862b43460309779e5814616a68aa36d29a70d6e0
> > commit:
On 15.08.2017 18:58, Oliver Neukum wrote:
Am Dienstag, den 15.08.2017, 16:38 +0300 schrieb Anton Volkov:
On 15.08.2017 16:20, Oliver Neukum wrote:
Am Dienstag, den 15.08.2017, 15:59 +0300 schrieb Anton Volkov:
Hello.
While searching for races in the Linux kernel I've come across
On 16.08.2017 05:15, Lu Baolu wrote:
Hi,
On 08/15/2017 07:30 PM, Mathias Nyman wrote:
On 11.08.2017 05:41, Lu Baolu wrote:
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI
I have two USB head sethead (Logitech Inc Logitech Stereo H650e and
Jabra Jabra UC VOICE 550a) who both causes lots of:
usb 1-2: 1:1: cannot set freq 44100 to ep 0x81
errors when using them pin pidgin audio chats.
I found that adding a small delay here:
diff -u sound/usb/clock.c.org
On 17.08.2017 06:19, Thang Q. Nguyen wrote:
On Tue, Aug 8, 2017 at 11:27 AM, Thang Q. Nguyen wrote:
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
Hi,
kbuild test robot writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> testing/next
> head: 862b43460309779e5814616a68aa36d29a70d6e0
> commit: 2b4e4d3c929db0fc7cf99212bfac0570b6902c14 [48/49] usb: gadget: serial:
> fix oops when data
tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
testing/next
head: 862b43460309779e5814616a68aa36d29a70d6e0
commit: 2b4e4d3c929db0fc7cf99212bfac0570b6902c14 [48/49] usb: gadget: serial:
fix oops when data rx'd after close
config: xtensa-allmodconfig (attached as .config)
Hi,
Kai-Heng Feng writes:
>>> When plugging Logitech C920 webcam, warning messages filled up dmesg:
>>> [77117.655018] xhci_hcd :0c:00.0: WARN Successful completion on short
>>> TX: needs XHCI_TRUST_TX_LENGTH quirk?
>>> [77117.659018] xhci_hcd :0c:00.0:
Hi,
On Fri, Aug 18, 2017 at 3:22 PM, Felipe Balbi
wrote:
>
> hi,
>
> Kai-Heng Feng writes:
>> When plugging Logitech C920 webcam, warning messages filled up dmesg:
>> [77117.655018] xhci_hcd :0c:00.0: WARN Successful completion on
Hi,
Rail Shafigulin writes:
> 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
the list is open to anybody and we welcome newcomers :-)
> online for
hi,
Kai-Heng Feng writes:
> When plugging Logitech C920 webcam, warning messages filled up dmesg:
> [77117.655018] xhci_hcd :0c:00.0: WARN Successful completion on short TX:
> needs XHCI_TRUST_TX_LENGTH quirk?
> [77117.659018] xhci_hcd :0c:00.0: WARN
Hi,
On 8/15/2017 2:44 AM, Jerry Zhang wrote:
> 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
15 matches
Mail list logo