From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
dongas86@gmail.com, shawnguo@kernel.org, kernel@pengutronix.de,
aford173@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] clk: imx6q: fix uart earlycon unwork
Date: Wed, 28 Jul 2021 11:28:11 +0300 [thread overview]
Message-ID: <YQEVG1R1IDxB8odE@ryzen> (raw)
In-Reply-To: <162741907003.2368309.8765989426815970294@swboyd.mtv.corp.google.com>
On 21-07-27 13:51:10, Stephen Boyd wrote:
> Quoting Abel Vesa (2021-07-19 03:39:31)
> > On 21-07-02 16:54:38, Dong Aisheng wrote:
> > > The earlycon depends on the bootloader setup UART clocks being retained.
> > > There're actually two uart clocks (ipg, per) on MX6QDL,
> > > but the 'Fixes' commit change to register only one which means
> > > another clock may be disabled during booting phase
> > > and result in the earlycon unwork.
> > >
> > > Cc: stable@vger.kernel.org # v5.10+
> > > Fixes: 379c9a24cc23 ("clk: imx: Fix reparenting of UARTs not associated with stdout")
> > > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> >
> >
> > Reviewed-by: Abel Vesa <abel.vesa@nxp.com>
> >
> > Stephen, will you pick this up ?
> >
>
> Sure I can pick it up if you need me to pick it to fixes?
Yes, please.
Thanks.
next prev parent reply other threads:[~2021-07-28 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 8:54 [PATCH 1/1] clk: imx6q: fix uart earlycon unwork Dong Aisheng
2021-07-19 10:39 ` Abel Vesa
2021-07-27 20:51 ` Stephen Boyd
2021-07-28 8:28 ` Abel Vesa [this message]
2021-08-06 1:12 ` Stephen Boyd
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=YQEVG1R1IDxB8odE@ryzen \
--to=abel.vesa@nxp.com \
--cc=aford173@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=dongas86@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox