From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@gmail.com>
Subject: Re: [PATCH v3 0/2] arm: remove cpu_efficiency
Date: Tue, 24 Oct 2017 15:31:54 +0100 [thread overview]
Message-ID: <316592bf-5aa4-3847-79cd-3a26adbb1231@arm.com> (raw)
In-Reply-To: <20171024105227.GD20805@n2100.armlinux.org.uk>
Hi Russel,
Thanks for the review!
On 24/10/17 11:52, Russell King - ARM Linux wrote:
> On Tue, Oct 24, 2017 at 11:27:16AM +0100, Dietmar Eggemann wrote:
>> With the dt related patches for exynos and renesas now in the
>> appropriated for-next branches for v4.15 there are no Cortex-A15/A7 arm
>> big.LITTLE systems left relying on the 'cpu_efficiency/clock-frequency
>> dt property' based solution anymore.
>
> This is way too early to remove support for something that has been
> in place since 2012. As you've just shown, people are using it with
> DT files today. We don't know how long people will persist using
> older files, and we don't know whether there are DT files out in the
> wild that we don't know about.
Understood. But do we really care about out of tree dt files?
In case the mentioned exynos and renesas Cortex-A15/A7 platforms change
to using 'capacity-dmips-mhz' in v4.15 there shouldn't be any
Cortex-A15/A7 platforms in mainline left using the cpu_efficiency
solution anymore.
> Our general rule is that we maintain compatibility for older DT.
OK.
> NAK.
Then I still send out [2/2] separately.
next prev parent reply other threads:[~2017-10-24 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:27 Dietmar Eggemann
2017-10-24 10:27 ` [PATCH v3 1/2] arm: topology: " Dietmar Eggemann
2017-10-24 10:27 ` [PATCH v3 2/2] arm: topology: add missing of_node_put() for cpu device node Dietmar Eggemann
2017-10-24 10:52 ` [PATCH v3 0/2] arm: remove cpu_efficiency Russell King - ARM Linux
2017-10-24 14:31 ` Dietmar Eggemann [this message]
2017-11-24 11:57 ` Dietmar Eggemann
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=316592bf-5aa4-3847-79cd-3a26adbb1231@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=juri.lelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®