From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Daniel Golle" <daniel@makrotopia.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Yu Jiaoliang" <yujiaoliang@vivo.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Changqi Hu" <changqi.hu@mediatek.com>,
"Sam Shih" <sam.shih@mediatek.com>,
"Steven Liu" <steven.liu@mediatek.com>,
"John Crispin" <john@phrozen.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3] serial: 8250_mtk: Enable baud clock and manage in runtime PM
Date: Wed, 17 Sep 2025 12:00:57 +0200 [thread overview]
Message-ID: <939cea9e-d7bd-4a13-b462-17e483f61e4c@gmail.com> (raw)
In-Reply-To: <de5197ccc31e1dab0965cabcc11ca92e67246cf6.1758058441.git.daniel@makrotopia.org>
On 16/09/2025 23:37, Daniel Golle wrote:
> Some MediaTek SoCs got a gated UART baud clock, which currently gets
> disabled as the clk subsystem believes it would be unused. This results in
> the uart freezing right after "clk: Disabling unused clocks" on those
> platforms.
>
> Request the baud clock to be prepared and enabled during probe, and to
> restore run-time power management capabilities to what it was before commit
> e32a83c70cf9 ("serial: 8250-mtk: modify mtk uart power and clock
> management") disable and unprepare the baud clock when suspending the UART,
> prepare and enable it again when resuming it.
>
> Fixes: e32a83c70cf9 ("serial: 8250-mtk: modify mtk uart power and clock management")
Most of the issues from this commit are already fixed in
b6c7ff2693ddc ("serial: 8250_mtk: Simplify clock sequencing and runtime PM")
which is more or less a revert of e32a83c70cf9.
I think we should add
Fixes: b6c7ff2693ddc ("serial: 8250_mtk: Simplify clock sequencing and runtime PM")
here as well. It's a fix of a fix :)
Regards,
Matthias
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
> ---
> v3: squash into single patch
> v2: add managing run-time PM in dedicated patch
>
> drivers/tty/serial/8250/8250_mtk.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_mtk.c b/drivers/tty/serial/8250/8250_mtk.c
> index b44de2ed7413..5875a7b9b4b1 100644
> --- a/drivers/tty/serial/8250/8250_mtk.c
> +++ b/drivers/tty/serial/8250/8250_mtk.c
> @@ -435,6 +435,7 @@ static int __maybe_unused mtk8250_runtime_suspend(struct device *dev)
> while
> (serial_in(up, MTK_UART_DEBUG0));
>
> + clk_disable_unprepare(data->uart_clk);
> clk_disable_unprepare(data->bus_clk);
>
> return 0;
> @@ -445,6 +446,7 @@ static int __maybe_unused mtk8250_runtime_resume(struct device *dev)
> struct mtk8250_data *data = dev_get_drvdata(dev);
>
> clk_prepare_enable(data->bus_clk);
> + clk_prepare_enable(data->uart_clk);
>
> return 0;
> }
> @@ -475,13 +477,13 @@ static int mtk8250_probe_of(struct platform_device *pdev, struct uart_port *p,
> int dmacnt;
> #endif
>
> - data->uart_clk = devm_clk_get(&pdev->dev, "baud");
> + data->uart_clk = devm_clk_get_enabled(&pdev->dev, "baud");
> if (IS_ERR(data->uart_clk)) {
> /*
> * For compatibility with older device trees try unnamed
> * clk when no baud clk can be found.
> */
> - data->uart_clk = devm_clk_get(&pdev->dev, NULL);
> + data->uart_clk = devm_clk_get_enabled(&pdev->dev, NULL);
> if (IS_ERR(data->uart_clk)) {
> dev_warn(&pdev->dev, "Can't get uart clock\n");
> return PTR_ERR(data->uart_clk);
next prev parent reply other threads:[~2025-09-17 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 21:37 Daniel Golle
2025-09-17 10:00 ` Matthias Brugger [this message]
2025-10-19 2:02 ` Daniel Golle
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=939cea9e-d7bd-4a13-b462-17e483f61e4c@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=changqi.hu@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=sam.shih@mediatek.com \
--cc=steven.liu@mediatek.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=yujiaoliang@vivo.com \
/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®