From: Andi Shyti <andi.shyti@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Peter Korsgaard <peter@korsgaard.com>,
Andrew Lunn <andrew@lunn.ch>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: ocores: Move system PM hooks to the NOIRQ phase
Date: Thu, 27 Jul 2023 02:35:51 +0200 [thread overview]
Message-ID: <20230727003551.dtjx3shwpjs3le6x@intel.intel> (raw)
In-Reply-To: <20230717203857.2626773-1-samuel.holland@sifive.com>
Hi Samuel,
On Mon, Jul 17, 2023 at 01:38:57PM -0700, Samuel Holland wrote:
> 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>
it's OK for me.
Peter, any comment on this?
Andi
> ---
>
> drivers/i2c/busses/i2c-ocores.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
> index 4ac77e57bbbf..b1f621d42910 100644
> --- a/drivers/i2c/busses/i2c-ocores.c
> +++ b/drivers/i2c/busses/i2c-ocores.c
> @@ -743,7 +743,6 @@ static void ocores_i2c_remove(struct platform_device *pdev)
> i2c_del_adapter(&i2c->adap);
> }
>
> -#ifdef CONFIG_PM_SLEEP
> static int ocores_i2c_suspend(struct device *dev)
> {
> struct ocores_i2c *i2c = dev_get_drvdata(dev);
> @@ -772,11 +771,9 @@ static int ocores_i2c_resume(struct device *dev)
> return ocores_init(dev, i2c);
> }
>
> -static SIMPLE_DEV_PM_OPS(ocores_i2c_pm, ocores_i2c_suspend, ocores_i2c_resume);
> -#define OCORES_I2C_PM (&ocores_i2c_pm)
> -#else
> -#define OCORES_I2C_PM NULL
> -#endif
> +static const struct dev_pm_ops ocores_i2c_pm_ops = {
> + NOIRQ_SYSTEM_SLEEP_PM_OPS(ocores_i2c_suspend, ocores_i2c_resume)
> +};
>
> static struct platform_driver ocores_i2c_driver = {
> .probe = ocores_i2c_probe,
> @@ -784,7 +781,7 @@ static struct platform_driver ocores_i2c_driver = {
> .driver = {
> .name = "ocores-i2c",
> .of_match_table = ocores_i2c_match,
> - .pm = OCORES_I2C_PM,
> + .pm = &ocores_i2c_pm_ops,
> },
> };
>
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-07-27 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 20:38 [PATCH] i2c: ocores: Move system PM hooks to the NOIRQ phase Samuel Holland
2023-07-27 0:35 ` Andi Shyti [this message]
2023-08-05 1:20 ` Andi Shyti
2023-10-24 20:20 ` Andi Shyti
2023-10-28 19:36 ` 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=20230727003551.dtjx3shwpjs3le6x@intel.intel \
--to=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.