From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx35: don't disable the uart clock when DEBUG_LL is in use
Date: Tue, 31 Jul 2012 19:43:58 +0200 [thread overview]
Message-ID: <20120731174358.GC30009@pengutronix.de> (raw)
In-Reply-To: <1343742279-29570-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Tue, Jul 31, 2012 at 03:44:39PM +0200, Uwe Kleine-K?nig wrote:
> Otherwise printch et al. and printk with earlyprintk and keep_bootcon
> becomes unfunctional when the clk framework disables all unused clocks.
Why don't you use the regular console? Letting the clock framework
disable the clocks was pretty much intentional.
Sascha
>
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> ---
> arch/arm/mach-imx/clk-imx35.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/mach-imx/clk-imx35.c b/arch/arm/mach-imx/clk-imx35.c
> index c6422fb..83d614c 100644
> --- a/arch/arm/mach-imx/clk-imx35.c
> +++ b/arch/arm/mach-imx/clk-imx35.c
> @@ -271,6 +271,10 @@ int __init mx35_clocks_init()
> */
> clk_prepare_enable(clk[scc_gate]);
>
> + /* Assert that the UART clock keeps running if DEBUG_LL is in use */
> + if (IS_ENABLED(CONFIG_DEBUG_IMX31_IMX35_UART))
> + clk_prepare_enable(clk[uart1_gate]);
> +
> imx_print_silicon_rev("i.MX35", mx35_revision());
>
> #ifdef CONFIG_MXC_USE_EPIT
> --
> 1.7.10.4
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-07-31 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 13:44 [PATCH] ARM: imx35: don't disable the uart clock when DEBUG_LL is in use Uwe Kleine-König
2012-07-31 17:43 ` Sascha Hauer [this message]
2012-07-31 18:32 ` Uwe Kleine-König
2012-08-06 14:24 ` Uwe Kleine-König
2012-08-06 14:35 ` Sascha Hauer
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=20120731174358.GC30009@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).