From: David Lechner <david@lechnology.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Sekhar Nori <nsekhar@ti.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kevin Hilman <khilman@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 1/3] clocksource: davinci: work around a clocksource problem on dm365 SoC
Date: Mon, 16 Dec 2019 11:58:31 -0600 [thread overview]
Message-ID: <b9a28314-4fce-ebbd-be20-b0ffa2f1f15f@lechnology.com> (raw)
In-Reply-To: <20191213162453.15691-2-brgl@bgdev.pl>
On 12/13/19 10:24 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> The DM365 platform has a strange quirk (only present when using ancient
> u-boot - mainline u-boot v2013.01 and later works fine) where if we
> enable the second half of the timer in periodic mode before we do its
> initialization - the time won't start flowing and we can't boot.
>
> When using more recent u-boot, we can enable the timer, then reinitialize
> it and all works fine.
>
> I've been unable to figure out why that is, but a workaround for this
> is straightforward - just cache the enable bits for tim34.
I had a hard time groking this code. See suggested changes below for
something that would make the intention more clear (to me at least).
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> drivers/clocksource/timer-davinci.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clocksource/timer-davinci.c b/drivers/clocksource/timer-davinci.c
> index 62745c962049..1c22443acaeb 100644
> --- a/drivers/clocksource/timer-davinci.c
> +++ b/drivers/clocksource/timer-davinci.c
> @@ -64,6 +64,8 @@ static struct {
> unsigned int tim_off;
> } davinci_clocksource;
>
> +static unsigned int davinci_clocksource_tim32_mode;
static unsigned bool davinci_clocksource_initialized;
> +
> static struct davinci_clockevent *
> to_davinci_clockevent(struct clock_event_device *clockevent)
> {
> @@ -94,7 +96,7 @@ static void davinci_tim12_shutdown(void __iomem *base)
> * halves. In this case TIM34 runs in periodic mode and we must
> * not modify it.
> */
> - tcr |= DAVINCI_TIMER_ENAMODE_PERIODIC <<
> + tcr |= davinci_clocksource_tim32_mode <<
> DAVINCI_TIMER_ENAMODE_SHIFT_TIM34;
if (davinci_clocksource_initialized)
tcr |= DAVINCI_TIMER_ENAMODE_PERIODIC <<
DAVINCI_TIMER_ENAMODE_SHIFT_TIM34;
>
> writel_relaxed(tcr, base + DAVINCI_TIMER_REG_TCR);
> @@ -107,7 +109,7 @@ static void davinci_tim12_set_oneshot(void __iomem *base)
> tcr = DAVINCI_TIMER_ENAMODE_ONESHOT <<
> DAVINCI_TIMER_ENAMODE_SHIFT_TIM12;
> /* Same as above. */
> - tcr |= DAVINCI_TIMER_ENAMODE_PERIODIC <<
> + tcr |= davinci_clocksource_tim32_mode <<
> DAVINCI_TIMER_ENAMODE_SHIFT_TIM34;
if (davinci_clocksource_initialized)
tcr |= DAVINCI_TIMER_ENAMODE_PERIODIC <<
DAVINCI_TIMER_ENAMODE_SHIFT_TIM34;
>
> writel_relaxed(tcr, base + DAVINCI_TIMER_REG_TCR);
> @@ -206,6 +208,8 @@ static void davinci_clocksource_init_tim34(void __iomem *base)
> writel_relaxed(0x0, base + DAVINCI_TIMER_REG_TIM34);
> writel_relaxed(UINT_MAX, base + DAVINCI_TIMER_REG_PRD34);
> writel_relaxed(tcr, base + DAVINCI_TIMER_REG_TCR);
> +
> + davinci_clocksource_tim32_mode = DAVINCI_TIMER_ENAMODE_PERIODIC;
davinci_clocksource_initialized = true;
> }
>
> /*
>
next prev parent reply other threads:[~2019-12-16 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 16:24 [PATCH 0/3] ARM: davinci: convert dm365 to using the new clocksource driver Bartosz Golaszewski
2019-12-13 16:24 ` [PATCH 1/3] clocksource: davinci: work around a clocksource problem on dm365 SoC Bartosz Golaszewski
2019-12-16 17:58 ` David Lechner [this message]
2019-12-17 8:00 ` Bartosz Golaszewski
2019-12-17 17:01 ` David Lechner
2019-12-18 9:28 ` Sekhar Nori
2019-12-19 8:59 ` Bartosz Golaszewski
2019-12-13 16:24 ` [PATCH 2/3] ARM: davinci: dm365: switch to using the clocksource driver Bartosz Golaszewski
2019-12-13 16:24 ` [PATCH 3/3] ARM: davinci: remove legacy timer support Bartosz Golaszewski
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=b9a28314-4fce-ebbd-be20-b0ffa2f1f15f@lechnology.com \
--to=david@lechnology.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=daniel.lezcano@linaro.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome