* [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat
@ 2014-01-31 21:29 Andrew Chew
[not found] ` <1391203779-5676-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Chew @ 2014-01-31 21:29 UTC (permalink / raw)
To: daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A,
tglx-hfZtesqFncYOwBW4kG4KsQ, swarren-3lzwWm7+Weoh9ZMKESR00Q,
thierry.reding-Re5JQEeQqe8AvxtiuMwx3w,
abrestic-F7+t8E8rja9g9hUCZPvPmw, dgreid-F7+t8E8rja9g9hUCZPvPmw,
katierh-F7+t8E8rja9g9hUCZPvPmw
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-tegra-u79uwXL29TY76Z2rM5mHXA, Andrew Chew
There are some differences between tegra20's timer registers and tegra30's
(and later). For one thing, the watchdogs don't seem to be present in
tegra20. Add this compatibility string in order to be able to distinguish
whether the watchdogs are there or not.
Signed-off-by: Andrew Chew <achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
---
drivers/clocksource/tegra20_timer.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/tegra20_timer.c b/drivers/clocksource/tegra20_timer.c
index d1869f0..73cfa56 100644
--- a/drivers/clocksource/tegra20_timer.c
+++ b/drivers/clocksource/tegra20_timer.c
@@ -218,6 +218,7 @@ static void __init tegra20_init_timer(struct device_node *np)
0x1, 0x1fffffff);
}
CLOCKSOURCE_OF_DECLARE(tegra20_timer, "nvidia,tegra20-timer", tegra20_init_timer);
+CLOCKSOURCE_OF_DECLARE(tegra30_timer, "nvidia,tegra30-timer", tegra20_init_timer);
static void __init tegra20_init_rtc(struct device_node *np)
{
--
1.8.1.5
^ permalink raw reply related [flat|nested] 7+ messages in thread[parent not found: <1391203779-5676-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>]
* Re: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat [not found] ` <1391203779-5676-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> @ 2014-02-03 16:39 ` Daniel Lezcano [not found] ` <52EFC652.9000209-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2014-02-03 21:07 ` Stephen Warren 1 sibling, 1 reply; 7+ messages in thread From: Daniel Lezcano @ 2014-02-03 16:39 UTC (permalink / raw) To: Andrew Chew, tglx-hfZtesqFncYOwBW4kG4KsQ, swarren-3lzwWm7+Weoh9ZMKESR00Q, thierry.reding-Re5JQEeQqe8AvxtiuMwx3w, abrestic-F7+t8E8rja9g9hUCZPvPmw, dgreid-F7+t8E8rja9g9hUCZPvPmw, katierh-F7+t8E8rja9g9hUCZPvPmw Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA, linux-tegra-u79uwXL29TY76Z2rM5mHXA On 01/31/2014 10:29 PM, Andrew Chew wrote: > There are some differences between tegra20's timer registers and tegra30's > (and later). For one thing, the watchdogs don't seem to be present in > tegra20. "don't seem", so it is an assumption ? > Add this compatibility string in order to be able to distinguish > whether the watchdogs are there or not. Sorry but I don't get the connection between declaring the tegra30_timer and the log. Can you elaborate please ? > Signed-off-by: Andrew Chew <achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> > --- > drivers/clocksource/tegra20_timer.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/clocksource/tegra20_timer.c b/drivers/clocksource/tegra20_timer.c > index d1869f0..73cfa56 100644 > --- a/drivers/clocksource/tegra20_timer.c > +++ b/drivers/clocksource/tegra20_timer.c > @@ -218,6 +218,7 @@ static void __init tegra20_init_timer(struct device_node *np) > 0x1, 0x1fffffff); > } > CLOCKSOURCE_OF_DECLARE(tegra20_timer, "nvidia,tegra20-timer", tegra20_init_timer); > +CLOCKSOURCE_OF_DECLARE(tegra30_timer, "nvidia,tegra30-timer", tegra20_init_timer); > > static void __init tegra20_init_rtc(struct device_node *np) > { > -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <52EFC652.9000209-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>]
* RE: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat [not found] ` <52EFC652.9000209-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> @ 2014-02-03 18:54 ` Andrew Chew 2014-02-04 19:10 ` Thomas Gleixner 0 siblings, 1 reply; 7+ messages in thread From: Andrew Chew @ 2014-02-03 18:54 UTC (permalink / raw) To: Daniel Lezcano, tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org, swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org, thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, katierh-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > From: Daniel Lezcano [mailto:daniel.lezcano@linaro.org] > Sent: Monday, February 03, 2014 8:40 AM > To: Andrew Chew; tglx@linutronix.de; swarren@wwwdotorg.org; > thierry.reding@gmail.com; abrestic@chromium.org; dgreid@chromium.org; > katierh@chromium.org > Cc: linux-kernel@vger.kernel.org; linux-tegra@vger.kernel.org > Subject: Re: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat > > On 01/31/2014 10:29 PM, Andrew Chew wrote: > > There are some differences between tegra20's timer registers and > > tegra30's (and later). For one thing, the watchdogs don't seem to be > > present in tegra20. > > "don't seem", so it is an assumption ? No, this is not an assumption. It has been verified by other NVIDIA engineers since I proposed this change. > > Add this compatibility string in order to be able to distinguish > > whether the watchdogs are there or not. > > Sorry but I don't get the connection between declaring the tegra30_timer > and the log. Can you elaborate please ? I don't know what you mean by "the log". Was that a typo? Anyway, I have a watchdog driver that I intend to follow up with, that binds with tegra30-timer. I don't want this driver to be able to bind with tegra20-timer, because the driver won't actually work on tegra20. Does that answer your question? ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat 2014-02-03 18:54 ` Andrew Chew @ 2014-02-04 19:10 ` Thomas Gleixner [not found] ` <alpine.DEB.2.02.1402042004000.24986-3cz04HxQygjZikZi3RtOZ1XZhhPuCNm+@public.gmane.org> 0 siblings, 1 reply; 7+ messages in thread From: Thomas Gleixner @ 2014-02-04 19:10 UTC (permalink / raw) To: Andrew Chew Cc: Daniel Lezcano, swarren@wwwdotorg.org, thierry.reding@gmail.com, abrestic@chromium.org, dgreid@chromium.org, katierh@chromium.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org On Mon, 3 Feb 2014, Andrew Chew wrote: > > From: Daniel Lezcano [mailto:daniel.lezcano@linaro.org] > > Sent: Monday, February 03, 2014 8:40 AM > > To: Andrew Chew; tglx@linutronix.de; swarren@wwwdotorg.org; > > thierry.reding@gmail.com; abrestic@chromium.org; dgreid@chromium.org; > > katierh@chromium.org > > Cc: linux-kernel@vger.kernel.org; linux-tegra@vger.kernel.org > > Subject: Re: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat > > > > On 01/31/2014 10:29 PM, Andrew Chew wrote: > > > There are some differences between tegra20's timer registers and > > > tegra30's (and later). For one thing, the watchdogs don't seem to be > > > present in tegra20. > > > > "don't seem", so it is an assumption ? > > No, this is not an assumption. It has been verified by other NVIDIA engineers > since I proposed this change. So why is your changelog saying "don't seem to be" ? > > > Add this compatibility string in order to be able to distinguish > > > whether the watchdogs are there or not. > > > > Sorry but I don't get the connection between declaring the tegra30_timer > > and the log. Can you elaborate please ? > > I don't know what you mean by "the log". Was that a typo? Anyway, I Daniel refers to the changelog. > have a watchdog driver that I intend to follow up with, that binds > with tegra30-timer. I don't want this driver to be able to bind with > tegra20-timer, because the driver won't actually work on tegra20. So the changelog should say: Tegra30 and later have more timer functionality than Tegra20, but share the clocksource core code. Add a separate devicetree entry which defaults to the tegra20 code for now. This is preparatory work for adding new tegra30 specific functionality. Thanks, tglx ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <alpine.DEB.2.02.1402042004000.24986-3cz04HxQygjZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>]
* RE: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat [not found] ` <alpine.DEB.2.02.1402042004000.24986-3cz04HxQygjZikZi3RtOZ1XZhhPuCNm+@public.gmane.org> @ 2014-02-04 19:14 ` Andrew Chew [not found] ` <643E69AA4436674C8F39DCC2C05F76386319985620-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org> 0 siblings, 1 reply; 7+ messages in thread From: Andrew Chew @ 2014-02-04 19:14 UTC (permalink / raw) To: Thomas Gleixner Cc: Daniel Lezcano, swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org, thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, katierh-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > > > On 01/31/2014 10:29 PM, Andrew Chew wrote: > > > > There are some differences between tegra20's timer registers and > > > > tegra30's (and later). For one thing, the watchdogs don't seem to > > > > be present in tegra20. > > > > > > "don't seem", so it is an assumption ? > > > > No, this is not an assumption. It has been verified by other NVIDIA > > engineers since I proposed this change. > > So why is your changelog saying "don't seem to be" ? I updated the commit message (see V2 of this patch). I hope the new commit message satisfies the concerns: "There are some differences between tegra20's timer registers and tegra30's (and later). For example, tegra30 has more timers. In addition, watchdogs are not present in tegra20. Add this compatibility string in order to be able to distinguish whether the additional timers and watchdogs are there or not." ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <643E69AA4436674C8F39DCC2C05F76386319985620-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>]
* RE: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat [not found] ` <643E69AA4436674C8F39DCC2C05F76386319985620-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org> @ 2014-02-04 20:22 ` Thomas Gleixner 0 siblings, 0 replies; 7+ messages in thread From: Thomas Gleixner @ 2014-02-04 20:22 UTC (permalink / raw) To: Andrew Chew Cc: Daniel Lezcano, swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org, thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, katierh-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Tue, 4 Feb 2014, Andrew Chew wrote: > > > > On 01/31/2014 10:29 PM, Andrew Chew wrote: > > > > > There are some differences between tegra20's timer registers and > > > > > tegra30's (and later). For one thing, the watchdogs don't seem to > > > > > be present in tegra20. > > > > > > > > "don't seem", so it is an assumption ? > > > > > > No, this is not an assumption. It has been verified by other NVIDIA > > > engineers since I proposed this change. > > > > So why is your changelog saying "don't seem to be" ? > > I updated the commit message (see V2 of this patch). I hope the new > commit message satisfies the concerns: > > "There are some differences between tegra20's timer registers and tegra30's > (and later). For example, tegra30 has more timers. In addition, watchdogs are > not present in tegra20. > > Add this compatibility string in order to be able to distinguish whether the > additional timers and watchdogs are there or not." Yup, that's way more understandable. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat [not found] ` <1391203779-5676-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2014-02-03 16:39 ` Daniel Lezcano @ 2014-02-03 21:07 ` Stephen Warren 1 sibling, 0 replies; 7+ messages in thread From: Stephen Warren @ 2014-02-03 21:07 UTC (permalink / raw) To: Andrew Chew, daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A, tglx-hfZtesqFncYOwBW4kG4KsQ, thierry.reding-Re5JQEeQqe8AvxtiuMwx3w, abrestic-F7+t8E8rja9g9hUCZPvPmw, dgreid-F7+t8E8rja9g9hUCZPvPmw, katierh-F7+t8E8rja9g9hUCZPvPmw Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA, linux-tegra-u79uwXL29TY76Z2rM5mHXA On 01/31/2014 02:29 PM, Andrew Chew wrote: > There are some differences between tegra20's timer registers and tegra30's > (and later). For one thing, the watchdogs don't seem to be present in > tegra20. Add this compatibility string in order to be able to distinguish > whether the watchdogs are there or not. Acked-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-02-04 20:22 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-31 21:29 [PATCH v1] clocksource: tegra: Add nvidia,tegra30-timer compat Andrew Chew
[not found] ` <1391203779-5676-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-02-03 16:39 ` Daniel Lezcano
[not found] ` <52EFC652.9000209-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-02-03 18:54 ` Andrew Chew
2014-02-04 19:10 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.02.1402042004000.24986-3cz04HxQygjZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2014-02-04 19:14 ` Andrew Chew
[not found] ` <643E69AA4436674C8F39DCC2C05F76386319985620-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2014-02-04 20:22 ` Thomas Gleixner
2014-02-03 21:07 ` Stephen Warren
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).