Hi!
My external USB-Speaker produces the following in the Journal from
systemd-journald
I'm not able to use the Speaker. Wheter ALSA nor pulseaudio can play
anything.
# aplay -l
Liste der Hardware-Geräte (PLAYBACK)
Karte 0: HDMI [HDA Intel HDMI], Gerät 3: HDMI 0 [HDMI 0]
Sub-Ger
CustomWare uses the FTDI VID with custom PIDs for their ShipModul MiniPlex
products.
Signed-off-by: Matthijs Kooijman
---
drivers/usb/serial/ftdi_sio.c | 4
drivers/usb/serial/ftdi_sio_ids.h | 8
2 files changed, 12 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/dr
On 2015-08-02 19:00, Matthijs Kooijman wrote:
CustomWare uses the FTDI VID with custom PIDs for their ShipModul MiniPlex
products.
Signed-off-by: Matthijs Kooijman
---
drivers/usb/serial/ftdi_sio.c | 4
drivers/usb/serial/ftdi_sio_ids.h | 8
2 files changed, 12 insertions(
On Sun, 2 Aug 2015, Jakob Schürz wrote:
> Hi!
>
> My external USB-Speaker produces the following in the Journal from
> systemd-journald
>
> I'm not able to use the Speaker. Wheter ALSA nor pulseaudio can play
> anything.
...
> Aug 02 11:53:17 aldebaran kernel: usb 2-3: new full-speed USB dev
Am 2015-08-02 um 15:58 schrieb Alan Stern:
On Sun, 2 Aug 2015, Jakob Schürz wrote:
Hi!
My external USB-Speaker produces the following in the Journal from
systemd-journald
I'm not able to use the Speaker. Wheter ALSA nor pulseaudio can play
anything.
...
Aug 02 11:53:17 aldebaran kernel: u
Hi Lars,
thanks for your feedback.
> >+{ USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX_PID) },
> >+{ USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2_PID) },
> >+{ USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2WI_PID) },
> >+{ USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX3_PID) },
>
On 2015-08-03 00:07, Matthijs Kooijman wrote:
Hi Lars,
thanks for your feedback.
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2WI_PID) },
+ { USB_DEV
When remove module g_serial on quark platform, the following Warning on:
Modules linked in: usb_f_acm u_serial g_serial(-) pch_udc libcomposite configfs
udc_core
ad7298 industrialio_triggered_buffer kfifo_buf tpm_i2c_infineon indus
CPU: 0 PID: 369 Comm: modprobe Not tainted 3.14.29ltsi-WR7.0.0.0_
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index f0c0c53..6996308 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
@@
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index f0c0c53..6996308 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
@@
The system bus and chipidea IP have different limitations for
both host and device mode.
For example, with below errata, we need to enable SDIS(Stream Disable
Mode) at host mode. But we don't want it for device mode at the
same system.
TAR 9000378958
Title: Non-Double Word Aligned Buffer Address S
The zero-length packet is the sendor tells the receiver that there
is no more data, so it is only needed at the TX side.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/udc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/
With this setting and AHBBRST at SBUSCFG as "Incremental burst of
unspecified length", each non-burst size can be taken as single
transfer. It is benefit for non-burst size transfer.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/usbmisc_imx.c | 12 ++--
1 file changed, 10 insertions
The users can change it through dts or platform data if they
want to change the default value.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/bits.h | 3 +++
drivers/usb/chipidea/core.c | 14 ++
include/linux/usb/chipidea.h | 2 ++
3 files changed, 19 insertions(+)
diff --gi
Stream mode enable is known for better performance, this stream mode
enable patch has been passed with stress tests at device mode for
imx6sl and imx6sx, and no issue is found.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.c | 16 ++--
1 file changed, 10 insertions(+
After setting ahb burst configuration as 0, we can increase tx/rx
burst size, it will improve the USB performance
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi | 4
arch/arm/boot/dts/imx6sl.dtsi | 3 +++
arch/arm/boot/dts/imx6sx.dtsi | 3 +++
3 files changed, 10 insertions(
It is used to change ahb burst configuration for platforms, it is
vendor specific.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b/Documentation/
It is used to override the default setting for burst size, changing
burst size takes effect only when the SBUSCFG.AHBBRST = 0.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/b
It can improve the USB performance when choosing larger
burst size at some systems (bus size is larger), there is
no side effect if this burst size is larger than bus size.
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi | 8
arch/arm/boot/dts/imx6sl.dtsi | 6 ++
arch/
Hi all,
In this series, I add several new interfaces for chipidea driver,
they are mainly for system configuration adjustment. The USB
performance may be improved with these configuration changing,
but each vendor driver owner needs to consult with your IC
owner which configuration parameters are
The user can adjust it through dts or platform data
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/bits.h | 4
drivers/usb/chipidea/ci.h| 1 +
drivers/usb/chipidea/core.c | 35 +++
include/linux/usb/chipidea.h | 4
4 files changed, 44 insert
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Friday, July 31, 2015 10:04 PM
> To: Badola Nikhil-B46172
> Cc: linux-ker...@vger.kernel.org; linux-usb@vger.kernel.org;
> gre...@linuxfoundation.org; Mehresh Ramneek-B31383
> Subject: Re: [PATCH] drivers: us
Hi Lars,
> What I meant is that ...FTDI_C. should come before ...FTDI_S
> and not after, but I've had a look at the whole ftdi_sio.c source
> now and it looks horrible.
> I think it doesn't really matter where you put your additions, do as
> others has done and put them at a random positio
23 matches
Mail list logo
