From: Olof Johansson <olof@lixom.net>
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 for v4.7-rc cycle
Date: Sat, 18 Jun 2016 22:58:48 -0700 [thread overview]
Message-ID: <20160619055848.GA16376@localhost> (raw)
In-Reply-To: <20160614081101.GV22406@atomide.com>
On Tue, Jun 14, 2016 at 01:11:02AM -0700, Tony Lindgren wrote:
> The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:
>
> Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.7/fixes-powedomain
>
> for you to fetch changes up to 6b41d44862e8f3a4b95102c6ff6cad3fccc7994b:
>
> ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret (2016-06-13 01:04:01 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps for v4.7-rc cycle:
>
> - Fix dra7 for hardware issues limiting L4Per and L3init power domains
> to on state. Without this the devices may not work correctly after
> some time of use because of asymmetric aging. And related to this,
> let's also remove the unusable states.
>
> - Always select omap interconnect for am43x as otherwise the am43x
> only configurations will not boot properly. This can happen easily
> for any product kernels that leave out other SoCs to save memory.
>
> - Fix DSS PLL2 addresses that have gone unused for now
>
> - Select erratum 430973 for omap3, this is now safe to do and can
> save quite a bit of debugging time for people who may have left
> it out.
Grmbl, our fixes branch was only at -rc1, but I merged this anyway.
-Olof
prev parent reply other threads:[~2016-06-19 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 8:11 [GIT PULL] omap fixes for v4.7-rc cycle Tony Lindgren
2016-06-19 5:58 ` Olof Johansson [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=20160619055848.GA16376@localhost \
--to=olof@lixom.net \
--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 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).