From: Kevin Hilman <khilman@linaro.org>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
hvaibhav@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Remove unused voltagedomain data for AM33xx
Date: Fri, 14 Jun 2013 07:01:09 -0700 [thread overview]
Message-ID: <8738skaj16.fsf@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306140243380.5514@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 14 Jun 2013 02:46:33 +0000 (UTC)")
Paul Walmsley <paul@pwsan.com> writes:
> cc Kevin, Vaibhav
>
> On Thu, 13 Jun 2013, Rajendra Nayak wrote:
>
>> The powerdomain framework today expects to always have a voltagedomain
>> associated with a given powerdomain. We already have AM33xx which
>> has no Voltage Controller/Voltage Processor as part of PRCM.
>> There are more SoCs' to follow starting with AM437x and DRA7xx
>> which do not have VC/VP.
>>
>> Instead of adding dummy voltage domain data files, make the powerdomain
>> framework aware of the fact that some SoCs' might not really have
>> scalable voltage domains.
>
> Fine with me in principle if AM335x doesn't support voltage scaling.
> Vaibhav, if this is okay for you, please ack it.
>
> Then, in terms of merging, probably Kevin would be the right person for
> this since he's done much of the voltagedomain work.
Yeah, I'll take this series after the minor issues I commented on are
fixed, and Vaivhav ack's the AM33xx parts.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Remove unused voltagedomain data for AM33xx
Date: Fri, 14 Jun 2013 07:01:09 -0700 [thread overview]
Message-ID: <8738skaj16.fsf@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306140243380.5514@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 14 Jun 2013 02:46:33 +0000 (UTC)")
Paul Walmsley <paul@pwsan.com> writes:
> cc Kevin, Vaibhav
>
> On Thu, 13 Jun 2013, Rajendra Nayak wrote:
>
>> The powerdomain framework today expects to always have a voltagedomain
>> associated with a given powerdomain. We already have AM33xx which
>> has no Voltage Controller/Voltage Processor as part of PRCM.
>> There are more SoCs' to follow starting with AM437x and DRA7xx
>> which do not have VC/VP.
>>
>> Instead of adding dummy voltage domain data files, make the powerdomain
>> framework aware of the fact that some SoCs' might not really have
>> scalable voltage domains.
>
> Fine with me in principle if AM335x doesn't support voltage scaling.
> Vaibhav, if this is okay for you, please ack it.
>
> Then, in terms of merging, probably Kevin would be the right person for
> this since he's done much of the voltagedomain work.
Yeah, I'll take this series after the minor issues I commented on are
fixed, and Vaivhav ack's the AM33xx parts.
Kevin
next prev parent reply other threads:[~2013-06-14 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 10:08 [PATCH 0/2] Remove unused voltagedomain data for AM33xx Rajendra Nayak
2013-06-13 10:08 ` Rajendra Nayak
2013-06-13 10:08 ` [PATCH 1/2] ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm associated to a pwrdm Rajendra Nayak
2013-06-13 10:08 ` Rajendra Nayak
2013-06-14 13:59 ` Kevin Hilman
2013-06-14 13:59 ` Kevin Hilman
2013-06-13 10:08 ` [PATCH 2/2] ARM: AM33xx: Remove the unused voltagedomain data Rajendra Nayak
2013-06-13 10:08 ` Rajendra Nayak
2013-06-14 2:46 ` [PATCH 0/2] Remove unused voltagedomain data for AM33xx Paul Walmsley
2013-06-14 2:46 ` Paul Walmsley
2013-06-14 13:14 ` Nishanth Menon
2013-06-14 13:14 ` Nishanth Menon
2013-06-14 14:01 ` Kevin Hilman [this message]
2013-06-14 14:01 ` Kevin Hilman
2013-06-17 5:08 ` Hiremath, Vaibhav
2013-06-17 5:08 ` Hiremath, Vaibhav
2013-06-17 5:12 ` Rajendra Nayak
2013-06-17 5:12 ` Rajendra Nayak
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=8738skaj16.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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.