From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] regmap: regmap-irq: Move handle_post_irq to before pm_runtime_put
Date: Thu, 01 Jun 2023 14:40:45 +0100 [thread overview]
Message-ID: <168562684586.62862.2063265056919048748.b4-ty@kernel.org> (raw)
In-Reply-To: <20230601101036.1499612-1-ckeepax@opensource.cirrus.com>
On Thu, 01 Jun 2023 11:10:35 +0100, Charles Keepax wrote:
> Typically handle_post_irq is going to be used to manage some
> additional chip specific hardware operations required on each IRQ,
> these are very likely to want the chip to be resumed. For example the
> current in tree user max77620 uses this to toggle a global mask bit,
> which would obviously want the device resumed. It is worth noting this
> device does not specify the runtime_pm flag in regmap_irq_chip, so
> there is no actual issue.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/2] regmap: regmap-irq: Move handle_post_irq to before pm_runtime_put
commit: 02534c8e967b51940ae7c0cd99befe216f1c2c8d
[2/2] regmap: Add missing cache_only checks
commit: 99e8dd39f34333d745e6c220be5d166e85214e6c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-06-01 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 10:10 Charles Keepax
2023-06-01 10:10 ` [PATCH 2/2] regmap: Add missing cache_only checks Charles Keepax
2023-06-01 13:40 ` Mark Brown [this message]
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=168562684586.62862.2063265056919048748.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rafael@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
all inboxes | Powered by JetHome®