From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, Arnd Bergmann <arnd@arndb.de>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
Date: Wed, 26 Jun 2013 00:30:57 -0700 [thread overview]
Message-ID: <20130626073056.GS5523@atomide.com> (raw)
In-Reply-To: <87sj05sp0p.fsf@linaro.org>
* Kevin Hilman <khilman@linaro.org> [130625 17:24]:
> Nishanth Menon <nm@ti.com> writes:
>
> > commit 20d49e9ccfece526db755940721aa13e331936d4
> > (ARM: OMAP5: voltagedomain data: Add OMAP5 voltage domain data)
> >
> > Introduced dummy volt data for OMAP5 with OMAP4460 voltage information.
> >
> > However with the fixes introduced in later patches
> >
> > commit cd8abed1da91a3250aa4b3857479613a2b446f84
> > (ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm
> > associated to a pwrdm)
> >
> > We are no longer restricted in that respect. Further, OPP voltage
> > information is supposed to be provided by dts information. This needs
> > to be added in future patches as various voltage modules are converted
> > to dts.
> >
> > This also fixes the build breakage for voltagedomains54xx_data.c when just
> > OMAP5 SoC is enabled: https://patchwork.kernel.org/patch/2764191/
> >
> > Reported-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> > Cc: Kevin Hilman <khilman@deeprootsystems.com>
> > Cc: Benoit Cousson <b-cousson@ti.com>
> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > Cc: Paul Walmsley <paul@pwsan.com>
> > Cc: Tony Lindgren <tony@atomide.com>
> > Cc: linux-omap@vger.kernel.org
>
> Acked-by: Kevin Hilman <khilman@linaro.org>
>
> Arnd, to make it easy, below is a pull request for this fix on top of
> arm-soc/omap/omap5.
This can get easily lost, might be best to send a new email with
[GIT PULL] in the subject.
Regards,
Tony
> The following changes since commit 6503a8e109a639760408f874c1251060d563942e:
>
> ARM: OMAP5: Remove unused include for ocp2scp (2013-06-09 21:17:15 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git tags/omap-pm-v3.11/fixes/omap5-voltdm
>
> for you to fetch changes up to 2ac524f151dbecb862c95b8f433267772caa800e:
>
> ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data (2013-06-25 17:11:06 -0700)
>
> ----------------------------------------------------------------
> OMAP5: PM: fix boot by removing unneeded dummy voltage domain data
>
> ----------------------------------------------------------------
> Nishanth Menon (1):
> ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
>
> arch/arm/mach-omap2/voltagedomains54xx_data.c | 10 ----------
> 1 file changed, 10 deletions(-)
next prev parent reply other threads:[~2013-06-26 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 23:56 [PATCH] ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data Nishanth Menon
2013-06-25 23:58 ` Santosh Shilimkar
2013-06-26 0:18 ` Kevin Hilman
2013-06-26 7:30 ` Tony Lindgren [this message]
2013-06-26 14:52 ` Arnd Bergmann
2013-06-26 15:10 ` 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=20130626073056.GS5523@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=khilman@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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 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).