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] Fix for omaps for v5.15-rc cycle
Date: Thu, 7 Oct 2021 15:26:31 +0300 [thread overview]
Message-ID: <pull-1633609552-789682@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.15/fixes-rc4
for you to fetch changes up to 80d680fdccba214e8106dc1aa33de5207ad75394:
ARM: dts: omap3430-sdp: Fix NAND device node (2021-10-06 08:05:08 +0300)
----------------------------------------------------------------
Fixes for omaps for v5.15
Few regression fixes for omaps for the v5.15-rc cycle. There is a fix
for boot time hangs that can happen on some am335x devices that started
when the pruss devicetree nodes were added. The other fixes are less
critical:
- Fix compiler warning for sysc_init_soc() that got recently introduced
- Fix external abort for am335x pruss as otherwise some am335x will hang
- Use CLKDM_NOAUTO quirk also for dra7 dcan1
- Fix older NAND device node regression for omap3-sdp
----------------------------------------------------------------
Nathan Chancellor (1):
bus: ti-sysc: Add break in switch statement in sysc_init_soc()
Roger Quadros (1):
ARM: dts: omap3430-sdp: Fix NAND device node
Tony Lindgren (3):
soc: ti: omap-prm: Fix external abort for am335x pruss
Merge branch 'pruss-fix' into fixes
bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893
arch/arm/boot/dts/omap3430-sdp.dts | 2 +-
arch/arm/mach-omap2/omap_hwmod.c | 2 ++
drivers/bus/ti-sysc.c | 4 ++++
drivers/soc/ti/omap_prm.c | 27 +++++++++++++++------------
4 files changed, 22 insertions(+), 13 deletions(-)
reply other threads:[~2021-10-07 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1633609552-789682@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