From: Hal Feng <hal.feng@starfivetech.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andreas Schwab <schwab@suse.de>, Conor Dooley <conor@kernel.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v1 0/2] Fix an irq issue and add system pm ops for StarFive JH7110 pinctrl drivers
Date: Tue, 5 Sep 2023 20:21:03 +0800 [thread overview]
Message-ID: <20230905122105.117000-1-hal.feng@starfivetech.com> (raw)
This patchset fixes some issues arising when CONFIG_PM is enabled
or suspending to disk.
The first patch fixes failure to set irq after CONFIG_PM is enabled.
The second patch adds system pm ops to save and restore context. So it can
ensure that the pins configuration keep consistent with the one before
suspending.
Hal Feng (2):
pinctrl: starfive: jh7110: Fix failure to set irq after CONFIG_PM is
enabled
pinctrl: starfive: jh7110: Add system pm ops to save and restore
context
MAINTAINERS | 1 +
.../starfive/pinctrl-starfive-jh7110-aon.c | 4 ++
.../starfive/pinctrl-starfive-jh7110-sys.c | 4 ++
.../starfive/pinctrl-starfive-jh7110.c | 42 ++++++++++++++++++-
.../starfive/pinctrl-starfive-jh7110.h | 4 ++
5 files changed, 53 insertions(+), 2 deletions(-)
base-commit: 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
--
2.38.1
next reply other threads:[~2023-09-05 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 12:21 Hal Feng [this message]
2023-09-05 12:21 ` [PATCH v1 1/2] pinctrl: starfive: jh7110: Fix failure to set irq after CONFIG_PM is enabled Hal Feng
2023-09-05 12:21 ` [PATCH v1 2/2] pinctrl: starfive: jh7110: Add system pm ops to save and restore context Hal Feng
2023-09-12 8:10 ` [PATCH v1 0/2] Fix an irq issue and add system pm ops for StarFive JH7110 pinctrl drivers Linus Walleij
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=20230905122105.117000-1-hal.feng@starfivetech.com \
--to=hal.feng@starfivetech.com \
--cc=conor@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=jianlong.huang@starfivetech.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
/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).