From: Johan Hovold <johan@kernel.org>
To: Michael Hanselmann <public@hansmi.ch>
Cc: Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org, Michael Dreher <michael@5dot1.de>,
Jonathan Olds <jontio@i4free.co.nz>
Subject: Re: [PATCH v2 6/6] USB: serial: ch341: Simulate break condition if not supported
Date: Mon, 6 Jul 2020 11:31:44 +0200 [thread overview]
Message-ID: <20200706093144.GG3334@localhost> (raw)
In-Reply-To: <f34a9b6e-ec2a-0873-e97b-2d5b2170e2ff@msgid.hansmi.ch>
Hi Michael,
On Sat, Jul 04, 2020 at 08:25:03PM +0200, Michael Hanselmann wrote:
> On 30.06.20 13:39, Johan Hovold wrote:
> > On Thu, May 28, 2020 at 12:21:11AM +0200, Michael Hanselmann wrote:
> Updated patch included below.
>
> Michael
>
> ---
When sending patches inline like this, try to avoid adding a (---)
marker like this as it makes git-am discard the commit message when
applying.
> From 41b8b06d343a69541a357d8c9d6d0fe3f22610d6 Mon Sep 17 00:00:00 2001
> Message-Id: <41b8b06d343a69541a357d8c9d6d0fe3f22610d6.1593887001.git.public@hansmi.ch>
> From: Michael Hanselmann <public@hansmi.ch>
> Date: Thu, 5 Mar 2020 01:50:35 +0100
> Subject: [PATCH] USB: serial: ch341: Simulate break condition if not supported
>
> A subset of all CH341 devices don't support a real break condition. This
> fact is already used in the "ch341_detect_quirks" function. With this
> change a quirk is implemented to simulate a break condition by
> temporarily lowering the baud rate and sending a NUL byte.
>
> The primary drawbacks of this approach are that the duration of the
> break can't be controlled by userland and that data incoming during
> a simulated break is corrupted.
>
> The "TTY_DRIVER_HARDWARE_BREAK" serial driver flag was investigated as
> an alternative. It's a driver-wide flag and would've required
> significant changes to the serial and USB-serial driver frameworks to
> expose it for individual USB-serial adapters.
>
> Tested by sending a break condition and watching the TX pin using an
> oscilloscope.
>
> Signed-off-by: Michael Hanselmann <public@hansmi.ch>
Now applied with a slightly condensed probe info message.
Thanks,
Johan
next prev parent reply other threads:[~2020-07-06 9:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 23:37 [PATCH v2 0/6] USB: serial: ch341: Add support for limited chips (was: Add support for HL340 devices) Michael Hanselmann
2020-03-31 23:37 ` [PATCH v2 1/6] USB: serial: ch341: Reduce special cases in clock calculation Michael Hanselmann
2020-03-31 23:37 ` [PATCH v2 2/6] USB: serial: ch341: Add basis for quirk detection Michael Hanselmann
2020-05-14 14:09 ` Johan Hovold
2020-03-31 23:37 ` [PATCH v2 3/6] USB: serial: ch341: Limit prescaler on quirky chips Michael Hanselmann
2020-05-14 14:17 ` Johan Hovold
2020-05-27 13:16 ` Johan Hovold
2020-05-27 15:41 ` Michael Hanselmann
2020-05-29 7:15 ` Johan Hovold
2020-03-31 23:37 ` [PATCH v2 4/6] USB: serial: ch341: Name prescaler, divisor registers Michael Hanselmann
2020-05-14 14:24 ` Johan Hovold
2020-05-27 20:59 ` Michael Hanselmann
2020-06-29 9:51 ` Johan Hovold
2020-03-31 23:37 ` [PATCH v2 5/6] USB: serial: ch341: Compute minimum baud rate Michael Hanselmann
2020-05-27 22:19 ` Michael Hanselmann
2020-06-30 9:57 ` Johan Hovold
2020-03-31 23:37 ` [PATCH v2 6/6] USB: serial: ch341: Simulate break condition if not supported Michael Hanselmann
2020-05-14 14:47 ` Johan Hovold
2020-05-27 22:21 ` Michael Hanselmann
2020-06-30 11:39 ` Johan Hovold
2020-07-04 18:25 ` Michael Hanselmann
2020-07-06 9:31 ` Johan Hovold [this message]
2020-05-14 14:02 ` [PATCH v2 0/6] USB: serial: ch341: Add support for limited chips (was: Add support for HL340 devices) Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200706093144.GG3334@localhost \
--to=johan@kernel.org \
--cc=jontio@i4free.co.nz \
--cc=linux-usb@vger.kernel.org \
--cc=michael@5dot1.de \
--cc=public@hansmi.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).