From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Daniel Mack <daniel@zonque.org>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rafael J Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 3/4] ARM: dts: pxa: add pxa27x cpu operating points
Date: Wed, 02 Nov 2016 22:54:19 +0100 [thread overview]
Message-ID: <874m3pzgxg.fsf@belgarion.home> (raw)
In-Reply-To: <1477943696-23477-4-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Mon, 31 Oct 2016 20:54:55 +0100")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Add the relevant data taken from the PXA27x Electrical, Mechanical, and
> Thermal Specfication. This will be input data for cpufreq-dt driver.
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> ---
> Since v2: opp definition amended as per Viresh's comment
Queued to pxa/dt.
--
Robert
next prev parent reply other threads:[~2016-11-02 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 19:54 [PATCH v3 0/4] PXA cpufreq conversion to clock API Robert Jarzmik
2016-10-31 19:54 ` [PATCH v3 1/4] cpufreq: pxa: use generic platdev driver for device-tree Robert Jarzmik
2016-10-31 19:54 ` [PATCH v3 2/4] ARM: dts: pxa: add pxa25x cpu operating points Robert Jarzmik
2016-11-02 21:53 ` Robert Jarzmik
2016-10-31 19:54 ` [PATCH v3 3/4] ARM: dts: pxa: add pxa27x " Robert Jarzmik
2016-11-02 21:54 ` Robert Jarzmik [this message]
2016-10-31 19:54 ` [PATCH v3 4/4] cpufreq: pxa: convert to clock API Robert Jarzmik
2016-11-02 4:45 ` [PATCH v3 0/4] PXA cpufreq conversion " Viresh Kumar
2016-11-02 21:49 ` Robert Jarzmik
[not found] ` <87d1idzh56.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2016-11-03 2:16 ` Viresh Kumar
2016-11-14 0:37 ` Rafael J. Wysocki
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=874m3pzgxg.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--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).