From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/3] OPP: Allow multiple OPP tables to be passed via DT
Date: Wed, 13 May 2015 10:11:29 +0530 [thread overview]
Message-ID: <20150513044129.GC28858@linux> (raw)
In-Reply-To: <555225A0.8050707@ti.com>
On 12-05-15, 11:09, Nishanth Menon wrote:
> On 04/30/2015 07:08 AM, Viresh Kumar wrote:
> > (sort of an eeprom) and knowing characteristics of the SoC.
>
> they are more like prom than eeprom in many instances.
Will replace.
> With some SoCs like AM335x - thanks to some brain dead incompatible
> hardware design choices, this might end up as a big list or various
> OPP tables. but overall, I must prefer this approach as well.
>
> Thanks for proposing this. will be great to see examples documented in
> bindings doc as well.
Right.
--
viresh
next prev parent reply other threads:[~2015-05-13 4:41 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 12:07 [PATCH V4 0/3] OPP: Introduce OPP (V2) bindings Viresh Kumar
2015-04-30 12:07 ` [PATCH V4 1/3] OPP: Redefine bindings to overcome shortcomings Viresh Kumar
2015-05-04 12:12 ` Mark Brown
2015-05-05 10:48 ` Viresh Kumar
2015-05-05 10:57 ` Mark Brown
2015-05-05 11:43 ` Viresh Kumar
2015-05-05 17:12 ` Mark Brown
2015-05-06 6:53 ` Viresh Kumar
2015-05-07 5:52 ` Stephen Boyd
2015-05-07 11:02 ` Mark Brown
2015-05-07 21:18 ` Stephen Boyd
2015-05-07 22:18 ` Mark Brown
2015-05-08 6:47 ` Viresh Kumar
2015-05-08 10:58 ` Mark Brown
2015-05-08 11:01 ` Viresh Kumar
2015-05-11 1:07 ` Nishanth Menon
2015-05-12 5:20 ` Viresh Kumar
2015-05-12 19:01 ` Michael Turquette
2015-05-12 19:14 ` Nishanth Menon
2015-05-12 19:41 ` Mark Brown
2015-05-12 19:57 ` Nishanth Menon
2015-05-13 11:54 ` Mark Brown
2015-05-13 14:24 ` Nishanth Menon
2015-05-13 15:07 ` Mark Brown
2015-05-13 15:43 ` Nishanth Menon
2015-05-07 12:13 ` Viresh Kumar
2015-05-07 21:30 ` Stephen Boyd
2015-05-08 6:49 ` Viresh Kumar
2015-05-11 1:02 ` Nishanth Menon
2015-05-12 5:16 ` Viresh Kumar
2015-05-12 16:04 ` Nishanth Menon
2015-05-13 5:05 ` Viresh Kumar
2015-05-13 15:00 ` Nishanth Menon
2015-05-13 15:16 ` Mark Brown
2015-05-13 16:14 ` Nishanth Menon
2015-05-13 16:21 ` Mark Brown
2015-05-13 16:34 ` Nishanth Menon
2015-05-12 16:19 ` Felipe Balbi
2015-05-13 4:45 ` Viresh Kumar
2015-05-12 21:42 ` Michael Turquette
2015-05-13 8:55 ` Viresh Kumar
2015-05-13 11:03 ` Mark Brown
2015-05-14 0:32 ` Michael Turquette
[not found] ` <CAKohpokeKtcJdrBcPZBBPR2zfJgpvuM_=wRaX5q1Uto2qx1oHQ@mail.gmail.com>
2015-05-15 14:15 ` Viresh Kumar
2015-05-15 15:43 ` Nishanth Menon
2015-05-15 17:27 ` Rob Herring
2015-05-21 6:02 ` Nishanth Menon
2015-05-22 14:04 ` Viresh Kumar
2015-05-22 16:04 ` Rob Herring
2015-05-22 17:42 ` Nishanth Menon
2015-05-26 5:25 ` Viresh Kumar
2015-05-20 0:51 ` Stephen Boyd
2015-05-20 2:07 ` Viresh Kumar
2015-05-20 19:39 ` Stephen Boyd
2015-05-21 4:33 ` Viresh Kumar
2015-05-25 11:59 ` Viresh Kumar
2015-04-30 12:08 ` [PATCH V4 2/3] OPP: Allow multiple OPP tables to be passed via DT Viresh Kumar
2015-05-12 16:09 ` Nishanth Menon
2015-05-13 4:41 ` Viresh Kumar [this message]
2015-05-20 0:52 ` Stephen Boyd
2015-04-30 12:08 ` [PATCH V4 3/3] OPP: Add 'opp-next' in operating-points-v2 bindings Viresh Kumar
2015-05-12 21:47 ` Michael Turquette
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=20150513044129.GC28858@linux \
--to=viresh.kumar@linaro.org \
--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).