From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Rob Herring <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/2] ARM: simplify timer initialisation and remove arm_timer.h inclusion
Date: Mon, 18 May 2015 11:42:24 +0100 [thread overview]
Message-ID: <20150518104223.GT2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <554239D5.4080301@arm.com>
On Thu, Apr 30, 2015 at 03:19:01PM +0100, Sudeep Holla wrote:
>
>
> On 30/04/15 15:09, Rob Herring wrote:
> >On Thu, Apr 30, 2015 at 5:44 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
> >>The header asm/hardware/arm_timer.h is included in various machine
> >>specific files to access TIMER_CTRL and initialise to a known state.
> >>However that's not required as the clock{source,event} driver timer-sp
> >>initialises all the timer being used.
> >
> >I believe the idea is not to initialize the timers being used, but the
> >ones not being used and perhaps left running by the bootloader. Cases
> >where the interrupt is shared could cause a problem.
> >
>
> Ah OK, makes sense. I will wait for Russell to confirm. The main idea
> was to keep the header file having offsets local to driver/clocksource
> and avoid sharing it in include/linux but looks like that's not possible.
An alternative would be to have a new function, something like
sp804_disable() which takes the virtual address of the timer.
That'd still allow the platforms to disable all timers, but
without exposing the register stuff to them.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-05-18 10:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:44 [PATCH 0/2] ARM: move Dual-Timer SP804 driver to drivers/clocksource Sudeep Holla
2015-04-30 10:44 ` [PATCH 1/2] ARM: simplify timer initialisation and remove arm_timer.h inclusion Sudeep Holla
2015-04-30 14:09 ` Rob Herring
2015-04-30 14:19 ` Sudeep Holla
2015-05-15 18:03 ` Sudeep Holla
2015-05-18 10:33 ` Catalin Marinas
2015-05-18 10:38 ` Sudeep Holla
2015-05-18 10:42 ` Russell King - ARM Linux [this message]
2015-05-18 10:44 ` Sudeep Holla
2015-05-18 10:40 ` Russell King - ARM Linux
2015-05-18 10:43 ` Sudeep Holla
2015-04-30 10:44 ` [PATCH 2/2] ARM: move Dual-Timer SP804 driver to drivers/clocksource Sudeep Holla
2015-05-18 12:44 ` [PATCH v2 0/2] " Sudeep Holla
2015-05-18 12:44 ` [PATCH v2 1/2] ARM: introduce sp804_timer_disable and remove arm_timer.h inclusion Sudeep Holla
2015-05-18 12:44 ` [PATCH v2 2/2] ARM: move Dual-Timer SP804 driver to drivers/clocksource Sudeep Holla
2015-05-18 13:47 ` [PATCH v2 0/2] " Russell King - ARM Linux
2015-05-18 14:05 ` Sudeep Holla
2015-05-18 14:34 ` Thomas Gleixner
2015-05-18 15:32 ` Sudeep Holla
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=20150518104223.GT2067@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Catalin.Marinas@arm.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®