From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers
Date: Wed, 26 Nov 2014 13:55:55 +0100 [thread overview]
Message-ID: <19683112.9S9LAQsUEX@diego> (raw)
In-Reply-To: <5475CC75.5030300@linaro.org>
Am Mittwoch, 26. November 2014, 13:49:57 schrieb Daniel Lezcano:
> On 11/26/2014 01:48 PM, Heiko St?bner wrote:
> > Am Mittwoch, 26. November 2014, 13:30:58 schrieb Daniel Lezcano:
> >> On 11/26/2014 01:06 PM, Heiko St?bner wrote:
> >>> Hi Daniel,
> >>>
> >>> Am Mittwoch, 26. November 2014, 12:51:08 schrieb Daniel Lezcano:
> >>>> Hi Doug, Olof,
> >>>>
> >>>> IIUC, it sounds like this patch is needed from some other patches in
> >>>> arm-soc. Olof was proposing to take this patch through its tree to
> >>>> facilitate the integration.
> >>>>
> >>>> Olof, is it this patch you were worried about ?
> >>>
> >>> I think this is one of two patches in question.
> >>>
> >>> "clocksource: arch_timer: Fix code to use physical timers when
> >>> requested"
> >>> [0] would be the second one.
> >>>
> >>> And the patch for arm-soc that Olof means would be "ARM: dts: rk3288:
> >>> add
> >>> arm,cpu-registers-not-fw-configured" [1].
> >>
> >> Ok, so IIUC, "clocksource: arch_timer: Fix code to use physical timers
> >> when requested" should go via arm's tree, right ?
> >
> > If I'm reading Olof's irc-comments from yesterday correctly, that is right
> > and the 3 patches should go in together:
> >
> > - "clocksource: arch_timer: Fix code to use physical timers
> >
> > when requested" fixes the use of physical timers in general
> >
> > - "clocksource: arch_timer: Allow the device tree to specify uninitialized
> >
> > timer registers" allows this to be set from dt
> >
> > - "ARM: dts: rk3288: add arm,cpu-registers-not-fw-configured" enables this
> > on>
> > rk3288
>
> Ok, then I drop them from my tree and will let Olof to handle them.
But maybe you could give them an Ack :-)
Heiko
next prev parent reply other threads:[~2014-11-26 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 7:33 [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers Sonny Rao
2014-11-19 23:01 ` Doug Anderson
2014-11-23 21:41 ` Daniel Lezcano
2014-11-26 11:51 ` Daniel Lezcano
2014-11-26 12:06 ` Heiko Stübner
2014-11-26 12:30 ` Daniel Lezcano
2014-11-26 12:48 ` Heiko Stübner
2014-11-26 12:49 ` Daniel Lezcano
2014-11-26 12:55 ` Heiko Stübner [this message]
2014-11-26 12:53 ` Daniel Lezcano
2014-11-26 12:49 ` Daniel Lezcano
2014-11-28 14:16 ` Catalin Marinas
2014-11-26 14:41 ` Yingjoe Chen
2014-11-26 16:14 ` Doug Anderson
2014-11-27 2:27 ` Yingjoe Chen
2014-12-05 7:34 ` Olof Johansson
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=19683112.9S9LAQsUEX@diego \
--to=heiko@sntech.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).