linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] cpufreq-cpu0: allow OPP table supplied by platform
Date: Thu, 13 Mar 2014 19:44:24 +0800	[thread overview]
Message-ID: <20140313194424.122ec572@xhacker> (raw)
In-Reply-To: <CAKohpoke1i8xmKProgF+ki7Q=Q+YxbPnewdtbyPqu7857DLLWA@mail.gmail.com>

Fixing lakml :)

sorry

On Thu, 13 Mar 2014 03:56:46 -0700
Viresh Kumar <viresh.kumar@linaro.org> wrote:

> Fixing Rafael's id.
> 
> On 13 March 2014 16:25, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 13 March 2014 16:18, Jisheng Zhang <jszhang@marvell.com> wrote:
> >> Hi all,
> >>
> >> cpufreq-cpu0 is suitable for Marvell Berlin SoC. But there's one issue
> >> to address. The opp is different between chips even on the same step
> >> SoC, BG2Q for example. we can calculate the OPP table from the value of
> >> one OTP register. We have two solutions:
> >>
> >> 1. bootloader reads OTP register and calculate the OPP table then change
> >> dtb danamically
> >>
> >> 2. supply one driver in mach-berlin to initialize the OPP table; and
> >> modify cpufreq-cpu0 to allow platform supply OPP table, fall back to
> >> of_init_opp_table() if there's no OPP table.
> >>
> >> Which solution is better?
> >
> > I think we can go ahead with second option here. We can just check if opp
> > tables are already initialized or not. In case they are, don't probe from
> > dt..
> >
> > But lets see with others have to say here..
> >
> > --
> > viresh

       reply	other threads:[~2014-03-13 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140313184859.7d6f6512@xhacker>
     [not found] ` <CAKohpokLv0m+Cky7nCUOgP-djTMrA6jyka_EZ07+_exCAexXXg@mail.gmail.com>
     [not found]   ` <CAKohpoke1i8xmKProgF+ki7Q=Q+YxbPnewdtbyPqu7857DLLWA@mail.gmail.com>
2014-03-13 11:44     ` Jisheng Zhang [this message]
2014-03-13 17:43       ` [RFC] cpufreq-cpu0: allow OPP table supplied by platform Sören Brinkmann
2014-03-14 12:32       ` Shawn Guo
2014-03-14 15:36         ` Nishanth Menon
2014-03-14 19:32           ` Dave Gerlach

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=20140313194424.122ec572@xhacker \
    --to=jszhang@marvell.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).