From: Nishanth Menon <menon.nishanth@gmail.com>
To: "Benoît Cousson" <b-cousson@ti.com>, "Tony Lindgren" <tony@atomide.com>
Cc: Nishanth Menon <nm@ti.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: dts: OMAP36xx/OMAP4460 Fix CPU OPP voltages
Date: Sun, 05 May 2013 10:04:52 -0500 [thread overview]
Message-ID: <51867514.9030803@gmail.com> (raw)
In-Reply-To: <1366997973-19120-1-git-send-email-nm@ti.com>
Tony/Benoit,
gentle offline ping for this series?
https://patchwork.kernel.org/patch/2494481/
https://patchwork.kernel.org/patch/2494491/
Regards,
Nishanth Menon
On 04/26/2013 12:39 PM, Nishanth Menon wrote:
> Hi,
> It seems that I have not been paying close attention to
> actual voltage value seen on scope to map it back to verify the validity
> of the voltage value. Even though I did verify[1] that voltage did scale to
> values in DT entries, the values in the case of 3630 and 4460 were lower than
> what the spec voltage was as per opp_data files.
>
> This series is based off Benoit's tree here:
> http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
>
> Commit ID's in the patches to indicate regressions are from there as well.
> Would be good to have this fix merged to 3.10 dts entries.
> I have cross verified that OMAP3430,3630,4430 and 4460 entries now match that
> of corresponding opp*_data.c
>
> My sincere apologies on the oversight.
>
> Nishanth Menon (2):
> ARM: dts: OMAP36xx: Fix CPU OPP voltages
> ARM: dts: OMAP4460: Fix CPU OPP voltages
>
> arch/arm/boot/dts/omap36xx.dtsi | 6 +++---
> arch/arm/boot/dts/omap4460.dtsi | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> [1] http://marc.info/?l=linux-arm-kernel&m=136580742724210&w=2
> Regards,
> Nishanth Menon
>
next prev parent reply other threads:[~2013-05-05 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:39 [PATCH 0/2] ARM: dts: OMAP36xx/OMAP4460 Fix CPU OPP voltages Nishanth Menon
2013-04-26 17:39 ` [PATCH 1/2] ARM: dts: OMAP36xx: " Nishanth Menon
2013-04-26 17:39 ` [PATCH 2/2] ARM: dts: OMAP4460: " Nishanth Menon
2013-05-05 15:04 ` Nishanth Menon [this message]
2013-05-08 23:14 ` [PATCH 0/2] ARM: dts: OMAP36xx/OMAP4460 " Tony Lindgren
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=51867514.9030803@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.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 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).