[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c7b4d3-021c-4a4b-9e91-316603b348c1@tuxon.dev>
Date: Thu, 5 Dec 2024 10:39:45 +0200
From: Claudiu Beznea <claudiu.beznea@...on.dev>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
gregkh@...uxfoundation.org, jirislaby@...nel.org, geert+renesas@...der.be,
prabhakar.mahadev-lad.rj@...renesas.com, lethal@...ux-sh.org,
g.liakhovetski@....de, groeck@...omium.org, mka@...omium.org,
ulrich.hecht+renesas@...il.com, ysato@...rs.sourceforge.jp,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH RFT 0/6] serial: sh-sci: Fixes for earlycon and
keep_bootcon
Hi, Wolfram,
On 04.12.2024 23:38, Wolfram Sang wrote:
> Hi Claudiu,
>
>> in the following scenarios:
>>
>> 1/ "earlycon keep_bootcon" were present in bootargs
>> 2/ only "earlycon" was present in bootargs
>> 3/ none of the "earlycon" or "earlycon keep_bootcon" were present in
>> bootargs
> ...
>> Please give it a try on your devices as well.
>
> Will happily do so. Is there something to look for? Except for "it
> works"?
As this code touches the earlycon functionality, of interest are the 3
cases highlighted above:
1/ "earlycon keep_bootcon" are both present in bootargs
2/ only "earlycon" is present in bootargs
3/ none of the "earlycon" or "earlycon keep_bootcon" are present in
bootargs
One other thing, that I was currently able to test only on RZ/G3S, is to
see how it behaves when the debug serial is described in DT with an alias
other than zero. E.g., on [1] the debug serial alias on RZ/G3S was changed
from 0 to 3. With the new alias (3) there were issues that I've tried to
fix with this series.
Thank you for checking it,
Claudiu
[1]
https://lore.kernel.org/all/20241115134401.3893008-6-claudiu.beznea.uj@bp.renesas.com/
>
> Happy hacking,
>
> Wolfram
>
Powered by blists - more mailing lists