[PATCH V3] usbcore: Select only first configuration for non-UAC3 compliant devices

From: Saranya Gopal In most of the UAC1 and UAC2 audio devices, the first configuration is most often the best configuration. However, with recent patch to support UAC3 configuration, second configuration was unintentionally chosen for some of the UAC1/2 devices that had more than one configurati

Re: [PATCH V2] usbcore: Select only first configuration for non-UAC3 compliant devices

Hi Saranya On Sun, 6 Jan 2019 at 04:41, wrote: > > From: Saranya Gopal > > In most of the UAC1 and UAC2 audio devices, the first > configuration is most often the best configuration. > However, with recent patch to support UAC3 configuration, > second configuration was unintentionally chosen for

[PATCH V2] usbcore: Select only first configuration for non-UAC3 compliant devices

From: Saranya Gopal In most of the UAC1 and UAC2 audio devices, the first configuration is most often the best configuration. However, with recent patch to support UAC3 configuration, second configuration was unintentionally chosen for some of the UAC1/2 devices that had more than one configurati

[PATCH] [V2] usb: chipidea: add a check for the availability of next child

of_get_next_available_child returns NULL when no child nodes are found. The fix checks its return value instead of assuming a child is found. Signed-off-by: Aditya Pakki --- drivers/usb/chipidea/ci_hdrc_msm.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/usb/chipidea/ci_hdrc_ms

Re: [PATCH] usbcore: Select only first configuration for non-UAC3 compliant devices

On Sat, Jan 05, 2019 at 07:32:37PM +0530, saranya.go...@intel.com wrote: > From: Saranya Gopal > > In most of the UAC1 and UAC2 audio devices, the first > configuration is most often the best configuration. > However, with recent patch to support UAC3 configuration, > second configuration was uni

Re: r8152: data corruption in various scenarios

On 2019-01-05 9:14 a.m., Mark Lord wrote: > A couple of years back, I reported data corruption resulting from > a change in kernel 3.16 which enabled hardware checksums in the r8152 driver. > This was happening on an embedded system that was using a r8152 USB dongle. > > At the time, it was very d

r8152: data corruption in various scenarios

A couple of years back, I reported data corruption resulting from a change in kernel 3.16 which enabled hardware checksums in the r8152 driver. This was happening on an embedded system that was using a r8152 USB dongle. At the time, it was very difficult to figure out what could possibly be causin

RE: [alsa-devel] ALSA:usb audio Higher sample rates on usb audio no longer working.

Hi Con, Thanks a lot for reporting the issue and also for taking your time to help me with lsusb output and dmesg logs. I have sent a patch in another mail to fix this issue. Could you help by checking if the patch fixes this issue for you? Thanks, Saranya > -Original Message- > From: C

[PATCH] usbcore: Select only first configuration for non-UAC3 compliant devices

From: Saranya Gopal In most of the UAC1 and UAC2 audio devices, the first configuration is most often the best configuration. However, with recent patch to support UAC3 configuration, second configuration was unintentionally chosen for some of the UAC1/2 devices that had more than one configurati

[PATCH] cdc_ether: trivial whitespace readability fix

This function is unreadable enough without indenting mismatches and unnecessary line breaks. Signed-off-by: Bjørn Mork --- drivers/net/usb/cdc_ether.c | 26 +++--- 1 file changed, 11 insertions(+), 15 deletions(-) diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cd

Re: [PATCH lora-next 3/5] net: lora: sx130x: Add PicoCell serdev driver

Hi, On 04/01/2019 20:21, Andreas Färber wrote: The picoGW reference MCU firmware implements a USB CDC or UART interface with a set of serial commands. It can be found on multiple mPCIe cards as well as USB adapters. https://github.com/Lora-net/picoGW_mcu That MCU design superseded earlier a