Aaron Thompson writes:
> I have a Moschip 7703 USB to single serial port adapter that I'm not
> using primarily because it doesn't have an in-tree driver, so I'd be
> happy to send it to anyone who would like to add support for it. It
> looks like it should be easy to add to the existing mos7720
Hi Heikki,
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org
> On Behalf Of Heikki Krogerus
> Sent: Monday, September 23, 2019 6:31 AM
> To: Ajay Gupta
> Cc: linux-usb@vger.kernel.org
> Subject: [RFC PATCH] usb: typec: ucsi: ccg: Remove run_isr flag
>
> There is no need to tr
* Yegor Yefremov [190821 01:24]:
> I'm moving our systems to the recent kernel and have encountered an
> older musb issue [1] that occurs with some 3G/4G modems. In this case
> it is SIMCom 7600G-H. After this dump occurs the modem is still
> working though.
>
> [ 45.585644] [ cut
The Rio500 kernel driver has not been used by Rio500 owners since 2001
not long after the rio500 project added support for a user-space USB stack
through the very first versions of usbdevfs and then libusb.
Support for the kernel driver was removed from the upstream utilities
in 2008:
https://gitl
On Mon, Sep 23 2019, Johan Hovold wrote:
> That's correct, the driver does not support software flow control even
> if the hardware seems to have some support for assisted XON/XOFF.
>
> Would you mind testing the below patch which may be enough to turn
> sw-flow control always on. If that works, I
On 18.9.2019 12.41, Rick Tseng wrote:
NVIDIA 3.1 xHCI card would lose power when moving power state into D3Cold.
Thus we need to wait CNR bit to clear when xhci resmue as xhci init.
Signed-off-by: Rick Tseng
Thanks, added to queue.
Did minor changes to commit message and comment
-Mathias
Hello,
just by looking at appledisplay_probe() I would say that the problem here is
that usb_submit_urb() is called while the probe function can still fail. If it
fails after submitting the urb the work item could already been scheduled from
appledisplay_complete() and therefore operates on fre
On Fri, 20 Sep 2019, David Heinzelmann wrote:
> On Fri, Sep 20, 2019 at 02:15:38PM +0200, Greg KH wrote:
> > On Fri, Sep 20, 2019 at 03:17:26PM +0200, David Heinzelmann wrote:
> > > Hi,
> > >
> > > sorry for the wrong patch format.
> >
> > No problem, that's normal. But please do not top-post o
On 23.9.2019 16.58, Bill Kuzeja wrote:
The system can hit a deadlock if an xhci adapter breaks while initializing.
The deadlock is between two threads: thread 1 is tearing down the
adapter and is stuck in usb_unlocked_disable_lpm waiting to lock the
hcd->handwidth_mutex. Thread 2 is holding this
The system can hit a deadlock if an xhci adapter breaks while initializing.
The deadlock is between two threads: thread 1 is tearing down the
adapter and is stuck in usb_unlocked_disable_lpm waiting to lock the
hcd->handwidth_mutex. Thread 2 is holding this mutex (while still trying
to add a usb de
On 23.9.2019 14.19, Mathias Nyman wrote:
On 19.9.2019 16.59, Suwan Kim wrote:
On Thu, Sep 19, 2019 at 05:54:25PM +0800, Peter Chen wrote:
On 17.9.2019 12.55, Peter Chen wrote:
I met "event ring full error" like below, this error is met when
I do iozone test on UAS storage at v4.19.35 kernel,
There is no need to try to prevent the extra ucsi_notify()
that runtime resuming the device will cause.
This fixes potential deadlock. Both ccg_read() and
ccg_write() are called with the mutex already taken at least
from ccg_send_command(). In ccg_read() and ccg_write, the
mutex is only acquired s
On Mon, Sep 23, 2019 at 06:35:19PM +0800, Charles Yeh wrote:
> Johan Hovold 於 2019年9月23日 週一 下午6:24寫道：
> > That looks much better. But please move the reset defines above the
> > flow control ones to keep the registers sorted by address (0x7 < 0xa).
>
> Thank you for your reply
>
> Charles Ans:
>
On 19.9.2019 16.59, Suwan Kim wrote:
On Thu, Sep 19, 2019 at 05:54:25PM +0800, Peter Chen wrote:
On 17.9.2019 12.55, Peter Chen wrote:
I met "event ring full error" like below, this error is met when
I do iozone test on UAS storage at v4.19.35 kernel, but not meet
this error at linux-next tree
Hi Alex,
alex zheng writes:
>> > I am a user of dwc3 USB host controller, I found there are some
>> > confused behavior of trb event on this controller.
>> > When I run a raw USB data transfer(run bulk in&out transfer with
>> > libusb) and iperf3(over rndis) at the same time,
>> > there are som
Johan Hovold 於 2019年9月23日 週一 下午6:24寫道：
> That looks much better. But please move the reset defines above the
> flow control ones to keep the registers sorted by address (0x7 < 0xa).
Thank you for your reply
Charles Ans:
The new define is follows
#define PL2303_READ_TYPE_HX_STATUS0x8080
#de
On Wed, Jul 24, 2019 at 03:09:39PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Jun 27, 2019 at 03:15:10AM +, Peter Chen wrote:
> >
> > > On 19-06-26 02:40, Peter Chen wrote:
> > > >
> > > > > Subject: [PATCH] ARM: imx25: provide a fixed regulator for usb phys
> > > > >
> > > > > The
On Mon, Sep 23, 2019 at 05:53:34PM +0800, Charles Yeh wrote:
> Johan Hovold 於 2019年9月20日 週五 下午3:56寫道：
> > Yes, that's better, but you're mixing register addresses, bit values and
> > masks above. Perhaps things would be more clear if you but a _REG suffix
> > on the register defines and order thin
This patch adds the following Telit FN980 compositions:
0x1050: tty, adb, rmnet, tty, tty, tty, tty
0x1051: tty, adb, mbim, tty, tty, tty, tty
0x1052: rndis, tty, adb, tty, tty, tty, tty
0x1053: tty, adb, ecm, tty, tty, tty, tty
Signed-off-by: Daniele Palmas
---
Sorry, forgot to add Signed-off-b
On Fri, Sep 20, 2019 at 02:49:51PM -0500, John Goerzen wrote:
> Hello,
>
> I have narrowed down the issue I'm about to describe to keyspan.c; a
> Digi Edgeport/1 with identical configuration works fine.
>
> I am configuring a Raspberry Pi running 4.19.66 (though keyspan.c hasn't
> changed since 2
On 23.9.2019 10.08, alex zheng wrote:
Hi, balbi,
Thank you for your reply~
Felipe Balbi 于2019年9月23日周一 下午1:36写道：
Hi,
(it helps when you Cc correct maintainers ;-)
alex zheng writes:
Hi all,
I am a user of dwc3 USB host controller, I found there are some
confused behavior of trb event o
On Mon, Sep 23, 2019 at 11:51:42AM +0200, Daniele Palmas wrote:
> This patch adds the following Telit FN980 compositions:
>
> 0x1050: tty, adb, rmnet, tty, tty, tty, tty
> 0x1051: tty, adb, mbim, tty, tty, tty, tty
> 0x1052: rndis, tty, adb, tty, tty, tty, tty
> 0x1053: tty, adb, ecm, tty, tty, tt
Johan Hovold 於 2019年9月20日 週五 下午3:56寫道：
> Yes, that's better, but you're mixing register addresses, bit values and
> masks above. Perhaps things would be more clear if you but a _REG suffix
> on the register defines and order things as follows:
>
> #define PL2303_HXN__REG 0
This patch adds the following Telit FN980 compositions:
0x1050: tty, adb, rmnet, tty, tty, tty, tty
0x1051: tty, adb, mbim, tty, tty, tty, tty
0x1052: rndis, tty, adb, tty, tty, tty, tty
0x1053: tty, adb, ecm, tty, tty, tty, tty
---
Hi Johan,
following the output of usb-devices for the compositio
On Wed, Aug 28, 2019 at 4:43 PM Rafael J. Wysocki wrote:
> > I'll report it to the vendor,
>
> Yes, please. At least try to get the information on what the exact
> platform expectations with respect to the OS are. Quite evidently,
> they aren't just "do the usual thing".
AMD's response was:
>
Hi, balbi,
Thank you for your reply~
Felipe Balbi 于2019年9月23日周一 下午1:36写道：
>
>
> Hi,
>
> (it helps when you Cc correct maintainers ;-)
>
> alex zheng writes:
>
> > Hi all,
> >
> > I am a user of dwc3 USB host controller, I found there are some
> > confused behavior of trb event on this controlle
26 matches
Mail list logo
