From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Liviu Dudau <liviu.dudau@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
Sekhar Nori <nsekhar@ti.com>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
kernel@stlinux.com, linux-arm-kernel@axis.com,
Florian Fainelli <f.fainelli@gmail.com>,
Wei Xu <xuwei5@hisilicon.com>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
Maxime Coquelin <maxime.coquelin@st.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Sudeep Holla <sudeep.holla@arm.com>, Jun Nie <jun.nie@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
Jesper Nilsson <jesper.nilsson@axis.com>, Lars Persson <lar>
Subject: Re: [PATCH v1] ARM: clocksource: make ARM_GLOBAL_TIMER selectable
Date: Wed, 27 Apr 2016 11:41:10 +0100 [thread overview]
Message-ID: <20160427104110.GU5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <571FC2EC.9090605@ti.com>
On Tue, Apr 26, 2016 at 10:35:08PM +0300, Grygorii Strashko wrote:
> On 04/26/2016 07:02 PM, Liviu Dudau wrote:
> > Well, SoC-B has the GT *and* the DT node, so what is the problem with
> > enabling it for SoC-B? If there are reasons not to use the Global Timer
> > on SoC-B, surely a better option would be to mark it in DT with status = "disabled";
>
> This was rejected [2]. DT describes HW and if it is functional the status = "disabled"
> is not good choice.
> ARM GT can't be used as clocksource/sched_clock/clockevent when CPUFreq or
> CPUIdle are enabled :(, and this is Linux specific functionality and
> not HW description.
Sorry, but we don't want to have to disable drivers in the kernel just
because one platform has a problem (consider the single zImage case
where it may be required that the global timer is enabled for some
platform to boot - it becomes mandatory in single zImage at that point.)
Maybe a linux-specific property is needed here - "linux,low-power-unstable"
or something like that?
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-04-27 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 15:28 [PATCH v1] ARM: clocksource: make ARM_GLOBAL_TIMER selectable Grygorii Strashko
2016-04-26 16:02 ` Liviu Dudau
[not found] ` <20160426160245.GI28464-2JSQmVVBSi7ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2016-04-26 19:35 ` Grygorii Strashko
2016-04-27 10:12 ` Liviu Dudau
[not found] ` <20160427101214.GK28464-2JSQmVVBSi7ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2016-04-27 13:46 ` Grygorii Strashko
2016-04-27 10:15 ` Robin Murphy
[not found] ` <57209154.6050508-5wv7dgnIgG8@public.gmane.org>
2016-04-27 13:25 ` Grygorii Strashko
2016-04-27 10:41 ` Russell King - ARM Linux [this message]
[not found] ` <20160427104110.GU5783-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2016-04-27 13:31 ` Grygorii Strashko
2016-04-27 16:24 ` Tony Lindgren
2016-04-27 21:06 ` Russell King - ARM Linux
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=20160427104110.GU5783@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=jesper.nilsson@axis.com \
--cc=jun.nie@linaro.org \
--cc=kernel@pengutronix.de \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=maxime.coquelin@st.com \
--cc=michal.simek@xilinx.com \
--cc=nsekhar@ti.com \
--cc=olof@lixom.net \
--cc=shawnguo@kernel.org \
--cc=srinivas.kandagatla@gmail.com \
--cc=sudeep.holla@arm.com \
--cc=tony@atomide.com \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).