From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
wsa+renesas@sang-engineering.com,
prabhakar.mahadev-lad.rj@bp.renesas.com, lethal@linux-sh.org,
g.liakhovetski@gmx.de, groeck@chromium.org, mka@chromium.org,
ulrich.hecht+renesas@gmail.com, ysato@users.sourceforge.jp,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
stable@vger.kernel.org
Subject: Re: [PATCH RFT 6/6] serial: sh-sci: Increment the runtime usage counter for the earlycon device
Date: Thu, 2 Jan 2025 19:57:54 +0200 [thread overview]
Message-ID: <38fc5c6a-e4b5-46d6-89df-3aea9a33f79b@tuxon.dev> (raw)
In-Reply-To: <CAMuHMdWB2q7=gkHUsmVWwZMCWaj-htUpOQCr24y5HsbQvM+HMA@mail.gmail.com>
Hi, Geert,
On 19.12.2024 16:30, Geert Uytterhoeven wrote:
> Hi Claudiu,
>
> On Wed, Dec 4, 2024 at 4:58 PM Claudiu <claudiu.beznea@tuxon.dev> wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> In the sh-sci driver, serial ports are mapped to the sci_ports[] array,
>> with earlycon mapped at index zero.
>>
>> The uart_add_one_port() function eventually calls __device_attach(),
>> which, in turn, calls pm_request_idle(). The identified code path is as
>> follows:
>>
>> uart_add_one_port() ->
>> serial_ctrl_register_port() ->
>> serial_core_register_port() ->
>> serial_core_port_device_add() ->
>> serial_base_port_add() ->
>> device_add() ->
>> bus_probe_device() ->
>> device_initial_probe() ->
>> __device_attach() ->
>> // ...
>> if (dev->p->dead) {
>> // ...
>> } else if (dev->driver) {
>> // ...
>> } else {
>> // ...
>> pm_request_idle(dev);
>> // ...
>> }
>>
>> The earlycon device clocks are enabled by the bootloader. However, the
>> pm_request_idle() call in __device_attach() disables the SCI port clocks
>> while earlycon is still active.
>>
>> The earlycon write function, serial_console_write(), calls
>> sci_poll_put_char() via serial_console_putchar(). If the SCI port clocks
>> are disabled, writing to earlycon may sometimes cause the SR.TDFE bit to
>> remain unset indefinitely, causing the while loop in sci_poll_put_char()
>> to never exit. On single-core SoCs, this can result in the system being
>> blocked during boot when this issue occurs.
>>
>> To resolve this, increment the runtime PM usage counter for the earlycon
>> SCI device before registering the UART port.
>>
>> Fixes: 0b0cced19ab1 ("serial: sh-sci: Add CONFIG_SERIAL_EARLYCON support")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Thanks for your patch!
>
>> --- a/drivers/tty/serial/sh-sci.c
>> +++ b/drivers/tty/serial/sh-sci.c
>> @@ -3435,7 +3435,24 @@ static int sci_probe_single(struct platform_device *dev,
>> sciport->port.flags |= UPF_HARD_FLOW;
>> }
>>
>> + /*
>> + * In case:
>> + * - this is the earlycon port (mapped on index 0 in sci_ports[]) and
>> + * - it now maps to an alias other than zero and
>> + * - the earlycon is still alive (e.g., "earlycon keep_bootcon" is
>> + * available in bootargs)
>> + *
>> + * we need to avoid disabling clocks and PM domains through the runtime
>> + * PM APIs called in __device_attach(). For this, increment the runtime
>> + * PM reference counter (the clocks and PM domains were already enabled
>> + * by the bootloader). Otherwise the earlycon may access the HW when it
>> + * has no clocks enabled leading to failures (infinite loop in
>> + * sci_poll_put_char()).
>> + */
>> +
>> if (sci_ports[0].earlycon && sci_ports[0].port.mapbase == sci_res->start) {
>
> Now there are two tests for mapbase: here and in sci_probe()...
I'm not sure how can we avoid it. We need to re-check it in this function
as the sci_probe_single() is the one that enables the runtime PM. Would you
prefer to move the devm_pm_runtime_enable() in sci_probe() and have the
pm_runtime_get_noresume() in sci_probe() as well?
Thank you,
Claudiu
>
>> + pm_runtime_get_noresume(&dev->dev);
>> +
>> /*
>> * Skip cleanup up the sci_port[0] in early_console_exit(), this
>> * port is the same as the earlycon one.
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2025-01-02 17:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:58 [PATCH RFT 0/6] serial: sh-sci: Fixes for earlycon and keep_bootcon Claudiu
2024-12-04 15:58 ` [PATCH RFT 1/6] serial: sh-sci: Check if TX data was written to device in .tx_empty() Claudiu
2024-12-19 9:46 ` Geert Uytterhoeven
2024-12-21 9:16 ` Claudiu Beznea
2024-12-04 15:58 ` [PATCH RFT 2/6] serial: sh-sci: Drop __initdata macro for port_cfg Claudiu
2024-12-19 9:55 ` Geert Uytterhoeven
2024-12-04 15:58 ` [PATCH RFT 3/6] serial: sh-sci: Move runtime PM enable to sci_probe_single() Claudiu
2024-12-19 10:18 ` Geert Uytterhoeven
2024-12-21 9:20 ` Claudiu Beznea
2024-12-04 15:58 ` [PATCH RFT 4/6] serial: sh-sci: Do not probe the serial port if its slot in sci_ports[] is in use Claudiu
2024-12-19 14:21 ` Geert Uytterhoeven
2024-12-04 15:58 ` [PATCH RFT 5/6] serial: sh-sci: Clean sci_ports[0] after at earlycon exit Claudiu
2024-12-19 14:26 ` Geert Uytterhoeven
2024-12-21 9:39 ` Claudiu Beznea
2024-12-04 15:58 ` [PATCH RFT 6/6] serial: sh-sci: Increment the runtime usage counter for the earlycon device Claudiu
2024-12-19 14:30 ` Geert Uytterhoeven
2024-12-21 9:40 ` Claudiu Beznea
2025-01-02 17:57 ` Claudiu Beznea [this message]
2024-12-04 21:38 ` [PATCH RFT 0/6] serial: sh-sci: Fixes for earlycon and keep_bootcon Wolfram Sang
2024-12-05 8:39 ` Claudiu Beznea
2024-12-05 8:51 ` Claudiu Beznea
2024-12-19 15:11 ` Geert Uytterhoeven
2024-12-21 9:54 ` Claudiu Beznea
2025-01-03 11:48 ` Claudiu Beznea
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=38fc5c6a-e4b5-46d6-89df-3aea9a33f79b@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=g.liakhovetski@gmx.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jirislaby@kernel.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mka@chromium.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=stable@vger.kernel.org \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®