From: Tomasz Figa <t.figa@samsung.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Kukjin Kim <kgene.kim@samsung.com>,
Chander Kashyap <chander.kashyap@linaro.org>
Subject: Re: [PATCH] serial: samsung: move clock deactivation below uart registration
Date: Tue, 10 Dec 2013 14:52:40 +0100 [thread overview]
Message-ID: <4640026.L8HxPz97OG@amdc1227> (raw)
In-Reply-To: <201312050054.39327.heiko@sntech.de>
Hi Heiko,
On Thursday 05 of December 2013 00:54:38 Heiko Stübner wrote:
> Commit 60e93575476f (serial: samsung: enable clock before clearing pending
> interrupts during init) added handling of the controller clock during init.
>
> On most systems this clock is also one of the baud_clock sources and
> possibly used by the earlycon and thus already enabled by the bootloader.
>
> Therefore a gap exists between s3c24xx_serial_init_port disabling the
> clock and an attached console reenabling it, making the transition from
> earlycon to regular console possibly hang the system - as seen on my
> S3C2442 based Freerunner today.
>
> Therefore move the disabling of the clock from s3c24xx_serial_init_port
> below the uart port registration, effectively creating an overlap and
> keeping the clock running non-stop if the console wants to grab this port.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> drivers/tty/serial/samsung.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Makes sense.
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Best regards,
Tomasz
next prev parent reply other threads:[~2013-12-10 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:54 [PATCH] serial: samsung: move clock deactivation below uart registration Heiko Stübner
2013-12-10 13:52 ` Tomasz Figa [this message]
2014-01-21 14:26 ` Heiko Stübner
2014-01-21 14:26 ` Heiko Stübner
2014-01-21 17:24 ` Greg Kroah-Hartman
2014-01-21 17:24 ` Greg Kroah-Hartman
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=4640026.L8HxPz97OG@amdc1227 \
--to=t.figa@samsung.com \
--cc=chander.kashyap@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=jslaby@suse.cz \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.