Hi,
On 10-04-16 00:44, kbuild test robot wrote:
Hi Reinder,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.6-rc2 next-20160408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
As mentioned in the cover letter, these
Grigori Goronzy wrote:
> Changing the LCR register after initialization does not seem to be
> reliable on all chips (particularly not on CH341A). Restructure
> initialization and configuration to always reinit the chip on
> configuration changes instead and pass the LCR register value directly
> t
On 5 April 2016 at 21:34, Jon Mason wrote:
> On Wed, Mar 30, 2016 at 5:32 PM, Jon Mason wrote:
>> On Tue, Mar 29, 2016 at 10:01 AM, Rafał Miłecki wrote:
>>> Northstar is a family of SoCs used in home routers. They have USB 2.0
>>> and 3.0 controllers with PHYs that need to be properly initialize
Hi!
> > It's your HW :-) You tell me if it's really necessary. But, hey, if you
> > get enumerated @500mA, this is the host telling you it _CAN_ give you
> > 500mA. In that case, why wouldn't you ?
Dunno, perhaps not to drain battery in host too quickly?
Or perhaps you are charging from external
Hi!
> >>> +#define DEFAULT_SDP_CUR_LIMIT(500 - DEFAULT_CUR_PROTECT)
> >>
> >> According to the spec we should always be talking about unit loads (1
> >> unit load is 100mA for HS/FS/LS and 150mA for SS). Also, this will not
> >> work for SS capable ports and SS gadgets (we have quite a few
On 2016-04-04 9:06:28, Olliver Schinagl wrote:
> Hi list,
>
> I have a Apple Inc. MacBookPro11,1 (with the most recent 'bios': BIOS
> MBP111.88Z.0138.B16.1509081438 09/08/2015).
> At the beginning, USB worked normally. After a while (and after newer kernel
> versions released by debian?) things s
On Sun, 10 Apr 2016, Sam Sany wrote:
> Alan Stern writes:
>
> >
> > On Sat, 9 Apr 2016, Sam Sany wrote:
>
> > --- usb-3.15.orig/drivers/usb/core/hub.c
> > +++ usb-3.15/drivers/usb/core/hub.c
> > -130,6 +130,8 struct usb_hub
> *usb_hub_to_struct_hub(st
> >
> > static int usb_devic
Alan Stern writes:
>
> On Sun, 10 Apr 2016, Sam Sany wrote:
>
> > Alan Stern ...> writes:
> >
> > >
> > > On Sat, 9 Apr 2016, Sam Sany wrote:
> >
> > > --- usb-3.15.orig/drivers/usb/core/hub.c
> > > +++ usb-3.15/drivers/usb/core/hub.c
> > > -130,6 +130,8 struct usb_hub
> > *usb_
On 04/09/2016 08:00 AM, Alan Stern wrote:
> On Sat, 9 Apr 2016, Sam Sany wrote:
>> I have yet to try the 4.5 kernel. I prefer to use a low-latency kernel, bc
>> the primary purpose of this machine is recording music. So I have been
>> downloading the newest source code available in the Ubuntu S
This may fail, do not assume it always works.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index c73808f..63df8ce 100644
--- a/drivers/usb/serial/ch341.
BREAK2 seems to be a misnomer, the register configures various aspects
of the UART configuration.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial
Use the correct types and sizes.
v2: use u8 shorthand for unsigned char.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index db4b561..95c8a40 10
With the new reinitialization method, configuring parity, different
frame lengths and different stop bit settings work as expected on
both CH340G and CH341A. This has been extensively tested with a
logic analyzer.
v2: only set mark/space when parity is enabled, simplifications,
patch termios HW f
v2: use correct flag variable.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index 94e6016..135370b 100644
--- a/drivers/usb/serial/ch341.c
+++ b/drivers/usb/s
The status bit was found with USB captures of the Windows driver and
some luck. Tested on CH340G and CH341A.
v2: unify general status definitions
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
dif
Hi,
here's a revised v3 of my ch341 patchset sent earlier this month.
Thanks to everyone who provided feedback. Changes compared to the
last submission have been indicated in the commit messages.
Please review.
Best regards
Grigori
--
To unsubscribe from this list: send the line "unsubscribe l
If the serial port hasn't been opened yet, no baud rate should be
set and RTS/DTR need to be deasserted.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index 78590b7..
Check for B0 in a more idiomatic way and make sure to not enable
RTS/CTS hardware flow control in B0 as it may override the control
lines. Also make sure to only enable RTS/DTR if there's a transition
from B0.
v2: use c_cflag macros.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.
Changing the LCR register after initialization does not seem to be
reliable on all chips (particularly not on CH341A). Restructure
initialization and configuration to always reinit the chip on
configuration changes instead and pass the LCR register value directly
to the initialization command.
v2
There are at least two hardware revisions, this may be helpful in
case compatibility issues need to be debugged.
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index 99b4621
No functional change. The following adjustments were made to be more in
line with official coding style and to be more consistent.
Stop mixing tabs and spaces for alignment. Stop putting labels and
statements into the same line. Use braces consistently for a single
statement.
v2: drop most cha
Signed-off-by: Grigori Goronzy
---
drivers/usb/serial/ch341.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
index 1ab4384..db4b561 100644
--- a/drivers/usb/serial/ch341.c
+++ b/drivers/usb/serial/ch341.c
@@ -61,6 +61,
No functional change. Remove explicit function name printing, it's
easy to use dynamic debug to print it every time, if required.
Fix capitalization and phrasing in some cases. Drop useless
information like a USB buffer pointer, which is not helpful.
Signed-off-by: Grigori Goronzy
---
drivers/
On Sun, 10 Apr 2016, Peter Hurley wrote:
> On 04/09/2016 08:00 AM, Alan Stern wrote:
> > On Sat, 9 Apr 2016, Sam Sany wrote:
> >> I have yet to try the 4.5 kernel. I prefer to use a low-latency kernel,
> >> bc
> >> the primary purpose of this machine is recording music. So I have been
> >> do
Hi Grigori,
[auto build test ERROR on v4.5-rc7]
[cannot apply to usb/usb-testing usb-serial/usb-next v4.6-rc2 v4.6-rc1
next-20160408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Grigori-Go
Alan Stern writes:
>
> On Sun, 10 Apr 2016, Peter Hurley wrote:
>
> > On 04/09/2016 08:00 AM, Alan Stern wrote:
> > > On Sat, 9 Apr 2016, Sam Sany wrote:
> > >> I have yet to try the 4.5 kernel. I prefer to use a low-latency
kernel, bc
> > >> the primary purpose of this machine is recording
Hi
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Friday, April 08, 2016 7:51 PM
> To: Jun Li
> Cc: ba...@kernel.org; gre...@linuxfoundation.org; s...@kernel.org;
> dbarysh...@gmail.com; dw...@infradead.org; peter.c...@freescale.com;
> st...@rowland.harva
On Fri, 2016-04-08 at 15:57 +0200, Matthias Brugger wrote:
>
> On 08/04/16 11:13, Chunfeng Yun wrote:
> > A new compatible string, "mediatek,mt2701-u3phy", is added.
> >
> > Some register settings to avoid RX sensitivity level degradation
> > which may arise on mt8173 platform are separated from o
On Fri, 2016-04-08 at 07:07 -0700, Greg Kroah-Hartman wrote:
> On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote:
> > NULL pointer dereferrence will happen when class driver
> > wants to allocate zero length buffer and pool_max[0]
> > can't be used, so skip reserved pool in this case.
>
Sam Sany writes:
No go. Just booted into the newly compiled kernel, and I still have the
exact same symptoms. The edited portion of the hub.c file I used to
compile looks as such:
int usb_device_supports_lpm(struct usb_device *udev)
{
return 0;
/* USB 2.1 (and greater) devic
Sam Sany writes:
Since the dmesg output always prints "usb_set_interface failed" could it have
something to do with the portions of the hub.c file that deal with those
functions? It only occurs twice through out the hub.c file...
--
To unsubscribe from this list: send the line "unsubscribe li
> -Original Message-
> From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> Sent: Friday, April 01, 2016 4:20 PM
> To: Rajesh Bhagat
> Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
> ker...@vger.kernel.org; Sriram Dash
> Subject: Re: [PATCH] usb: xhci: Fix in
Hi,
chunfeng yun writes:
> On Fri, 2016-04-08 at 07:07 -0700, Greg Kroah-Hartman wrote:
>> On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote:
>> > NULL pointer dereferrence will happen when class driver
>> > wants to allocate zero length buffer and pool_max[0]
>> > can't be used, so s
Hi,
Janna Martl writes:
> On 2016-04-04 9:06:28, Olliver Schinagl wrote:
>> Hi list,
>>
>> I have a Apple Inc. MacBookPro11,1 (with the most recent 'bios': BIOS
>> MBP111.88Z.0138.B16.1509081438 09/08/2015).
>> At the beginning, USB worked normally. After a while (and after newer kernel
>> ver
Hi,
John Youn writes:
> Set the reserved fields of the SuperSpeed Plus Device Capability
> descriptor to 0. Otherwise there might be stale data there which will
> cause USB CV to fail.
>
> Fixes: f228a8de242a ("usb: gadget: composite: Return SSP Dev Cap descriptor")
> Signed-off-by: John Youn
>
Hi,
Denys Vlasenko writes:
> This function compiles to 298 bytes of machine code, has ~10 callsites.
fair enough
> This is a USB 2.0 device, USB 2.0 is limited to 35 MB/s, so should be
it's not limited to 35MB/sec, sorry. USB 2.0 has a theoretical maximum
of 60MB/sec. But 44MB/sec is what peo
Hi,
Matthew Giassa writes:
> *Migrating from linux-media mailing list.
>
> Good day,
>
> I maintain an SDK for USB2.0 and USB3.0 U3V machine vision cameras, and
> several of our customers have reported severe issues since upgrading
> from
> kernel 3.19.0-51 (Ubuntu 14.04.3 LTS) to kernel 4.2.0-3
Alan Stern writes:
> On Fri, 8 Apr 2016, Felipe Balbi wrote:
>
>> > Aside from the multi-line comment formatting, you should avoid adding a
>>
>> I can fix the multiline comment style, but I'm merely following what's
>> already in the file. What do people prefer in this case ? How about a
>> patc
Hi Felipe,
On Mon, Apr 11, 2016 at 08:12:16AM +0300, Felipe Balbi wrote:
> > On 2016-04-04 9:06:28, Olliver Schinagl wrote:
> >> It spews some messages in dmesg (taking some 15 seconds) and only then, the
> >> keyboard starts to work again.
>
> which messages ? We need these dmesg messages
Olliv
39 matches
Mail list logo
