From: Vaibhav Hiremath <hvaibhav@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>, Afzal Mohammed <afzal@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>, Benoit Cousson <b-cousson@ti.com>,
Rajendra Nayak <rnayak@ti.com>
Subject: Re: [PATCH 2/6] ARM: OMAP AM33xx: voltagedomain: Add voltage domain data
Date: Mon, 11 Jun 2012 14:49:58 +0530 [thread overview]
Message-ID: <4FD5B83E.6020807@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206101916480.20674@utopia.booyaka.com>
On 6/11/2012 6:50 AM, Paul Walmsley wrote:
> Hi Vaibhav, Afzal, Tony,
>
> On Mon, 21 May 2012, Paul Walmsley wrote:
>
>> From: Vaibhav Hiremath <hvaibhav@ti.com>
>>
>> Currently dummy voltage domain data is being created
>> in order to succeed boot process, nothing has been done
>> w.r.t actual hardware (voltage control).
>>
>> Also, hook up the AM33XX voltage domain to OMAP framework.
>
> I had to update this patch again for v3.5 to account for the lack of
> am33xx_init_early(). So now this patch has to add it (updated patch
> below).
>
Paul,
I think this is not required, since Tony has already accepted the patch
which has this implementation (available on linux-omap/master).
Please refer to the commit,
commit 08f3098928c991560408e8c71d4af8b1a3ff2d67
Author: Afzal Mohammed <afzal@ti.com>
Date: Fri May 11 00:38:49 2012 +0530
ARM: OMAP2+: am33xx: Add AM335XEVM machine support
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
From: hvaibhav@ti.com (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] ARM: OMAP AM33xx: voltagedomain: Add voltage domain data
Date: Mon, 11 Jun 2012 14:49:58 +0530 [thread overview]
Message-ID: <4FD5B83E.6020807@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206101916480.20674@utopia.booyaka.com>
On 6/11/2012 6:50 AM, Paul Walmsley wrote:
> Hi Vaibhav, Afzal, Tony,
>
> On Mon, 21 May 2012, Paul Walmsley wrote:
>
>> From: Vaibhav Hiremath <hvaibhav@ti.com>
>>
>> Currently dummy voltage domain data is being created
>> in order to succeed boot process, nothing has been done
>> w.r.t actual hardware (voltage control).
>>
>> Also, hook up the AM33XX voltage domain to OMAP framework.
>
> I had to update this patch again for v3.5 to account for the lack of
> am33xx_init_early(). So now this patch has to add it (updated patch
> below).
>
Paul,
I think this is not required, since Tony has already accepted the patch
which has this implementation (available on linux-omap/master).
Please refer to the commit,
commit 08f3098928c991560408e8c71d4af8b1a3ff2d67
Author: Afzal Mohammed <afzal@ti.com>
Date: Fri May 11 00:38:49 2012 +0530
ARM: OMAP2+: am33xx: Add AM335XEVM machine support
Thanks,
Vaibhav
next prev parent reply other threads:[~2012-06-11 9:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 18:41 [PATCH 0/6] ARM: OMAP AM33xx: PRM/CM support for 3.6 Paul Walmsley
2012-05-21 18:41 ` Paul Walmsley
2012-05-21 18:41 ` [PATCH 1/6] ARM: OMAP2+: control: Add AM33XX control reg & sec clkctrl offset Paul Walmsley
2012-05-21 18:41 ` Paul Walmsley
2012-05-21 18:41 ` [PATCH 2/6] ARM: OMAP AM33xx: voltagedomain: Add voltage domain data Paul Walmsley
2012-05-21 18:41 ` Paul Walmsley
2012-06-11 1:20 ` Paul Walmsley
2012-06-11 1:20 ` Paul Walmsley
2012-06-11 9:19 ` Vaibhav Hiremath [this message]
2012-06-11 9:19 ` Vaibhav Hiremath
2012-06-11 16:10 ` Paul Walmsley
2012-06-11 16:10 ` Paul Walmsley
2012-06-11 17:16 ` Vaibhav Hiremath
2012-06-11 17:16 ` Vaibhav Hiremath
2012-05-21 18:41 ` [PATCH 3/6] ARM: OMAP AM33xx: PRM: add PRM support Paul Walmsley
2012-05-21 18:41 ` Paul Walmsley
2012-05-21 18:42 ` [PATCH 4/6] ARM: OMAP AM33xx: CM: Introduce AM33xx CM APIs and register level details Paul Walmsley
2012-05-21 18:42 ` Paul Walmsley
2012-05-21 18:42 ` [PATCH 5/6] ARM: OMAP AM33xx: powerdomains: add AM335x support Paul Walmsley
2012-05-21 18:42 ` Paul Walmsley
2012-05-21 18:42 ` [PATCH 6/6] ARM: OMAP AM33xx: clockdomains: Add clockdomain data and respective operations Paul Walmsley
2012-05-21 18:42 ` Paul Walmsley
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=4FD5B83E.6020807@ti.com \
--to=hvaibhav@ti.com \
--cc=afzal@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@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.