From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/2] cpufreq: OMAP: Handle missing frequency table on SMP systems
Date: Thu, 09 Aug 2012 14:25:39 -0700 [thread overview]
Message-ID: <874nobhi5o.fsf@ti.com> (raw)
In-Reply-To: <201208092132.25141.rjw@sisk.pl> (Rafael J. Wysocki's message of "Thu, 9 Aug 2012 21:32:24 +0200")
"Rafael J. Wysocki" <rjw@sisk•pl> writes:
> On Thursday, August 09, 2012, Kevin Hilman wrote:
>> "Rafael J. Wysocki" <rjw@sisk•pl> writes:
>>
>> > On Thursday, August 09, 2012, Rajendra Nayak wrote:
>> >> On OMAP4, if the first CPU fails to get a valid frequency table (this
>> >> could happen if the platform does not register any OPP table), the
>> >> subsequent CPU instances end up dealing with a NULL freq_table and
>> >> crash.
>> >>
>> >> Check for an already existing freq_table, before trying to create one,
>> >> and increment the freq_table_users only if the table is sucessfully
>> >> created.
>> >>
>> >> Signed-off-by: Rajendra Nayak <rnayak@ti•com>
>> >> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti•com>
>> >> Cc: <linux-pm@vger•kernel.org>
>> >
>> > Kevin, are you going to merge this?
>> >
>>
>> Yes, I plan to queue this with 2/2 for v3.6-rc.
>
> If you have any cpufreq patches for v3.7, can you please tell me where to
> pull them from (and when)?
Yes, I will.
Thanks,
Kevin
next prev parent reply other threads:[~2012-08-09 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 7:08 [PATCH v2 0/2] OMAP cpufreq fixes Rajendra Nayak
2012-08-09 7:08 ` [PATCH v2 1/2] cpufreq: OMAP: Handle missing frequency table on SMP systems Rajendra Nayak
2012-08-09 9:32 ` Rafael J. Wysocki
2012-08-09 15:00 ` Kevin Hilman
2012-08-09 19:32 ` Rafael J. Wysocki
2012-08-09 21:25 ` Kevin Hilman [this message]
2012-08-09 7:08 ` [PATCH v2 2/2] ARM: OMAP4: Register the OPP table only for 4430 device Rajendra Nayak
2012-08-09 7:23 ` Shilimkar, Santosh
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=874nobhi5o.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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