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] Few regression fixes for omaps
Date: Fri, 11 Dec 2020 10:22:54 +0200 [thread overview]
Message-ID: <pull-1607674932-973902@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 05d5de6ba7dbe490dd413b5ca11d0875bd2bc006:
ARM: dts: dra76x: m_can: fix order of clocks (2020-11-19 11:37:57 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.10/fixes-rc6-signed
for you to fetch changes up to c0bc969c176b10598b31d5d1a5edf9a5261f0a9f:
ARM: omap2: pmic-cpcap: fix maximum voltage to be consistent with defaults on xt875 (2020-12-08 15:56:24 +0200)
----------------------------------------------------------------
Few regression fixes for omaps for v5.10
Few fixes for regression issues recently noticed by folks testing
the current kernel:
- We need to disable AES for n950 as it's not accessible because of the
secure mode configuration and kernel fails to boot
- On gta04 wlan probe exposed a bug for BUS_NOTIFY_BIND_DRIVER that has
been around for a long time
- Droid bionic exposed an issue where we configure an invalid range on
the PMIC that adds boot time warnings
Obviously these fixes can be merged whenever suitable.
----------------------------------------------------------------
Aaro Koskinen (1):
ARM: dts: OMAP3: disable AES on N950/N9
Andreas Kemnade (1):
ARM: OMAP2+: omap_device: fix idling of devices during probe
Carl Philipp Klemm (1):
ARM: omap2: pmic-cpcap: fix maximum voltage to be consistent with defaults on xt875
arch/arm/boot/dts/omap3-n950-n9.dtsi | 8 ++++++++
arch/arm/mach-omap2/omap_device.c | 8 +++++---
arch/arm/mach-omap2/pmic-cpcap.c | 2 +-
3 files changed, 14 insertions(+), 4 deletions(-)
reply other threads:[~2020-12-11 8: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-1607674932-973902@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).