devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@stlinux.com,
	rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, ajitpal.singh@st.com
Subject: Re: [PATCH v2 0/9] cpufreq: Introduce support for ST's cpufreq functionality
Date: Wed, 8 Jul 2015 11:59:58 +0100	[thread overview]
Message-ID: <20150708105958.GO3182@x1> (raw)
In-Reply-To: <20150708105054.GB1805@linux>

On Wed, 08 Jul 2015, Viresh Kumar wrote:

> On 24-06-15, 14:58, Lee Jones wrote:
> > This driver reads very platform specific information in from Device Tree
> > and translates it into frequency tables.  The generic drivers then use the
> > tables to conduct frequency and voltage scaling in the normal way.
> > 
> > There are 'ARM' patches in the set which are not necessarily related to CPUFreq,
> > but are required to get it to work.  Anyone who is not interested in general STi
> > DT changes can safely ignore these.
> > 
> > v1 => v2:
> >  - CPUFreq is no longer it's own device in DT; instead:
> >    - It is probed from the platform area
> >    - Key properties have been moved into the CPU's node
> >  - Driver is less generic [ST => STI]
> >  - Documentation has been updated
> >    - Point one (above) has been accounted for
> >    - Example of bootloader supplied node has been provided
> >  - GPL licensing has been updated to reflected the header
> >  - Kconfig disparity has been rectified [bool => tristate]
> 
> Sorry for being so late to get back to this.. Was tooo busy :(

No problem.  So long as it's still on your radar.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2015-07-08 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 13:58 [PATCH v2 0/9] cpufreq: Introduce support for ST's cpufreq functionality Lee Jones
2015-06-24 13:59 ` [PATCH v2 1/9] ARM: STi: STiH407: Provide generic (safe) DVFS configuration Lee Jones
2015-06-24 13:59 ` [PATCH v2 2/9] ARM: STi: STiH407: Provide CPU with clocking information Lee Jones
2015-06-24 13:59 ` [PATCH v2 3/9] ARM: STi: STiH407: Link CPU with its voltage supply Lee Jones
2015-06-24 13:59 ` [PATCH v2 4/9] ARM: STi: STiH407: Provide CPU with a means to look-up Major number Lee Jones
2015-06-24 13:59 ` [PATCH v2 5/9] ARM: STi: Register CPUFreq device Lee Jones
2015-06-24 13:59 ` [PATCH v2 6/9] ARM: STi: STiH407: Move PWM nodes STiH407 => STiH407-family Lee Jones
     [not found] ` <1435154348-28840-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-06-24 13:59   ` [PATCH v2 7/9] ARM: multi_v7_defconfig: Enable support for PWM Regulators Lee Jones
2015-06-24 14:52     ` Javier Martinez Canillas
2015-06-25  8:42       ` Lee Jones
2015-06-25  9:18         ` Javier Martinez Canillas
2015-06-25 15:02           ` Lee Jones
2015-06-25 16:29             ` Javier Martinez Canillas
2015-07-01 12:31               ` Lee Jones
2015-07-08 10:50   ` [PATCH v2 0/9] cpufreq: Introduce support for ST's cpufreq functionality Viresh Kumar
2015-07-08 10:59     ` Lee Jones [this message]
2015-07-08 11:12       ` Viresh Kumar
2015-06-24 13:59 ` [PATCH v2 8/9] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Lee Jones
2015-06-24 13:59 ` [PATCH v2 9/9] cpufreq: st: Provide runtime initialised driver for ST's platforms Lee Jones

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=20150708105958.GO3182@x1 \
    --to=lee.jones@linaro.org \
    --cc=ajitpal.singh@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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).