Hello Felix Hädicke,
The patch 54dfce6d07b0: "usb: gadget: f_fs: handle control requests
not directed to interface or endpoint" from Jun 22, 2016, leads to
the following static checker warning:
drivers/usb/gadget/function/f_fs.c:3152 ffs_func_req_match()
warn: always true conditio
On Mon, Oct 10, 2016 at 3:39 PM, Martyn Welch
wrote:
> This patch adds support for the GPIO found on the CP2105. Unlike the GPIO
> provided by some of the other devices supported by the cp210x driver, the
> GPIO on the CP2015 is muxed on pins otherwise used for serial control
> lines. The GPIO ha
Hello,
> vdev_to_vhci() derefernces "vdev" to get vdev->rhport
Yes, you are right.
Sorry about my misreading.
I'm creating the patch and will send later.
Thank you for your help,
n.iwata
//
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Wednesday,
Hi Bastien,
On 12/10/16 07:10, Bastien Nocera wrote:
> Hey,
>
> I recently bought some cheap USB soundcards for a computer that doesn't
> have any audio output other than through the HDMI output, and the
> screen I'm attaching doesn't have an audio output.
>
> So I'm looking to plug in 2 of thos
On Wed, 2016-10-12 at 11:14 +0200, Felipe Ferreri Tonello wrote:
>
> What you need is PulseAudio server instead. PulseAudio supports this
> via
> kcontrol for quite some time.
>
> Jack is supposed to be a low-latency audio server for audio
> applications, not for normal desktop usage.
I'm not t
Hi,
Am Dienstag, 20. September 2016, 11:36:41 CEST schrieb Peter Chen:
> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices.
>
> This power sequence is hard
On Oct 12 2016 14:10, Bastien Nocera wrote:
> My questions are:
> - does the USB audio driver support jack sensing?
> - is this something standard that's just not implemented yet? In which
> case, I'd be up for at least trying, given specs.
> - or is it something that depends on the device, and in
On Wed, 2016-10-12 at 19:36 +0900, Takashi Sakamoto wrote:
> On Oct 12 2016 14:10, Bastien Nocera wrote:
> > My questions are:
> > - does the USB audio driver support jack sensing?
> > - is this something standard that's just not implemented yet? In
> > which
> > case, I'd be up for at least trying
On Wed, Oct 12, 2016 at 05:24:31AM +, fx IWATA NOBUO wrote:
> Hello,
>
> I will send a patch to clear this warning.
>
> The current behavior is as following:
> vdev_to_vhci() is inline of container_of().
> A pointer (struct vhci_hcd *vhci) may be container_of() from NULL for a
> while.
> If i
When we change the USB function with configfs frequently, sometimes it will
hang the system to crash. The reason is the gadget driver can not hanle the
end transfer complete event after free the gadget irq (since the xHCI will
share the same interrupt number with gadget, thus when free the gadget i
Bastien Nocera wrote:
> Looks like whether or not jack sensing works depends on the device
> itself, but there is a mechanism to propagate the change in setup in
> the USB Audio 2.0 spec
Some recent Windows 10 beta added partial support for USB Audio 2.0.
Earlier Windowses implement only USB Audio
Hi Bastien,
On 12/10/16 12:58, Bastien Nocera wrote:
> On Wed, 2016-10-12 at 19:36 +0900, Takashi Sakamoto wrote:
>> On Oct 12 2016 14:10, Bastien Nocera wrote:
>>> My questions are:
>>> - does the USB audio driver support jack sensing?
>>> - is this something standard that's just not implemented
Hi David
On Tue, Oct 11, 2016 at 1:18 AM, David Lechner wrote:
> On 10/07/2016 11:42 AM, ahas...@baylibre.com wrote:
>>
>> From: Axel Haslam
>>
>> Currently requesting the vbus and overcurrent gpio is handled on
>> the board specific file. But this does not play well moving to
>> device tree.
>>
On Wed, 2016-10-12 at 14:43 +0200, Clemens Ladisch wrote:
> Bastien Nocera wrote:
> > Looks like whether or not jack sensing works depends on the device
> > itself, but there is a mechanism to propagate the change in setup
> > in
> > the USB Audio 2.0 spec
>
>
> Some recent Windows 10 beta added
Bastien Nocera wrote:
> On Wed, 2016-10-12 at 14:43 +0200, Clemens Ladisch wrote:
>> Bastien Nocera wrote:
>>> "
>>> A change of state in the audio function is most often caused by a
>>> certain event that takes place. An event can either be user-
>>> initiated
>>> or device-initiated. User-initiat
Hello,
To follow up on the original bug report. I am still experiencing
memory corruption problems in the xhci stack.
One thing I noticed is that the corruption always occur on a secondary
CPU (ie. the stack trace starts on cpu_startup_entry) and it is always
going on when trying to handle an int
Forgot to mention, I just reproduced it on the mainline 4.8.1 kernel.
On Wed, Oct 12, 2016 at 5:13 PM, Alex Damian wrote:
> Hello,
>
> To follow up on the original bug report. I am still experiencing
> memory corruption problems in the xhci stack.
>
> One thing I noticed is that the corruption al
On Wed, 2016-10-12 at 18:06 +0200, Clemens Ladisch wrote:
> Bastien Nocera wrote:
> > On Wed, 2016-10-12 at 14:43 +0200, Clemens Ladisch wrote:
> > > Bastien Nocera wrote:
> > > > "
> > > > A change of state in the audio function is most often caused by
> > > > a
> > > > certain event that takes pl
On Wed, 12 Oct 2016, Pierre de Villemereuil wrote:
> Hi!
>
> I'm sorry, I'm not savvy enough to know what to do with this (I know
> basics on how to code and compile, but I'm no dev). Could someone
> guide me through it?
>
> I gather this patch needs to be applied to some kernel module code
>
Brauchen Sie einen Kredit? Wenn ja, mailen Sie uns für weitere Informationen.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 10/12/2016 10:01 AM, Axel Haslam wrote:
I agree that we should use a regulator for the vbus power.
i will make that change. However, im not so sure about using the
regulator for the overcurrent handling. There seems to be no other
driver doing this, and as you mention, we would need to chang
Member @mem in struct dwc3 is not used in any places. Clean up it.
Signed-off-by: Lu Baolu
---
drivers/usb/dwc3/core.c | 1 -
drivers/usb/dwc3/core.h | 3 ---
2 files changed, 4 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index 7287a76..3dc535a 100644
--- a/drive
On Wed, Oct 12, 2016 at 12:30:29PM +0200, Heiko Stuebner wrote:
> Hi,
>
> Am Dienstag, 20. September 2016, 11:36:41 CEST schrieb Peter Chen:
> > We have an well-known problem that the device needs to do some power
> > sequence before it can be recognized by related host, the typical
> > example li
For the usb31 IP and from version 2.90a of the usb3 IP, the core
supports HW exit from L1 in HS. Enable it, otherwise the controller may
never exit from LPM to do a transfer.
Signed-off-by: John Youn
---
drivers/usb/dwc3/core.c | 10 ++
drivers/usb/dwc3/core.h | 4
2 files changed,
This patch fixes possibility of dereference by NULLL pointer in "[PATCH
v5 1/3] usbip: vhci extension: modifications to vhci driver" which has
been merged to 4.9-rc1. It occurs when a URB with pointer to invalid
USB/IP device is enqueued in race condition against detach operation.
A pointer was
rds 'device-side' and 'application-side' are used in
documentations as needed for clarity.
---
Version information
This series is divided from "USB/IP over WebSocket" patch set.
Rest of the set will be sent as another series.
v12)
# Recreated based on linux-next 20
usbip_get_device() method in usbip_host_driver_ops was not used. It is
modified as a function to find an exported device for new operations
'connect' and 'disconnect'.
bind and unbind function are exported for the new operations.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/libsrc/usbip_hos
Modification to export and un-export response in
tools/usb/usbip/src/usbip_network.h. It just changes return code type
from int to uint32_t as same as other responses.
Added export and un-export request/response to
Documentation/usb/usbip_protocol.txt.
Signed-off-by: Nobuo Iwata
---
Document
New connect operation.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/src/Makefile.am | 3 +-
tools/usb/usbip/src/usbip.c | 9 +-
tools/usb/usbip/src/usbip.h | 5 +-
tools/usb/usbip/src/usbip_connect.c | 228
4 files changed, 242 insertions(
New disconnect operation.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/src/Makefile.am| 2 +-
tools/usb/usbip/src/usbip.c| 6 +
tools/usb/usbip/src/usbip.h| 2 +
tools/usb/usbip/src/usbip_disconnect.c | 215 +
4 files changed, 224 i
New application(vhci)-side daemon.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/libsrc/vhci_driver.c | 19 +++
tools/usb/usbip/libsrc/vhci_driver.h | 1 +
tools/usb/usbip/src/Makefile.am | 7 +-
tools/usb/usbip/src/usbipd.c | 12 +-
tools/usb/usbip/src/usbipd_app.c | 242
Refactoring to attach and detatch operation. Common parts to new
application(vhci)-side daemon are moved to libsrc/vhci_driver.c.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/libsrc/vhci_driver.c | 99
tools/usb/usbip/libsrc/vhci_driver.h | 6 +-
tools/usb/usbip
Correction to wording inconsistency around import and export in
usbip_list.c.
Please, see also cover letter about wording.
Signed-off-by: Nobuo Iwata
---
tools/usb/usbip/src/usbip_list.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/tools/usb/usbi
This patch adds function and usage of new connect operation, disconnect
operation and application(vhci)-side daemon to README and manuals.
At this point, the wording, 'server' and 'client' are ambiguous in
several place.
For existing attach command, the daemon runs device side machine and
atta
Refactoring to the daemon.
usbipd_dev.c is device-side specific code extracted from usbipd.c.
usbipd.c is left as common parts for both device(stub)-side and
application(vhci)-side daemon.
usbip_net_set_nodelay() is the middle of device side daemon operation
and it does not make mush sence. In
Thanks for your interest in this matter.
If it's ok, I will update in this document collected related
information about interactive whiteboards:
https://docs.google.com/document/d/18028I8M8el_iJGb3hk3WDxQ8m642Li_yeLeuwD1lL1E/edit?usp=sharing
2016-10-11 8:49 GMT+02:00 Greg KH :
> On Mon, Oct 10,
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Oct 13, 2016 at 07:3
Hi,
(please avoid top-posting, see: http://daringfireball.net/2007/07/on_top)
Alex Damian writes:
> Forgot to mention, I just reproduced it on the mainline 4.8.1 kernel.
>
> On Wed, Oct 12, 2016 at 5:13 PM, Alex Damian wrote:
>> Hello,
>>
>> To follow up on the original bug report. I am still
38 matches
Mail list logo
