From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Anton Vorontsov <avorontsov@mvista.com>
Cc: Paul Walmsley <paul@pwsan.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Benoit Cousson <b-cousson@ti.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Tony Lindgren <tony@atomide.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Colin Cross <ccross@android.com>,
Varun Swara <Varun.Swara@arm.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: TWD: Consolidate local timers support
Date: Tue, 30 Nov 2010 22:16:15 +0000 [thread overview]
Message-ID: <20101130221615.GA9424@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101130173105.GA26929@oksana.dev.rtsoft.ru>
On Tue, Nov 30, 2010 at 08:31:05PM +0300, Anton Vorontsov wrote:
> This greatly reduces amount of platform-specific code, and thus
> makes it easier to add local timers for new platforms.
>
> Technically, it's not very nice to place machine-specific (i.e.
> local_timer_setup()) routine into the machine-agnostic code.
> But the true thing is: currently all machines want the same thing.
I've just been talking to someone this week about (presumably) non-TWD
local timers.
I suspect your patch is all part of the "lets try to get ARM building
for every platform in the world in one kernel" but it's really painful
to see carefully abstracted interfaces being trodden on by this argument
- which is just going to make things more difficult in the future.
next prev parent reply other threads:[~2010-11-30 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 17:31 [PATCH] ARM: TWD: Consolidate local timers support Anton Vorontsov
2010-11-30 22:16 ` Russell King - ARM Linux [this message]
2010-12-02 15:24 ` Catalin Marinas
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=20101130221615.GA9424@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Varun.Swara@arm.com \
--cc=avorontsov@mvista.com \
--cc=b-cousson@ti.com \
--cc=catalin.marinas@arm.com \
--cc=ccross@android.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=srinidhi.kasagar@stericsson.com \
--cc=tony@atomide.com \
/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