linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: boot: dts: am4372: add operating points
Date: Mon, 11 May 2015 12:02:23 -0500	[thread overview]
Message-ID: <20150511170223.GC22558@saruman.tx.rr.com> (raw)
In-Reply-To: <CAGo_u6oQ_uzO4B4ezC-Vi8_FQZWH49+6fbutdVgP5s0fL3MhrA@mail.gmail.com>

HI,

On Mon, May 11, 2015 at 11:46:13AM -0500, Nishanth Menon wrote:
> On Mon, May 11, 2015 at 10:19 AM, Felipe Balbi <balbi@ti.com> wrote:
> >
> >> in my opinion, doing a temporary hack in upstream kernel is not an
> >> elegant approach. I suggest helping review and approving Viresh's new
> >
> > however this is not a hack, right ? If we get rid of OPP_NITRO and
> > OPP_TURBO, then we will more than likely always be dealing with safe
> > OPPs (yeah, I need to confirm this since it's not on public TRM, so as
> > of now, take this statement with a grain of salt :-), moreover, even
> > though we're trying to change opp bindings, the current situation is
> > still very much accepted and will remain valid even after changing
> > binding :-)
> 
> yes - if we do have a documented subset of OPPs that are valid for all
> "variants" of AM437x, we could add that in using the legacy bindings,
> but, we will have to do a transition over to the new bindings when
> they are finalized to support all OPPs appropriately.

sounds fair to me.

> > Not to mention that people using AM43xx today might be using it under
> > invalid OPPs and decreasing silicon life; I'd assume that's a very
> > urgent detail to sort out.
> 
> While I do agree that there is always a debate between fixing things
> in kernel for bootloader issues, but it does not mean that we should
> just postpone fixing the bootloader in this case - since, at this very
> moment, we are already in broken configuration - example sitting on a
> bootloader shell does have the same impact we have at this time.

agreed, I'll cook up a patch for bootloader too.

> Lets try to help Viresh in getting his series sorted out meanwhile -
> maybe others can help as well :(

sure.

-- 
balbi
-------------- 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/20150511/b970e4dc/attachment.sig>

      reply	other threads:[~2015-05-11 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 19:57 [PATCH 1/2] arm: boot: dts: am4372: add operating points Felipe Balbi
2015-05-08 19:57 ` [PATCH 2/2] cpufreq: dt: allow driver to boot automatically Felipe Balbi
2015-05-08 20:16   ` Nishanth Menon
2015-05-09  2:29   ` Viresh Kumar
2015-06-16 21:40   ` Felipe Balbi
2015-06-16 22:04     ` Rafael J. Wysocki
2015-06-16 22:08       ` Felipe Balbi
2015-05-08 20:09 ` [PATCH 1/2] arm: boot: dts: am4372: add operating points Nishanth Menon
2015-05-08 20:12   ` Nishanth Menon
2015-05-08 20:24     ` Felipe Balbi
2015-05-11  0:23       ` Nishanth Menon
2015-05-11 15:19         ` Felipe Balbi
2015-05-11 16:46           ` Nishanth Menon
2015-05-11 17:02             ` Felipe Balbi [this message]

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=20150511170223.GC22558@saruman.tx.rr.com \
    --to=balbi@ti.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 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).