Hi Stephen,
Am 08.11.2015 um 06:06 schrieb Stephen Warren:
On 11/07/2015 05:16 PM, Stefan Wahren wrote:
Hi,
[...]
* phys (optional)
* phy-names (optional)
So here are my questions:
How to fix the kernel oops in dwc2 driver?
Do you know exactly what causes the crash; you've bisected to
Thought it might be useful to include the kernel versions:
usb-host-arch$ uname -a
Linux viii 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015
x86_64 GNU/Linux
usb-gadget-debian(beaglebone black)$ # uname -a
Linux beaglebone 4.1.12-ti-r26 #1 SMP PREEMPT Fri Oct 30 21:28:17 UTC
2015 armv7l
It looks like the ordering may be important.
Configuring uac2 as your first function seems to resolve the issue.
Must be a requirement documented somewhere, or an interesting bug. :)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.k
Chris McClimans writes:
> It looks like the ordering may be important.
> Configuring uac2 as your first function seems to resolve the issue.
> Must be a requirement documented somewhere, or an interesting bug. :)
It's a bug in uac2. It statically sets the IAD bFirstInterface to 0
regardless of
Hi, I have trouble with CP2110 chip (USB-to-serial converter) in kernel,
no /dev/ttyUSBx device created after connection.
I reported this bug https://bugzilla.kernel.org/show_bug.cgi?id=107501
Thanks
Martin Kozelsky
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the b
Hi Ruslan,
On Mon, Nov 02, 2015 at 06:44:00PM +0200, Ruslan Bilovol wrote:
> >> This patchset adds independent registration of gadgets
> >> and gadget drivers to udc-core. This is very useful for
> >> built-in modules into kernel case since it's possible
> >> situation that gadget driver is probin
On 7 November 2015 at 00:56, Greg KH wrote:
> On Fri, Nov 06, 2015 at 07:35:10PM +0800, Baolin Wang wrote:
>> #ifdef CONFIG_HAS_DMA
>> diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
>> index c14a69b..755e8bc 100644
>> --- a/include/linux/usb/gadget.h
>> +++ b/include/
On 11/07/2015 07:05 PM, Steinar H. Gunderson wrote:
Can you cat /sys/bus/usb/devices/2-2/power/usb3_hardware_lpm_u1
>and /sys/bus/usb/devices/2-2/power/usb3_hardware_lpm_u2 for several
>times? Don't use that device when cat these two files.
I waited a bit longer, and indeed, now it consistentl
Hello,
On Fri, Nov 6, 2015 at 12:42 AM, Javi Barroso wrote:
> Hello,
>
> El 6 de noviembre de 2015 0:28:40 CET, Greg KH escribió:
>>On Thu, Nov 05, 2015 at 06:03:15PM +0100, Javier Barroso wrote:
>>> Hello,
>>>
>>> I have a usb stick which was (apparently) broken after plug it on a
>>> usb port
xHCI compatible USB3 host controller may provide debug capability
which enables low-level system debug over USB. In order to probing
this debug capability, Linux kernel needs to map and access the
mmio of the host controller during early boot.
This patch adds permenent fixmap pages in fixed_addres
This patch series adds support for early printk through USB3 debug port.
USB3 debug port is described in xHCI specification as an optional extended
capability.
The first patch adds a file in sysfs, through which users can check
whether the debug capability is supported by a specific host controlle
This patch add dbc debug device support in usb_debug driver.
Signed-off-by: Lu Baolu
Acked-by: Johan Hovold
---
drivers/usb/serial/usb_debug.c | 28 +---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/usb_debug.c b/drivers/usb/serial/us
Add Documentation/usb/xhci-dbc.txt. This document includes
development status and user guide for USB3 debug port.
Signed-off-by: Lu Baolu
---
Documentation/usb/xhci-dbc.txt | 325 +
MAINTAINERS| 1 +
drivers/usb/early/xhci-dbc.c |
Add support for early printk by writing debug messages to the USB3
debug port. Users can use this type of early printk by specifying
kernel parameter of "earlyprintk=xdbc". This gives users a chance
of providing debug output.
Signed-off-by: Lu Baolu
---
Documentation/kernel-parameters.txt | 1 +
This patch adds interfaces for bulk out and bulk in ops. These
interfaces could be used to implement early printk bootconsole
or hook to various system debuggers.
Signed-off-by: Lu Baolu
---
drivers/usb/early/xhci-dbc.c | 373 +++
include/linux/usb/xhci-db
After DbC setup, debug target needs to wait until tty driver and
application (e.g. mincom) on debug taget start. Otherwise, out
messages might be ignored.
This patch adds a ping/pong mechanism between debug target and
host. Debug target will be waiting there until user presses 'Y'
or 'y' in the t
In case of endpoint stall, software is able to detect the situation
by reading DCCTRL.HIT or DCCTRL.HOT bits. DbC follows the normal USB
framework to handle endpoint stall. When software detects endpoint
stall situation, it should wait until endpoint is recovered before
read or write oprations.
Si
DbC might exit configured state in some cases (refer to 7.6.4.4 in
xHCI spec 1.1). Software needs detect and clear this situation by
clearing DCCTRL.DCR and wait until the DbC configured before read
or write oprations.
Signed-off-by: Lu Baolu
---
drivers/usb/early/xhci-dbc.c | 28 +++
xHCI debug capability (DbC) is an optional functionality provided
by an xHCI host controller. Software learns this capability by
walking through the extended capability list in mmio of the host.
This patch introduces the code to probe and initialize the debug
capability hardware during early boot.
On Intel platform, if the debug target is connected with debug
host, enabling DCE bit in command register leads to a hung bus
state. In the hung state, the host system will not see a port
connected status bit set. Hence debug target fails to be probed.
The state could be resolved by performing a p
"printk" is not suitable for dbc debugging especially when console
is in usage. This patch adds a debug buffer in dbc driver and puts
the debug messages in this local buffer. The debug buffer could be
dumped whenever the console is not in use. This part of code will
not be visible unless DBC_DEBUG
This patch adds a sysfs file for users to check 1) whether the debug
capability is implemented by hardware; 2) if supported, which state
does it stay at.
With a host that supports debug port, a file named "debug_port_state"
will be created under the device sysfs directory. Reading this file
will s
22 matches
Mail list logo