All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
	sebastian.hesselbarth@gmail.com, zmxu@marvell.com,
	jszhang@marvell.com,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support
Date: Wed, 19 Aug 2015 10:17:57 +0200	[thread overview]
Message-ID: <20150819081757.GA1089@kwain> (raw)
In-Reply-To: <20150818145925.GF31148@linux>

On Tue, Aug 18, 2015 at 08:29:25PM +0530, Viresh Kumar wrote:
> On 18-08-15, 16:39, Antoine Tenart wrote:
> > However, it seems the OPP-v2 table takes precedence over the old one.
> > When a default OPP-v2 table is supplied in the device tree, if the
> > bootloader supplies an OPP table the old way it won't be taken into
> > account.
> > 
> > So if I understood correctly, this won't work here for the BG2Q.
> 
> Didn't understood it completely. Are you saying that your dtb will
> have two operating-points tables ?

Yes. If the device tree has an OPP-v2 table and the bootloader modify it
to add an old OPP table at boot, the one added by the bootloader won't
be taken into account by the kernel.

> The deal is that for any device, parsing of opp-v2 will be attempted
> first. If its not available, then opp-v1 will be tried. But this is
> per-device. So, one device can have opp-v2 tables and other one can do
> v1 type.

Sure. OPP-v2 tables can be used for devices having an up-to-date
bootloader or if the bootloader do not modify the device tree at boot
time to add an (old) OPP table.

Antoine

-- 
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] ARM: berlin: add cpufreq support
Date: Wed, 19 Aug 2015 10:17:57 +0200	[thread overview]
Message-ID: <20150819081757.GA1089@kwain> (raw)
In-Reply-To: <20150818145925.GF31148@linux>

On Tue, Aug 18, 2015 at 08:29:25PM +0530, Viresh Kumar wrote:
> On 18-08-15, 16:39, Antoine Tenart wrote:
> > However, it seems the OPP-v2 table takes precedence over the old one.
> > When a default OPP-v2 table is supplied in the device tree, if the
> > bootloader supplies an OPP table the old way it won't be taken into
> > account.
> > 
> > So if I understood correctly, this won't work here for the BG2Q.
> 
> Didn't understood it completely. Are you saying that your dtb will
> have two operating-points tables ?

Yes. If the device tree has an OPP-v2 table and the bootloader modify it
to add an old OPP table at boot, the one added by the bootloader won't
be taken into account by the kernel.

> The deal is that for any device, parsing of opp-v2 will be attempted
> first. If its not available, then opp-v1 will be tried. But this is
> per-device. So, one device can have opp-v2 tables and other one can do
> v1 type.

Sure. OPP-v2 tables can be used for devices having an up-to-date
bootloader or if the bootloader do not modify the device tree at boot
time to add an (old) OPP table.

Antoine

-- 
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-19  8:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 11:46 [PATCH v2 0/6] ARM: berlin: add cpufreq support Antoine Tenart
2015-08-18 11:46 ` Antoine Tenart
2015-08-18 11:46 ` [PATCH v2 1/6] clk: berlin: move MAX_CLKS out of drivers/clk/berlin Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-25 20:25   ` Michael Turquette
2015-08-25 20:25     ` Michael Turquette
2015-08-18 11:46 ` [PATCH v2 2/6] clk: berlin: add cpuclk Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 11:46 ` [PATCH v2 3/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2Q Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 11:46 ` [PATCH v2 4/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2 Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 11:46 ` [PATCH v2 5/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2CD Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 11:46 ` [PATCH v2 6/6] ARM: berlin: register cpufreq-dt Antoine Tenart
2015-08-18 11:46   ` Antoine Tenart
2015-08-18 12:56 ` [PATCH v2 0/6] ARM: berlin: add cpufreq support Viresh Kumar
2015-08-18 12:56   ` Viresh Kumar
2015-08-18 14:39   ` Antoine Tenart
2015-08-18 14:39     ` Antoine Tenart
2015-08-18 14:59     ` Viresh Kumar
2015-08-18 14:59       ` Viresh Kumar
2015-08-19  8:17       ` Antoine Tenart [this message]
2015-08-19  8:17         ` Antoine Tenart

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=20150819081757.GA1089@kwain \
    --to=antoine.tenart@free-electrons.com \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=viresh.kumar@linaro.org \
    --cc=zmxu@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.