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] More fixes for omaps for v5.12-rc cycle
Date: Wed, 24 Mar 2021 13:20:39 +0200 [thread overview]
Message-ID: <pull-1616584662-702939@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.12/fixes-rc4-signed
for you to fetch changes up to b3d09a06d89f474cb52664e016849315a97e09d9:
ARM: OMAP4: PM: update ROM return address for OSWR and OFF (2021-03-17 15:15:52 +0200)
----------------------------------------------------------------
More fixes for omaps for v5.12-rc cycle
Two fixes for hangs, mmc slot order fix, and a voltage typo fix:
- Remove unused duplicate sha2md5_fck clock node that can race with the
OMAP4_SHA2MD5_CLKCTRL clock node for disable for unused clocks
- Add aliases for omap4/5 mmc to put the slots back into the right
order again
- Fix typo for bionic voltage controllers that accidentally use mpu
for all instances instead of mpu, core and iva
- Fix random hangs for droid4 caused by missing fix from TI Android
kernel tree to do a dummy smc call on cpuidle wakeup path
----------------------------------------------------------------
Note that the stats below also include my earlier pull request as the pull
request is generated against v5.12-rc2.
Carlos Leija (1):
ARM: OMAP4: PM: update ROM return address for OSWR and OFF
Grygorii Strashko (1):
bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD
Mans Rullgard (1):
ARM: dts: am33xx: add aliases for mmc interfaces
Tony Lindgren (9):
soc: ti: omap-prm: Fix reboot issue with invalid pcie reset map for dra7
ARM: OMAP2+: Fix smartreflex init regression after dropping legacy data
Merge branch 'fixes-v5.11' into fixes
bus: ti-sysc: Fix warning on unbind if reset is not deasserted
soc: ti: omap-prm: Fix occasional abort on reset deassert for dra7 iva
ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
Merge branch 'fixes-rc2' into fixes
ARM: OMAP4: Fix PMIC voltage domains for bionic
arch/arm/boot/dts/am33xx.dtsi | 3 ++
arch/arm/boot/dts/omap4.dtsi | 5 +++
arch/arm/boot/dts/omap44xx-clocks.dtsi | 8 ----
arch/arm/boot/dts/omap5.dtsi | 5 +++
arch/arm/mach-omap2/omap-secure.c | 39 ++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 1 +
arch/arm/mach-omap2/pmic-cpcap.c | 4 +-
arch/arm/mach-omap2/sr_device.c | 75 ++++++++++++++++++++++++++--------
drivers/bus/omap_l3_noc.c | 4 +-
drivers/bus/ti-sysc.c | 4 +-
drivers/soc/ti/omap_prm.c | 8 +++-
11 files changed, 124 insertions(+), 32 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-24 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 11:20 Tony Lindgren [this message]
2021-04-01 10:23 ` [GIT PULL] More fixes for omaps for v5.12-rc cycle Arnd Bergmann
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-1616584662-702939@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).