From: Kevin Hilman <khilman@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: OMAP4: Register the OPP table only for 4430 device
Date: Thu, 09 Aug 2012 08:01:13 -0700 [thread overview]
Message-ID: <878vdogldy.fsf@ti.com> (raw)
In-Reply-To: <50236570.6030301@ti.com> (Rajendra Nayak's message of "Thu, 09 Aug 2012 12:53:28 +0530")
Rajendra Nayak <rnayak@ti.com> writes:
> Hi Kevin,
>
> On Wednesday 08 August 2012 10:48 PM, Kevin Hilman wrote:
>>> The 4430 OPP table was being registered for all other OMAP4 variants
>>> > too, like 4460 and 4470 causing issues with cpufreq driver
>>> > enabled. 4460 and 4470 devices have different OPPs as compared to
>>> > 4430, and they should be populated seperately. As long as that
>>> > happens, let the OPP table registeration happen only on 4430 device.
>>> >
>>> > Signed-off-by: Rajendra Nayak<rnayak@ti.com>
>> Thanks, adding to PM fixes for v3.6-rc (branch: for_3.6/fixes/pm)
>
> I just posted a v2 of this series addressing the issues raised by
> Santosh on Patch 1/2. The problem with taking just $subject fix (or
> taking it before Patch 1/2) is that you would hit the issue fixed
> by the Patch 1/2 and cause a crash on non-4430 based OMAP4 devices with
> cpufreq enabled.
OK, thanks for the warning. I'll be sure to keep them together.
Kevin
prev parent reply other threads:[~2012-08-09 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 10:54 [PATCH 0/2] OMAP cpufreq fixes Rajendra Nayak
2012-08-08 10:54 ` [PATCH 1/2] cpufreq: OMAP: Handle missing frequency table on SMP systems Rajendra Nayak
2012-08-08 11:30 ` Shilimkar, Santosh
2012-08-08 17:28 ` Kevin Hilman
2012-08-09 5:27 ` Shilimkar, Santosh
2012-08-08 10:54 ` [PATCH 2/2] ARM: OMAP4: Register the OPP table only for 4430 device Rajendra Nayak
2012-08-08 17:18 ` Kevin Hilman
2012-08-09 7:23 ` Rajendra Nayak
2012-08-09 15:01 ` Kevin Hilman [this message]
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=878vdogldy.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 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).