From: Paolo Bonzini <pbonzini@redhat.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Ulrich Hecht <uli@fpond.eu>, Rob Landley <rob@landley.net>,
Rich Felker <dalias@libc.org>,
qemu-devel@nongnu.org, linux-renesas-soc@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH qemu v2] hw/char/sh_serial: Add timeout handling to unbreak serial input
Date: Tue, 11 Sep 2018 13:11:44 +0000 [thread overview]
Message-ID: <76422049-ffe3-d4a9-6dcb-8edf05a8e200@redhat.com> (raw)
In-Reply-To: <20180905131125.12635-1-geert+renesas@glider.be>
On 05/09/2018 15:11, Geert Uytterhoeven wrote:
> As of commit 18e8cf159177100e ("serial: sh-sci: increase RX FIFO trigger
> defaults for (H)SCIF") in Linux v4.11-rc1, the serial console on the
> QEMU SH4 target is broken: it delays serial input until enough data has
> been received.
>
> Since aforementioned commit, the Linux SCIF driver programs the Receive
> FIFO Data Count Trigger bits in the FIFO Control Register, to postpone
> generating a receive interrupt until:
> 1. At least the receive trigger count of bytes of data are available
> in the receive FIFO, OR
> 2. No further data has been received for at least 15 etu after the
> last received data.
>
> While QEMU implements the former, it does not implement the latter.
> Hence the receive interrupt is not generated until the former condition
> is met.
>
> Fix this by adding basic timeout handling. As the QEMU SCIF emulation
> ignores any serial speed programming, the timeout value used conforms to
> a default speed of 9600 bps, which is fine for any interactive console.
>
> Reported-by: Rob Landley <rob@landley.net>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Tested-by: Ulrich Hecht <uli@fpond.eu>
> Tested-by: Rob Landley <rob@landley.net>
> Tested-by: Rich Felker <dalias@libc.org>
> ---
> v2:
> - Add Tested-by,
> - Fix spelling in patch description.
> ---
> hw/char/sh_serial.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/hw/char/sh_serial.c b/hw/char/sh_serial.c
> index 373a40595fd975d1..12831561a6c8b137 100644
> --- a/hw/char/sh_serial.c
> +++ b/hw/char/sh_serial.c
> @@ -29,6 +29,7 @@
> #include "hw/sh4/sh.h"
> #include "chardev/char-fe.h"
> #include "qapi/error.h"
> +#include "qemu/timer.h"
>
> //#define DEBUG_SERIAL
>
> @@ -63,6 +64,8 @@ typedef struct {
> int rtrg;
>
> CharBackend chr;
> + QEMUTimer *fifo_timeout_timer;
> + uint64_t etu; /* Elementary Time Unit (ns) */
>
> qemu_irq eri;
> qemu_irq rxi;
> @@ -314,6 +317,16 @@ static int sh_serial_can_receive1(void *opaque)
> return sh_serial_can_receive(s);
> }
>
> +static void sh_serial_timeout_int(void *opaque)
> +{
> + sh_serial_state *s = opaque;
> +
> + s->flags |= SH_SERIAL_FLAG_RDF;
> + if (s->scr & (1 << 6) && s->rxi) {
> + qemu_set_irq(s->rxi, 1);
> + }
> +}
> +
> static void sh_serial_receive1(void *opaque, const uint8_t *buf, int size)
> {
> sh_serial_state *s = opaque;
> @@ -330,8 +343,12 @@ static void sh_serial_receive1(void *opaque, const uint8_t *buf, int size)
> if (s->rx_cnt >= s->rtrg) {
> s->flags |= SH_SERIAL_FLAG_RDF;
> if (s->scr & (1 << 6) && s->rxi) {
> + timer_del(s->fifo_timeout_timer);
> qemu_set_irq(s->rxi, 1);
> }
> + } else {
> + timer_mod(s->fifo_timeout_timer,
> + qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) + 15 * s->etu);
> }
> }
> }
> @@ -402,6 +419,9 @@ void sh_serial_init(MemoryRegion *sysmem,
> sh_serial_event, NULL, s, NULL, true);
> }
>
> + s->fifo_timeout_timer = timer_new_ns(QEMU_CLOCK_VIRTUAL,
> + sh_serial_timeout_int, s);
> + s->etu = NANOSECONDS_PER_SECOND / 9600;
> s->eri = eri_source;
> s->rxi = rxi_source;
> s->txi = txi_source;
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2018-09-11 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 13:11 [PATCH qemu v2] hw/char/sh_serial: Add timeout handling to unbreak serial input Geert Uytterhoeven
2018-09-11 13:11 ` Paolo Bonzini [this message]
2018-09-28 12:36 ` Geert Uytterhoeven
2018-09-30 7:32 ` Paolo Bonzini
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=76422049-ffe3-d4a9-6dcb-8edf05a8e200@redhat.com \
--to=pbonzini@redhat.com \
--cc=dalias@libc.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=uli@fpond.eu \
/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).