linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] Documentation: dt: add bindings for ti-cpufreq
Date: Fri, 20 Jan 2017 10:43:24 -0800	[thread overview]
Message-ID: <20170120184324.GJ7403@atomide.com> (raw)
In-Reply-To: <b7d11925-879a-9be0-fdd8-45b70e642ce1@ti.com>

* Dave Gerlach <d-gerlach@ti.com> [170119 10:32]:
> On 01/19/2017 12:07 PM, Rob Herring wrote:
> > > +	/*
> > > +	 * The three following nodes are marked with opp-suspend
> > > +	 * because they can not be enabled simultaneously on a
> > > +	 * single SoC.
> > > +	 */
> > > +	opp50 at 300000000 {
> > 
> > What's the 50, 100, 120 in the names?
> 
> Those are the names of the OPPs given in Table 5-7 of the AM335x data
> manual, seen here http://www.ti.com/lit/ds/symlink/am3359.pdf . I typically
> reference the table and document in the commit message of the actual DT
> patches but didn't here for the binding.

If you don't need the names, you could maybe use:

opp100: opp at 275000000 {
	...
};

opp200: opp at 300000000 {
	...
};
...

Regards,

Tony

  reply	other threads:[~2017-01-20 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 13:18 [PATCH v4 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
2017-01-17 13:18 ` [PATCH v4 1/4] PM / OPP: Expose _of_get_opp_desc_node as dev_pm_opp API Dave Gerlach
2017-01-18  3:14   ` Viresh Kumar
2017-01-17 13:18 ` [PATCH v4 2/4] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach
2017-01-18  3:16   ` Viresh Kumar
2017-01-19 18:07   ` Rob Herring
2017-01-19 18:31     ` Dave Gerlach
2017-01-20 18:43       ` Tony Lindgren [this message]
2017-01-23 21:48         ` Dave Gerlach
2017-01-17 13:18 ` [PATCH v4 3/4] cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime Dave Gerlach
2017-01-18  3:17   ` Viresh Kumar
2017-01-17 13:18 ` [PATCH v4 4/4] cpufreq: dt: Don't use generic platdev driver for ti-cpufreq platforms Dave Gerlach
2017-01-18  3:17   ` 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=20170120184324.GJ7403@atomide.com \
    --to=tony@atomide.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).