From: Tony Lindgren <tony@atomide.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH 2/2] clocksource/drivers/timer-ti-dm: Handle dra7 timer wrap errata i940
Date: Mon, 22 Mar 2021 12:17:19 +0200 [thread overview]
Message-ID: <YFhurzhHvusXbvyU@atomide.com> (raw)
In-Reply-To: <1edba5bd-5408-c545-85ea-689b4171cb5b@linaro.org>
Hi,
* Daniel Lezcano <daniel.lezcano@linaro.org> [210322 10:16]:
> On 04/03/2021 08:37, Tony Lindgren wrote:
> > There is a timer wrap issue on dra7 for the ARM architected timer.
> > In a typical clock configuration the timer fails to wrap after 388 days.
> >
> > To work around the issue, we need to use timer-ti-dm percpu timers instead.
> >
> > Let's configure dmtimer3 and 4 as percpu timers by default, and warn about
> > the issue if the dtb is not configured properly.
> >
> > Let's do this as a single patch so it can be backported to v5.8 and later
> > kernels easily.
>
> Cc: <stable@vger.kernel.org> # v5.8+
>
> ??
Yes please, that would be great.
Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH 2/2] clocksource/drivers/timer-ti-dm: Handle dra7 timer wrap errata i940
Date: Mon, 22 Mar 2021 12:17:19 +0200 [thread overview]
Message-ID: <YFhurzhHvusXbvyU@atomide.com> (raw)
In-Reply-To: <1edba5bd-5408-c545-85ea-689b4171cb5b@linaro.org>
Hi,
* Daniel Lezcano <daniel.lezcano@linaro.org> [210322 10:16]:
> On 04/03/2021 08:37, Tony Lindgren wrote:
> > There is a timer wrap issue on dra7 for the ARM architected timer.
> > In a typical clock configuration the timer fails to wrap after 388 days.
> >
> > To work around the issue, we need to use timer-ti-dm percpu timers instead.
> >
> > Let's configure dmtimer3 and 4 as percpu timers by default, and warn about
> > the issue if the dtb is not configured properly.
> >
> > Let's do this as a single patch so it can be backported to v5.8 and later
> > kernels easily.
>
> Cc: <stable@vger.kernel.org> # v5.8+
>
> ??
Yes please, that would be great.
Thanks,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-22 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 7:37 [PATCH 0/2] Fixes for for dra7 timer wrap errata i940 Tony Lindgren
2021-03-04 7:37 ` Tony Lindgren
2021-03-04 7:37 ` [PATCH 1/2] clocksource/drivers/timer-ti-dm: Prepare to handle dra7 timer wrap issue Tony Lindgren
2021-03-04 7:37 ` Tony Lindgren
2021-03-22 15:55 ` Daniel Lezcano
2021-03-22 15:55 ` Daniel Lezcano
2021-03-22 16:33 ` Tony Lindgren
2021-03-22 16:33 ` Tony Lindgren
2021-03-22 18:23 ` Daniel Lezcano
2021-03-22 18:23 ` Daniel Lezcano
2021-03-23 6:31 ` Tony Lindgren
2021-03-23 6:31 ` Tony Lindgren
2021-03-04 7:37 ` [PATCH 2/2] clocksource/drivers/timer-ti-dm: Handle dra7 timer wrap errata i940 Tony Lindgren
2021-03-04 7:37 ` Tony Lindgren
2021-03-22 10:15 ` Daniel Lezcano
2021-03-22 10:15 ` Daniel Lezcano
2021-03-22 10:17 ` Tony Lindgren [this message]
2021-03-22 10:17 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2021-03-23 7:43 [PATCHv2 0/2] Fixes for for " Tony Lindgren
2021-03-23 7:43 ` [PATCH 2/2] clocksource/drivers/timer-ti-dm: Handle " Tony Lindgren
2021-03-23 7:43 ` Tony Lindgren
2022-01-29 21:05 ` Drew Fustini
2022-01-29 21:05 ` Drew Fustini
2022-01-31 10:16 ` Tony Lindgren
2022-01-31 10:16 ` Tony Lindgren
2022-02-02 20:54 ` Drew Fustini
2022-02-02 20:54 ` Drew Fustini
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=YFhurzhHvusXbvyU@atomide.com \
--to=tony@atomide.com \
--cc=daniel.lezcano@linaro.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 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.