From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Mark Rutland <mark.rutland@arm.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 1/2] Documentation: dt: add bindings for ti-cpufreq
Date: Thu, 8 Sep 2016 09:05:57 +0530 [thread overview]
Message-ID: <20160908033557.GQ27345@vireshk-i7> (raw)
In-Reply-To: <57D025E8.6030202@ti.com>
On 07-09-16, 09:36, Dave Gerlach wrote:
> On 09/07/2016 12:12 AM, Viresh Kumar wrote:
> >On 31-08-16, 21:53, Dave Gerlach wrote:
> >>+In 'operating-points-v2' table:
> >>+- compatible: Should be
> >>+ - 'operating-points-v2-ti-am3352-cpu' for am335x SoCs
> >>+ - 'operating-points-v2-ti-am4372-cpu' for am43xx SoCs
> >>+ - 'operating-points-v2-ti-dra7-cpu' for dra7xx/am57xx SoCs
> >
> >Why do you need SoC specific compatible here? Are you defining new
> >fields in OPP tables for your SoC ? How are the tables for your case
> >going to differ from the ones using "operating-points-v2" compatible
> >string?
> >
>
> I thought you had suggested that I do this in your comments from v1, but I
> guess that was dependent on whether or not I put the properties I have
> inserted into the cpu node into the operating-points table instead.
Yes.
> I still
> have gotten no comments from any DT maintainers so I left it as is. I am
> still not sure if that is acceptable.
@Rob: Can you please share your views on the new properties being
added to the CPU node ?
--
viresh
next prev parent reply other threads:[~2016-09-08 3:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 2:53 [PATCH v2 0/2] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
[not found] ` <20160901025328.376-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-09-01 2:53 ` [PATCH v2 1/2] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach
2016-09-07 5:12 ` Viresh Kumar
2016-09-07 14:36 ` Dave Gerlach
2016-09-08 3:35 ` Viresh Kumar [this message]
2016-09-12 20:56 ` Dave Gerlach
[not found] ` <20160901025328.376-2-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-09-19 21:14 ` Rob Herring
2016-09-20 14:19 ` Dave Gerlach
2016-09-01 2:53 ` [PATCH v2 2/2] cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime Dave Gerlach
2016-09-07 5:20 ` Viresh Kumar
2016-09-07 15:04 ` Dave Gerlach
[not found] ` <57D02C85.7020300-l0cyMroinI0@public.gmane.org>
2016-09-08 3:39 ` Viresh Kumar
2016-09-21 19:34 ` Dave Gerlach
2016-09-23 5:19 ` Viresh Kumar
2016-09-23 16:17 ` Dave Gerlach
[not found] ` <57E555B3.2010304-l0cyMroinI0@public.gmane.org>
2016-09-26 4:33 ` Viresh Kumar
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=20160908033557.GQ27345@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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 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).