From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Felipe Balbi <balbi@ti.com>, Venkatraman S <svenkatr@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP baseline test results for v3.7-rc4
Date: Tue, 13 Nov 2012 10:50:30 -0800 [thread overview]
Message-ID: <87r4nxgww9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211092347520.20703@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 9 Nov 2012 23:49:14 +0000 (UTC)")
Paul Walmsley <paul@pwsan.com> writes:
> On Fri, 9 Nov 2012, Kevin Hilman wrote:
>
>> I found that disabling MMC in the config made the tests pass again, so
>> then bisected it down to the commit below removing SYSCONFIG
>> accesses[2]. I haven't had the time to find out exactly the cause, but
>> clearly the code that was removed was doing something that hwmod is not
>> taking care of automatically.
>>
>> Venkat, Felipe, could you please investigate this and hopefully get a
>> fix out for v3.7-rc?
>
> This one might fix it -- it fixes another PM bug in the v3.7-rcs involving
> the same commit:
>
> http://git.kernel.org/?p=linux/kernel/git/pjw/omap-pending.git;a=commit;h=613ad0e98c3596cd2524172fae2a795c3fc57e4a
>
Indeed, that fixes it. Somehow I thought I was already including that
fix, but I wasn't.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc4
Date: Tue, 13 Nov 2012 10:50:30 -0800 [thread overview]
Message-ID: <87r4nxgww9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211092347520.20703@utopia.booyaka.com> (Paul Walmsley's message of "Fri, 9 Nov 2012 23:49:14 +0000 (UTC)")
Paul Walmsley <paul@pwsan.com> writes:
> On Fri, 9 Nov 2012, Kevin Hilman wrote:
>
>> I found that disabling MMC in the config made the tests pass again, so
>> then bisected it down to the commit below removing SYSCONFIG
>> accesses[2]. I haven't had the time to find out exactly the cause, but
>> clearly the code that was removed was doing something that hwmod is not
>> taking care of automatically.
>>
>> Venkat, Felipe, could you please investigate this and hopefully get a
>> fix out for v3.7-rc?
>
> This one might fix it -- it fixes another PM bug in the v3.7-rcs involving
> the same commit:
>
> http://git.kernel.org/?p=linux/kernel/git/pjw/omap-pending.git;a=commit;h=613ad0e98c3596cd2524172fae2a795c3fc57e4a
>
Indeed, that fixes it. Somehow I thought I was already including that
fix, but I wasn't.
Thanks,
Kevin
next prev parent reply other threads:[~2012-11-13 18:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 2:46 OMAP baseline test results for v3.7-rc4 Paul Walmsley
2012-11-05 2:46 ` Paul Walmsley
2012-11-07 17:14 ` Jon Hunter
2012-11-07 17:14 ` Jon Hunter
2012-11-07 17:32 ` Paul Walmsley
2012-11-07 17:32 ` Paul Walmsley
2012-11-07 18:07 ` Jon Hunter
2012-11-07 18:07 ` Jon Hunter
2012-11-07 20:56 ` Jon Hunter
2012-11-07 20:56 ` Jon Hunter
2012-11-09 23:23 ` Kevin Hilman
2012-11-09 23:23 ` Kevin Hilman
2012-11-09 23:49 ` Paul Walmsley
2012-11-09 23:49 ` Paul Walmsley
2012-11-13 18:50 ` Kevin Hilman [this message]
2012-11-13 18:50 ` 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=87r4nxgww9.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=svenkatr@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 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.