From: Peter Korsgaard <peter@korsgaard.com>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: ocores: Move system PM hooks to the NOIRQ phase
Date: Mon, 13 Nov 2023 08:50:13 +0100 [thread overview]
Message-ID: <87r0kuf5xm.fsf@48ers.dk> (raw)
In-Reply-To: <20231113023249.1185682-1-samuel.holland@sifive.com> (Samuel Holland's message of "Sun, 12 Nov 2023 18:32:45 -0800")
>>>>> "Samuel" == Samuel Holland <samuel.holland@sifive.com> writes:
> When an I2C device contains a wake IRQ subordinate to a regmap-irq chip,
> the regmap-irq code must be able to perform I2C transactions during
> suspend_device_irqs() and resume_device_irqs(). Therefore, the bus must
> be suspended/resumed during the NOIRQ phase.
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
Acked-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Changes in v2:
> - Rebase on v6.7-rc1
> drivers/i2c/busses/i2c-ocores.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
> index 041a76f71a49..e106af83cef4 100644
> --- a/drivers/i2c/busses/i2c-ocores.c
> +++ b/drivers/i2c/busses/i2c-ocores.c
> @@ -771,8 +771,8 @@ static int ocores_i2c_resume(struct device *dev)
> return ocores_init(dev, i2c);
> }
> -static DEFINE_SIMPLE_DEV_PM_OPS(ocores_i2c_pm,
> - ocores_i2c_suspend, ocores_i2c_resume);
> +static DEFINE_NOIRQ_DEV_PM_OPS(ocores_i2c_pm,
> + ocores_i2c_suspend, ocores_i2c_resume);
> static struct platform_driver ocores_i2c_driver = {
> .probe = ocores_i2c_probe,
> --
> 2.42.0
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2023-11-13 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 2:32 [PATCH v2] i2c: ocores: Move system PM hooks to the NOIRQ phase Samuel Holland
2023-11-13 7:50 ` Peter Korsgaard [this message]
2023-11-13 17:45 ` Wolfram Sang
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=87r0kuf5xm.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.holland@sifive.com \
/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