From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Two omap regression fixes
Date: Thu, 1 Oct 2020 12:30:44 +0300 [thread overview]
Message-ID: <pull-1601544624-617679@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 6542e2b613c2b1952e83973dc434831332ce8e27:
ARM: dts: omap5: Fix DSI base address and clocks (2020-08-19 08:54:33 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.9/fixes-rc7
for you to fetch changes up to 8f04aea048d56f3e39a7e543939450246542a6fc:
ARM: OMAP2+: Restore MPU power domain if cpu_cluster_pm_enter() fails (2020-09-23 10:39:33 +0300)
----------------------------------------------------------------
Two regression fixes for omaps
Fix AM33XX_IOPAD macro that broke after recent pinctrl changes
to use #pinctrl-cells = 2. And fix omap_enter_idle_coupled()
for cases where cpu_cluster_pm_enter() returns an error as
otherwise we may end up wrongly idling the MPU domain on the
next WFI.
----------------------------------------------------------------
Drew Fustini (1):
ARM: dts: am33xx: modify AM33XX_IOPAD for #pinctrl-cells = 2
Tony Lindgren (1):
ARM: OMAP2+: Restore MPU power domain if cpu_cluster_pm_enter() fails
arch/arm/mach-omap2/cpuidle44xx.c | 4 +++-
include/dt-bindings/pinctrl/omap.h | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2020-10-01 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:30 Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-02 19:55 [GIT PULL] two omap regression fixes Tony Lindgren
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=pull-1601544624-617679@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.org \
/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).