From: Johan Hovold <johan@kernel.org>
To: "Ji-Ze Hong \(Peter Hong\)" <hpeter@gmail.com>
Cc: peter_hong@fintek.com.tw, johan@kernel.org,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Ji-Ze Hong \(Peter Hong\)" <hpeter+linux_kernel@gmail.com>,
Oliver Neukum <oneukum@suse.com>
Subject: [V3,1/3] USB: serial: f81232: clear overrun flag
Date: Fri, 29 Mar 2019 15:40:51 +0100 [thread overview]
Message-ID: <20190329144051.GA12562@localhost> (raw)
On Fri, Mar 29, 2019 at 04:28:40PM +0800, Ji-Ze Hong (Peter Hong) wrote:
> The F81232 will report data and LSR with bulk like following format:
> bulk-in data: [LSR(1Byte)+DATA(1Byte)][LSR(1Byte)+DATA(1Byte)]...
>
> LSR will auto clear frame/parity/break error flag when reading by H/W,
> but overrrun will only cleared when reading LSR. So this patch add a
> worker to read LSR when overrun and flush the worker on close() &
> suspend().
>
> Cc: Oliver Neukum <oneukum@suse.com>
> Signed-off-by: Ji-Ze Hong (Peter Hong) <hpeter+linux_kernel@gmail.com>
> ---
What changed since v2? Please always make sure to include a changelog
here below the cut-off line.
Thanks,
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
Cc: peter_hong@fintek.com.tw, johan@kernel.org,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Ji-Ze Hong (Peter Hong)" <hpeter+linux_kernel@gmail.com>,
Oliver Neukum <oneukum@suse.com>
Subject: Re: [PATCH V3 1/3] USB: serial: f81232: clear overrun flag
Date: Fri, 29 Mar 2019 15:40:51 +0100 [thread overview]
Message-ID: <20190329144051.GA12562@localhost> (raw)
In-Reply-To: <1553848122-1227-1-git-send-email-hpeter+linux_kernel@gmail.com>
On Fri, Mar 29, 2019 at 04:28:40PM +0800, Ji-Ze Hong (Peter Hong) wrote:
> The F81232 will report data and LSR with bulk like following format:
> bulk-in data: [LSR(1Byte)+DATA(1Byte)][LSR(1Byte)+DATA(1Byte)]...
>
> LSR will auto clear frame/parity/break error flag when reading by H/W,
> but overrrun will only cleared when reading LSR. So this patch add a
> worker to read LSR when overrun and flush the worker on close() &
> suspend().
>
> Cc: Oliver Neukum <oneukum@suse.com>
> Signed-off-by: Ji-Ze Hong (Peter Hong) <hpeter+linux_kernel@gmail.com>
> ---
What changed since v2? Please always make sure to include a changelog
here below the cut-off line.
Thanks,
Johan
next reply other threads:[~2019-03-29 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 14:40 Johan Hovold [this message]
2019-03-29 14:40 ` [PATCH V3 1/3] USB: serial: f81232: clear overrun flag Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2019-03-29 8:28 [V3,3/3] USB: serial: f81232: implement break control Ji-Ze Hong (Peter Hong)
2019-03-29 8:28 ` [PATCH V3 3/3] " Ji-Ze Hong (Peter Hong)
2019-03-29 8:28 [V3,2/3] USB: serial: f81232: add high baud rate support Ji-Ze Hong (Peter Hong)
2019-03-29 8:28 ` [PATCH V3 2/3] " Ji-Ze Hong (Peter Hong)
2019-03-29 8:28 [V3,1/3] USB: serial: f81232: clear overrun flag Ji-Ze Hong (Peter Hong)
2019-03-29 8:28 ` [PATCH V3 1/3] " Ji-Ze Hong (Peter Hong)
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=20190329144051.GA12562@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hpeter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=peter_hong@fintek.com.tw \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.