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 2/3] Driver changes for ti-sysc for v5.16
Date: Mon, 11 Oct 2021 14:02:43 +0300 [thread overview]
Message-ID: <pull-1633950030-501948@atomide.com-2> (raw)
In-Reply-To: <pull-1633950030-501948@atomide.com>
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.16/ti-sysc-signed
for you to fetch changes up to 1b1da99b845337362a3dafe0f7b49927ab4ae041:
bus: ti-sysc: Fix variable set but not used warning for reinit_modules (2021-10-06 08:38:09 +0300)
----------------------------------------------------------------
Driver changes for ti-sysc for v5.16
Changes for ti-sysc driver for improved system suspend and resume
support as some drivers need to be reinitialized on resume. Also
a non-urgent resume warning fix, and dropping of legacy flags for
gpio and sham:
- Fix timekeeping suspended warning on resume. Probably no need to merge
this into fixes as it's gone unnoticed for a while.
- Check for context loss for reinit of a module
- Add add quirk handling to reinit on context loss, and also fix a
build warning it caused
- Add quirk handling to reset on reinit
- Use context loss quirk for gpmc and otg
- Handle otg force-idle quirk even if no driver is loaded
- Drop legacy flags for gpio and sham
----------------------------------------------------------------
Tony Lindgren (10):
bus: ti-sysc: Fix timekeeping_suspended warning on resume
bus: ti-sysc: Check for lost context in sysc_reinit_module()
bus: ti-sysc: Add quirk handling for reinit on context lost
bus: ti-sysc: Add quirk handling for reset on re-init
bus: ti-sysc: Use context lost quirks for gpmc
bus: ti-sysc: Use context lost quirk for otg
bus: ti-sysc: Handle otg force idle quirk
bus: ti-sysc: Drop legacy quirk flag for gpio
bus: ti-sysc: Drop legacy quirk flag for sham
bus: ti-sysc: Fix variable set but not used warning for reinit_modules
drivers/bus/ti-sysc.c | 276 +++++++++++++++++++++++++++++-----
include/linux/platform_data/ti-sysc.h | 3 +
2 files changed, 244 insertions(+), 35 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-11 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 11:02 [GIT PULL 1/3] SoC changes for omaps for v5.16 Tony Lindgren
2021-10-11 11:02 ` Tony Lindgren [this message]
2021-10-11 15:02 ` [GIT PULL 2/3] Driver changes for ti-sysc " Arnd Bergmann
2021-10-11 11:02 ` [GIT PULL 3/3] Devicetree changes for omaps " Tony Lindgren
2021-10-11 22:11 ` Arnd Bergmann
2021-10-12 12:50 ` [GIT PULL 1/3] SoC " 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-1633950030-501948@atomide.com-2 \
--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).