From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clocksource: add DB8500 PRCMU Timer support
Date: Tue, 31 May 2011 23:18:25 +0200 [thread overview]
Message-ID: <BANLkTinPKbUu40066+wr3cdFRc2di-Uv6g@mail.gmail.com> (raw)
In-Reply-To: <4DE51EB7.7010606@stericsson.com>
On Tue, May 31, 2011 at 7:00 PM, Mattias Wallin
<mattias.wallin@stericsson.com> wrote:
> On 05/31/2011 12:38 PM, Thomas Gleixner wrote:
>>> +++ b/include/linux/clksrc-db8500-prcmu.h
>> Huch, why needs this to be a separate head in include/linux ?
>
> I will move the header file to mach-ux500/include/mach/. Ok?
>
> (I have long time ago been thought to avoid include mach headers from the
> drivers. But if I understand it correct it is not true any more and in this
> case it certainly makes no sense since I break that rule myself.)
Keeping it under include/linux is probably wise since we want drivers
OUT of the ARM tree, but I don't know if there is much consensus on that?
I was more understanding the question as why it was needed at all.
Does it work to register the clocksource with say a core_initcall()
and avoid the header altogether?
Else a header is needed since we need to call out from the platform timer
init function to this clocksource to register it.
Thanks,
Linus Walleij
next prev parent reply other threads:[~2011-05-31 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 8:31 [PATCH 2/3] clocksource: add DB8500 PRCMU Timer support Mattias Wallin
2011-05-31 10:38 ` Thomas Gleixner
2011-05-31 17:00 ` Mattias Wallin
2011-05-31 21:18 ` Linus Walleij [this message]
2011-06-01 7:57 ` Mattias Wallin
2011-06-01 14:22 ` Mattias Wallin
2011-06-01 14:25 ` Russell King - ARM Linux
2011-06-01 14:31 ` Mattias Wallin
2011-06-01 14:36 ` Mattias Wallin
2011-06-01 23:35 ` Linus Walleij
2011-06-01 8:30 ` Russell King - ARM Linux
2011-06-01 8:37 ` Linus Walleij
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=BANLkTinPKbUu40066+wr3cdFRc2di-Uv6g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).