From: Rob Landley <rob@landley.net>
To: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Kazuhiro Fujita <kazuhiro.fujita.jg@renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hao Bui <hao.bui.yg@renesas.com>,
KAZUMI HARADA <kazumi.harada.rh@renesas.com>,
Sasha Levin <sashal@kernel.org>,
Chris Brandt <Chris.Brandt@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct sequence
Date: Mon, 17 Aug 2020 03:17:48 +0000 [thread overview]
Message-ID: <b384543f-c80d-aa63-63a6-1b5dbc47885d@landley.net> (raw)
In-Reply-To: <OSBPR01MB50485F5DA2F82E455DCA6B56AA5E0@OSBPR01MB5048.jpnprd01.prod.outlook.com>
On 8/16/20 11:22 AM, Prabhakar Mahadev Lad wrote:
>> FTR, I gave it a try on the SH7751R-based I-O DATA USL-5P aka Landisk:
>> SCIF is affected, and fixed by commit 3dc4db3662366306 ("serial: sh-sci:
>> Make sure status register SCxSR is read in correct sequence").
>>
> Thank you Geert.
>
> Cheers,
> Prabhakar
Did we ever figure out how to get linux to talk to the _first_ serial port on
the qemu-system-sh4 r2d board? I'm still doing:
qemu-system-sh4 -M r2d -serial null -serial mon:stdio
Because I can only get a working console on the _second_ serial port. (SCI vs
SCIF I think?)
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Kazuhiro Fujita <kazuhiro.fujita.jg@renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hao Bui <hao.bui.yg@renesas.com>,
KAZUMI HARADA <kazumi.harada.rh@renesas.com>,
Sasha Levin <sashal@kernel.org>,
Chris Brandt <Chris.Brandt@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct sequence
Date: Sun, 16 Aug 2020 22:17:48 -0500 [thread overview]
Message-ID: <b384543f-c80d-aa63-63a6-1b5dbc47885d@landley.net> (raw)
In-Reply-To: <OSBPR01MB50485F5DA2F82E455DCA6B56AA5E0@OSBPR01MB5048.jpnprd01.prod.outlook.com>
On 8/16/20 11:22 AM, Prabhakar Mahadev Lad wrote:
>> FTR, I gave it a try on the SH7751R-based I-O DATA USL-5P aka Landisk:
>> SCIF is affected, and fixed by commit 3dc4db3662366306 ("serial: sh-sci:
>> Make sure status register SCxSR is read in correct sequence").
>>
> Thank you Geert.
>
> Cheers,
> Prabhakar
Did we ever figure out how to get linux to talk to the _first_ serial port on
the qemu-system-sh4 r2d board? I'm still doing:
qemu-system-sh4 -M r2d -serial null -serial mon:stdio
Because I can only get a working console on the _second_ serial port. (SCI vs
SCIF I think?)
Rob
next prev parent reply other threads:[~2020-08-17 3:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 18:17 [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct sequence Kazuhiro Fujita
2020-03-31 13:11 ` Sasha Levin
2020-03-31 15:17 ` Geert Uytterhoeven
2020-03-31 15:58 ` Prabhakar Mahadev Lad
2020-03-31 17:38 ` Geert Uytterhoeven
2020-03-31 18:10 ` Prabhakar Mahadev Lad
2020-04-01 12:43 ` Geert Uytterhoeven
2020-04-02 11:27 ` Lad, Prabhakar
2020-04-02 15:24 ` Geert Uytterhoeven
2020-04-02 15:24 ` Geert Uytterhoeven
2020-04-15 12:36 ` Geert Uytterhoeven
2020-04-15 12:36 ` Geert Uytterhoeven
2020-04-15 23:21 ` Rob Landley
2020-04-15 23:21 ` Rob Landley
2020-08-14 15:25 ` Geert Uytterhoeven
2020-08-14 15:25 ` Geert Uytterhoeven
2020-08-16 16:22 ` Prabhakar Mahadev Lad
2020-08-16 16:22 ` Prabhakar Mahadev Lad
2020-08-17 3:17 ` Rob Landley [this message]
2020-08-17 3:17 ` Rob Landley
2020-08-18 15:11 ` SCI on R2D+ (was: Re: [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct seq Geert Uytterhoeven
2020-08-18 15:11 ` SCI on R2D+ (was: Re: [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct sequence) Geert Uytterhoeven
2020-03-31 19:07 ` [PATCH] serial: sh-sci: Make sure status register SCxSR is read in correct sequence Chris Brandt
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=b384543f-c80d-aa63-63a6-1b5dbc47885d@landley.net \
--to=rob@landley.net \
--cc=Chris.Brandt@renesas.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=hao.bui.yg@renesas.com \
--cc=jslaby@suse.com \
--cc=kazuhiro.fujita.jg@renesas.com \
--cc=kazumi.harada.rh@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sashal@kernel.org \
/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.