On Thu, 29 Jun 2017, Alan Stern wrote:
> 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")
> >
On 06/29/2017 01:03 AM, Tony Lindgren wrote:
> * Vignesh R [170628 21:21]:
>>
>>
>> On Thursday 29 June 2017 05:01 AM, Strashko, Grygorii wrote:
>>> IRQ_NOAUTOEN can't be used with shared IRQs and Kernel now will triggers
>>> warning if it happns, since commit 04c848d39879
"Baxter, Jim" writes:
> I tested this with printk's to show when the low memory code was triggered
> and the value of ctx->tx_low_mem_val and ctx->tx_low_mem_max_cnt.
> I created a workqueue that slowly used up the atomic memory until the
> code is triggered.
>
> I could
> Jim Baxter writes:
>
>> The CDC-NCM driver can require large amounts of memory to create
>> skb's and this can be a problem when the memory becomes fragmented.
>>
>> This especially affects embedded systems that have constrained
>> resources but wish to maximise the
Jim Baxter writes:
> The CDC-NCM driver can require large amounts of memory to create
> skb's and this can be a problem when the memory becomes fragmented.
>
> This especially affects embedded systems that have constrained
> resources but wish to maximise the throughput of
From: David S. Miller (da...@davemloft.net)
Sent: Fri, 30 Jun 2017 12:59:53 -0400
To: jim_bax...@mentor.com
Cc: linux-usb@vger.kernel.org, net...@vger.kernel.org,
linux-ker...@vger.kernel.org, oli...@neukum.org,
From: Jim Baxter
Date: Wed, 28 Jun 2017 21:35:29 +0100
> The CDC-NCM driver can require large amounts of memory to create
> skb's and this can be a problem when the memory becomes fragmented.
>
> This especially affects embedded systems that have constrained
> resources
On Fri, Jun 23, 2017 at 02:58:11PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> pci_target_state() calls device_may_wakeup() which checks whether
> or not the device may wake up the system from sleep states, but
> pci_target_state() is used for
On 06/30/2017 08:46 AM, Arnd Bergmann wrote:
The new driver causes a build failure in some configurations:
In file included from /git/arm-soc/drivers/usb/typec/ucsi/trace.h:9:0,
from /git/arm-soc/drivers/usb/typec/ucsi/trace.c:2:
drivers/usb/typec/ucsi/ucsi.h:331:39: error:
The new driver causes a build failure in some configurations:
In file included from /git/arm-soc/drivers/usb/typec/ucsi/trace.h:9:0,
from /git/arm-soc/drivers/usb/typec/ucsi/trace.c:2:
drivers/usb/typec/ucsi/ucsi.h:331:39: error: 'struct device' declared inside
parameter list
Thanks very much for the response.
My application requires being able to present a very specific list of
devices to a host system I don't fully control, so providing one
device with multiple functions doesn't work in this specific case.
I'll investigate that Aspeed BMC solution.
Thanks again!
On Thu, 29 Jun 2017, Josh Litherland wrote:
> I've been tinkering with developing a USB touchscreen gadget device on
> a board using a Mentor USB peripheral controller (driver musb-hdrc).
> The gadget I'm developing runs in userspace via gadgetfs. From what
> I've been able to tell, there's no
The current HID function driver doesn't support GET_PROCOTOL and
SET_PROCOTOL commands, which are required to operate the HID gadgets in
BOOT mode. This change implements this feature for devices that have
the same implementation for REPORT and BOOT mode
Signed-off-by: Abdulhadi Mohamed
Currently linux HID gadgets do not support remote wakeup (the ability
to wake up a host from suspend). This is an important feature for
gadgets that want to properly emulate the normal operation of a mouse
and keyboard. Ultimately, This feature has to be enabled/supported by
the underlying UDC
On Fri, Jun 30, 2017 at 2:48 PM, Abdulhadi Mohamed
wrote:
> Currently linux HID gadgets do not support remote wakeup (the ability
> to wake up a host from suspend). This is an important feature for
> gadgets that want to properly emulate the normal operation of a mouse
>
On Fri, Jun 30, 2017 at 2:44 PM, Stefan Triller wrote:
> The German Telekom offers a ZigBee USB Stick under the brand name Qivicon
> for their SmartHome Home Base in its 1. Generation. The productId is not
> known by the according kernel module, this patch adds support
Currently linux HID gadgets do not support remote wakeup (the ability
to wake up a host from suspend). This is an important feature for
gadgets that want to properly emulate the normal operation of a mouse
and keyboard. Ultimately, This feature has to be enabled/supported by
the underlying UDC
The German Telekom offers a ZigBee USB Stick under the brand name Qivicon
for their SmartHome Home Base in its 1. Generation. The productId is not
known by the according kernel module, this patch adds support for it.
Signed-off-by: Stefan Triller
---
Hi,
You should probably mention the relevant subsystem in your subject.
On Fri, Jun 30, 2017 at 11:43 AM, Stefan Triller
wrote:
> The german Telekom offers a ZigBee USB Stick under the brand name Qivicon for
> their SmartHome Home Base in its 1. Generation. The
Hi,
On Tue, Jun 27, 2017 at 11:04 PM, Abdulhadi Mohamed
wrote:
> Currently linux HID gadgets do not support remote wakeup (the ability
> to wake up a host from suspend). This is an important feature for gadgets
> that want to properly emulate the normal operation of a
On Fri, Jun 23, 2017 at 4:55 PM, Abdulhadi Mohamed
wrote:
> the current HID function dirver doesn't support GET_PROCOTOL and
> SET_PROCOTOL commands, which are required to operate the HID gadget in
> BOOT mode. This change implements this feature for devices that have
>
Sending v2 of this patch series, including fixes for build regressions
introduced with the original series. I missed the usage of f_uac* in the
legacy modules and did not test that. Fixed now, see patches changelog for
details.
This patch series adds support for exposing multiple supported
Implement support for multiple sampling rates in the USB Audio gadgets.
A list of sampling rates can be specified via configfs. All enabled
sampling rates are sent to the USB host on request. When the host
selects a sampling rate the internal active rate is updated. The
currently configured rates
This replaces the dedicated headers for uac1 and uac2 functions with a
shared header for both of them. Apart from unifying the struct names,
further duplicated code for configfs setup is moved out of the function
files into the shared header.
Signed-off-by: Julian Scheel
---
The endpoint is stored in the lower byte of wIndex, according to USB
Audio 1.0 specification, section 5.2.1.1.
Signed-off-by: Julian Scheel
---
drivers/usb/gadget/function/f_uac1.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
In some MSC CV tests device sending ZLP IN on non EP0 which
reassigning EP0 OUT descriptor pointer to that EP.
Dedicated for EP0 OUT descriptor multiple time re-used by
other EP while that descriptor already in use by EP0 OUT
for SETUP transaction. As result when SETUP packet received
BNA
The german Telekom offers a ZigBee USB Stick under the brand name Qivicon for
their SmartHome Home Base in its 1. Generation. The productId is not known by
the according kernel module, this patch adds support for it.
You can buy the stick here:
This patch adds support for the Qivicon ZigBee USB dongle. Qivicon
is a brand by the german Telekom and they sell this stick for use
with their SmartHome Home Base 1. In order to use this rather
famous stick on regular Linux PCs this patch is neccessary.
You can buy it here:
On Fri, Jun 30, 2017 at 12:37:00AM +0200, Rafael J. Wysocki wrote:
> On Friday, June 23, 2017 02:58:11 PM Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > pci_target_state() calls device_may_wakeup() which checks whether
> > or not the device may wake up
29 matches
Mail list logo