From: Kevin Hilman <khilman@linaro.org>
To: Rajendra Nayak <rnayak@ti.com>
Cc: paul@pwsan.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Remove unused voltagedomain data for AM33xx
Date: Mon, 17 Jun 2013 07:32:49 -0700 [thread overview]
Message-ID: <87wqps959q.fsf@linaro.org> (raw)
In-Reply-To: <1371474983-29296-1-git-send-email-rnayak@ti.com> (Rajendra Nayak's message of "Mon, 17 Jun 2013 18:46:21 +0530")
Rajendra Nayak <rnayak@ti.com> writes:
> Hi,
>
> The powerdomain framework currently 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. All these SoCs', hence do not support any
> form of auto-scaling of voltages, that was possible on earlier OMAPs'
> using the VFSM to trigger an i2c communication to the PMIC automatically
> on hitting a low power state.
>
> Instead of adding dummy voltage domain data files, like was done for the
> AM33xx case, make the powerdomain framework aware of the fact that some
> SoCs' might not really have support for auto-scaling of voltages in hw.
>
> Patches are based of 3.10-rc6 and are boot tested on am335x bone.
>
> Rajendra Nayak (2):
> ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm
> associated to a pwrdm
> ARM: AM33xx: Remove the unused voltagedomain data
Thanks, queuing up this series with ack from Santosh and tested-by from
Afzal. I'll try, but not sure if it can make it for v3.11.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Remove unused voltagedomain data for AM33xx
Date: Mon, 17 Jun 2013 07:32:49 -0700 [thread overview]
Message-ID: <87wqps959q.fsf@linaro.org> (raw)
In-Reply-To: <1371474983-29296-1-git-send-email-rnayak@ti.com> (Rajendra Nayak's message of "Mon, 17 Jun 2013 18:46:21 +0530")
Rajendra Nayak <rnayak@ti.com> writes:
> Hi,
>
> The powerdomain framework currently 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. All these SoCs', hence do not support any
> form of auto-scaling of voltages, that was possible on earlier OMAPs'
> using the VFSM to trigger an i2c communication to the PMIC automatically
> on hitting a low power state.
>
> Instead of adding dummy voltage domain data files, like was done for the
> AM33xx case, make the powerdomain framework aware of the fact that some
> SoCs' might not really have support for auto-scaling of voltages in hw.
>
> Patches are based of 3.10-rc6 and are boot tested on am335x bone.
>
> Rajendra Nayak (2):
> ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm
> associated to a pwrdm
> ARM: AM33xx: Remove the unused voltagedomain data
Thanks, queuing up this series with ack from Santosh and tested-by from
Afzal. I'll try, but not sure if it can make it for v3.11.
Kevin
next prev parent reply other threads:[~2013-06-17 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 13:16 [PATCH v2 0/2] Remove unused voltagedomain data for AM33xx Rajendra Nayak
2013-06-17 13:16 ` Rajendra Nayak
2013-06-17 13:16 ` [PATCH v2 1/2] ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm associated to a pwrdm Rajendra Nayak
2013-06-17 13:16 ` Rajendra Nayak
2013-06-17 13:16 ` [PATCH v2 2/2] ARM: AM33xx: Remove the unused voltagedomain data Rajendra Nayak
2013-06-17 13:16 ` Rajendra Nayak
2013-06-17 13:22 ` [PATCH v2 0/2] Remove unused voltagedomain data for AM33xx Santosh Shilimkar
2013-06-17 13:22 ` Santosh Shilimkar
2013-06-17 13:43 ` Mohammed, Afzal
2013-06-17 13:43 ` Mohammed, Afzal
2013-06-17 14:32 ` Kevin Hilman [this message]
2013-06-17 14:32 ` 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=87wqps959q.fsf@linaro.org \
--to=khilman@linaro.org \
--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.