All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] omap fixes against v4.6-rc2
Date: Fri, 22 Apr 2016 08:38:37 -0700	[thread overview]
Message-ID: <7hinz94ps2.fsf@baylibre.com> (raw)
In-Reply-To: <20160419195147.GE5973@atomide.com> (Tony Lindgren's message of "Tue, 19 Apr 2016 12:51:47 -0700")

Tony Lindgren <tony@atomide.com> writes:

> * Tony Lindgren <tony@atomide.com> [160419 07:55]:
>> * Tony Lindgren <tony@atomide.com> [160408 12:22]:
>> >       ARM: OMAP: Catch callers of revision information prior to it being populated
>> 
>> And this one causes bogus runtime warnings with other SoCs
>> as reported by Guenter Roeck. I'll revert this and post
>> an updated pull request shortly.
>
> And below is the updated pull request with just the above
> commit reverted.
>
> Regards,
>
> Tony
>
> 8< -------------------
> The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9:
>
>   Linux 4.6-rc2 (2016-04-03 09:09:40 -0500)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.6/fixes-rc2-v2-signed
>
> for you to fetch changes up to 3d51ae172d759198b2e47e104c31a92d20d17927:
>
>   Revert "ARM: OMAP: Catch callers of revision information prior to it being populated" (2016-04-19 08:01:05 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps against v4.6-rc2, mostly to fix suspend for beagle-x15
> that broke when we added runtime based SoC revision detection earlier.
>
> It seems suspend worked earlier as things were only partially initialized,
> while now we initialize things properly for dra7.
>
> Note that the "ARM: OMAP: Catch callers of revision information prior
> to it being populated" had to be reverted as it caused bogus warnings
> for other SoCs because omap initcalls bail out based on revision being
> set to 0 for other SoCs. These initcalls will mostly just disappear
> when we drop support for omap3 legacy booting.
>
> Also included is a fix for dra7 sys_32k_ck clock source that is not
> enabled on boot making system fall back to using emulated clock.
>
> ----------------------------------------------------------------

Applied to fixes,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes against v4.6-rc2
Date: Fri, 22 Apr 2016 08:38:37 -0700	[thread overview]
Message-ID: <7hinz94ps2.fsf@baylibre.com> (raw)
In-Reply-To: <20160419195147.GE5973@atomide.com> (Tony Lindgren's message of "Tue, 19 Apr 2016 12:51:47 -0700")

Tony Lindgren <tony@atomide.com> writes:

> * Tony Lindgren <tony@atomide.com> [160419 07:55]:
>> * Tony Lindgren <tony@atomide.com> [160408 12:22]:
>> >       ARM: OMAP: Catch callers of revision information prior to it being populated
>> 
>> And this one causes bogus runtime warnings with other SoCs
>> as reported by Guenter Roeck. I'll revert this and post
>> an updated pull request shortly.
>
> And below is the updated pull request with just the above
> commit reverted.
>
> Regards,
>
> Tony
>
> 8< -------------------
> The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9:
>
>   Linux 4.6-rc2 (2016-04-03 09:09:40 -0500)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.6/fixes-rc2-v2-signed
>
> for you to fetch changes up to 3d51ae172d759198b2e47e104c31a92d20d17927:
>
>   Revert "ARM: OMAP: Catch callers of revision information prior to it being populated" (2016-04-19 08:01:05 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps against v4.6-rc2, mostly to fix suspend for beagle-x15
> that broke when we added runtime based SoC revision detection earlier.
>
> It seems suspend worked earlier as things were only partially initialized,
> while now we initialize things properly for dra7.
>
> Note that the "ARM: OMAP: Catch callers of revision information prior
> to it being populated" had to be reverted as it caused bogus warnings
> for other SoCs because omap initcalls bail out based on revision being
> set to 0 for other SoCs. These initcalls will mostly just disappear
> when we drop support for omap3 legacy booting.
>
> Also included is a fix for dra7 sys_32k_ck clock source that is not
> enabled on boot making system fall back to using emulated clock.
>
> ----------------------------------------------------------------

Applied to fixes,

Kevin

  reply	other threads:[~2016-04-22 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 19:18 [GIT PULL] omap fixes against v4.6-rc2 Tony Lindgren
2016-04-08 19:18 ` Tony Lindgren
2016-04-19 14:54 ` Tony Lindgren
2016-04-19 14:54   ` Tony Lindgren
2016-04-19 19:51   ` Tony Lindgren
2016-04-19 19:51     ` Tony Lindgren
2016-04-22 15:38     ` Kevin Hilman [this message]
2016-04-22 15:38       ` 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=7hinz94ps2.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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 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.