From: Kevin Hilman <khilman@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Mike Turquette <mturquette@linaro.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH V5 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot
Date: Thu, 03 Oct 2013 13:13:15 -0700 [thread overview]
Message-ID: <87d2nmun8k.fsf@linaro.org> (raw)
In-Reply-To: <524DA41C.7000809@ti.com> (Nishanth Menon's message of "Thu, 3 Oct 2013 12:06:36 -0500")
Nishanth Menon <nm@ti.com> writes:
> fixing Benoit's mail ID.
> On 10/03/2013 11:43 AM, Kevin Hilman wrote:
>> Hi Nishanth,
>>
>> Nishanth Menon <nm@ti.com> writes:
>>
>>> The following version 5 of the series arose from trying to use
>>> BeagleBoard-XM (OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0.
>>> This series enables the generic cpufreq-cpu0 driver to be used in
>>> device tree enabled boot while maintaining support of the legacy
>>> omap-cpufreq driver when used in non device tree enabled boot.
>>
>> What's the status of this series? Is it still waiting on the clock DT
>> changes?
>
> yes - i do have a new series lined up at the moment here[1] - trying
> to ensure everything is dandy before public post. ofcourse, we'd like
> to ensure we have feedback on tero's series[2]. I am now working on
> ensuring ABB regulator[3](again depends on Tero's series) fits on top
> of Mike's voltage notifier series[4]
>
> So, yep, everything is blocked due to lack of feedback on Tero's
> series [2].
OK, thanks for the update.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot
Date: Thu, 03 Oct 2013 13:13:15 -0700 [thread overview]
Message-ID: <87d2nmun8k.fsf@linaro.org> (raw)
In-Reply-To: <524DA41C.7000809@ti.com> (Nishanth Menon's message of "Thu, 3 Oct 2013 12:06:36 -0500")
Nishanth Menon <nm@ti.com> writes:
> fixing Benoit's mail ID.
> On 10/03/2013 11:43 AM, Kevin Hilman wrote:
>> Hi Nishanth,
>>
>> Nishanth Menon <nm@ti.com> writes:
>>
>>> The following version 5 of the series arose from trying to use
>>> BeagleBoard-XM (OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0.
>>> This series enables the generic cpufreq-cpu0 driver to be used in
>>> device tree enabled boot while maintaining support of the legacy
>>> omap-cpufreq driver when used in non device tree enabled boot.
>>
>> What's the status of this series? Is it still waiting on the clock DT
>> changes?
>
> yes - i do have a new series lined up at the moment here[1] - trying
> to ensure everything is dandy before public post. ofcourse, we'd like
> to ensure we have feedback on tero's series[2]. I am now working on
> ensuring ABB regulator[3](again depends on Tero's series) fits on top
> of Mike's voltage notifier series[4]
>
> So, yep, everything is blocked due to lack of feedback on Tero's
> series [2].
OK, thanks for the update.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Mike Turquette <mturquette@linaro.org>,
Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH V5 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot
Date: Thu, 03 Oct 2013 13:13:15 -0700 [thread overview]
Message-ID: <87d2nmun8k.fsf@linaro.org> (raw)
In-Reply-To: <524DA41C.7000809@ti.com> (Nishanth Menon's message of "Thu, 3 Oct 2013 12:06:36 -0500")
Nishanth Menon <nm@ti.com> writes:
> fixing Benoit's mail ID.
> On 10/03/2013 11:43 AM, Kevin Hilman wrote:
>> Hi Nishanth,
>>
>> Nishanth Menon <nm@ti.com> writes:
>>
>>> The following version 5 of the series arose from trying to use
>>> BeagleBoard-XM (OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0.
>>> This series enables the generic cpufreq-cpu0 driver to be used in
>>> device tree enabled boot while maintaining support of the legacy
>>> omap-cpufreq driver when used in non device tree enabled boot.
>>
>> What's the status of this series? Is it still waiting on the clock DT
>> changes?
>
> yes - i do have a new series lined up at the moment here[1] - trying
> to ensure everything is dandy before public post. ofcourse, we'd like
> to ensure we have feedback on tero's series[2]. I am now working on
> ensuring ABB regulator[3](again depends on Tero's series) fits on top
> of Mike's voltage notifier series[4]
>
> So, yep, everything is blocked due to lack of feedback on Tero's
> series [2].
OK, thanks for the update.
Kevin
next prev parent reply other threads:[~2013-10-03 20:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 19:06 [PATCH V5 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` [PATCH V5 1/6] clk: OMAP: introduce device tree binding to kernel clock data Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-13 23:51 ` Mike Turquette
2013-05-13 23:51 ` Mike Turquette
2013-05-13 23:51 ` Mike Turquette
2013-05-16 17:43 ` Tony Lindgren
2013-05-16 17:43 ` Tony Lindgren
2013-05-16 19:46 ` Mike Turquette
2013-05-16 19:46 ` Mike Turquette
2013-05-16 20:02 ` Tony Lindgren
2013-05-16 20:02 ` Tony Lindgren
2013-05-08 19:06 ` [PATCH V5 2/6] ARM: dts: OMAP3: add clock nodes for CPU Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` [PATCH V5 3/6] ARM: dts: OMAP4: " Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` [PATCH V5 4/6] ARM: dts: AM33XX: " Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` [PATCH V5 5/6] ARM: OMAP2+: AM33XX: add lateinit hook for calling pm late init Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` [PATCH V5 6/6] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-05-08 19:06 ` Nishanth Menon
2013-10-03 16:43 ` [PATCH V5 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Kevin Hilman
2013-10-03 16:43 ` Kevin Hilman
2013-10-03 17:06 ` Nishanth Menon
2013-10-03 17:06 ` Nishanth Menon
2013-10-03 17:06 ` Nishanth Menon
2013-10-03 20:13 ` Kevin Hilman [this message]
2013-10-03 20:13 ` Kevin Hilman
2013-10-03 20:13 ` Kevin Hilman
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=87d2nmun8k.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.