All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: Is cpufreq-dt safe without regulator support?
Date: Wed, 18 Mar 2015 11:20:17 +0100	[thread overview]
Message-ID: <20150318102017.GN4638@lukather> (raw)
In-Reply-To: <CAKohponKrwm47YQ0oRjYo9tMBu4gkOvi8fTWCuaWA1SNbT0b9g@mail.gmail.com>

On Wed, Mar 18, 2015 at 03:41:36PM +0530, Viresh Kumar wrote:
> On 18 March 2015 at 15:33, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > Another solution would be to have the safe OPPs in the DTSI, and the
> > one that requires some PMIC support in the board DTS.
> 
> Yes .dtsi and .dts files do get merged, but I don't think that will
> happen in case
> of OPPs as well. As we are talking about a single field with any array of OPP
> pairs.

Sorry, what I meant was to redefine the whole OPPs set in the DTS,
overriding the one in the DTSI.

That would add some duplication, but still far less than what you
first suggested in our case.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150318/4bd1ef80/attachment.sig>

  reply	other threads:[~2015-03-18 10:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  7:45 Is cpufreq-dt safe without regulator support? wens Tsai
2015-03-17  8:47 ` Viresh Kumar
2015-03-18  1:40   ` wens Tsai
2015-03-18  3:53     ` Viresh Kumar
2015-03-18 10:03       ` Maxime Ripard
2015-03-18 10:11         ` Viresh Kumar
2015-03-18 10:20           ` Maxime Ripard [this message]
2015-03-18 10:35             ` Viresh Kumar
2015-03-17 18:22 ` Lucas Stach
2015-03-17 19:26   ` Nishanth Menon

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=20150318102017.GN4638@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.