From: Abel Vesa <abel.vesa@nxp.com>
To: Anson.Huang@nxp.com
Cc: mturquette@baylibre.com, sboyd@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Linux-imx@nxp.com
Subject: Re: [PATCH] clk: imx8mn: Keep uart clocks on for early console
Date: Fri, 26 Jul 2019 11:38:40 +0300 [thread overview]
Message-ID: <20190726083840.k26dyjgpq4b56gab@fsr-ub1664-175> (raw)
In-Reply-To: <20190724075017.11003-1-Anson.Huang@nxp.com>
On 19-07-24 15:50:17, Anson.Huang@nxp.com wrote:
> From: Anson Huang <Anson.Huang@nxp.com>
>
> Call imx_register_uart_clocks() API to keep uart clocks enabled
> when earlyprintk or earlycon is active.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Reviewed-by: Abel Vesa <abel.vesa@nxp.com>
> ---
> drivers/clk/imx/clk-imx8mn.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/clk/imx/clk-imx8mn.c b/drivers/clk/imx/clk-imx8mn.c
> index 07481a5..ecd1062 100644
> --- a/drivers/clk/imx/clk-imx8mn.c
> +++ b/drivers/clk/imx/clk-imx8mn.c
> @@ -355,6 +355,14 @@ static const char * const imx8mn_clko2_sels[] = {"osc_24m", "sys_pll2_200m", "sy
> static struct clk *clks[IMX8MN_CLK_END];
> static struct clk_onecell_data clk_data;
>
> +static struct clk ** const uart_clks[] = {
> + &clks[IMX8MN_CLK_UART1_ROOT],
> + &clks[IMX8MN_CLK_UART2_ROOT],
> + &clks[IMX8MN_CLK_UART3_ROOT],
> + &clks[IMX8MN_CLK_UART4_ROOT],
> + NULL
> +};
> +
> static int imx8mn_clocks_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -612,6 +620,8 @@ static int imx8mn_clocks_probe(struct platform_device *pdev)
> goto unregister_clks;
> }
>
> + imx_register_uart_clocks(uart_clks);
> +
> return 0;
>
> unregister_clks:
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-07-26 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 7:50 [PATCH] clk: imx8mn: Keep uart clocks on for early console Anson.Huang
2019-07-26 8:38 ` Abel Vesa [this message]
2019-08-03 9:04 ` Shawn Guo
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=20190726083840.k26dyjgpq4b56gab@fsr-ub1664-175 \
--to=abel.vesa@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).