From: "Gole, Dhruva" <d-gole@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vaishnav Achath <vaishnav.a@ti.com>, Vignesh <vigneshr@ti.com>,
Apurva Nandan <a-nandan@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>
Subject: Re: [PATCH 1/2] spi: cadence-quadspi: use macro SIMPLE_DEV_PM_OPS
Date: Tue, 18 Apr 2023 19:47:57 +0530 [thread overview]
Message-ID: <c2cc4f31-97e0-fa1a-befd-f0dfad751022@ti.com> (raw)
In-Reply-To: <e65683c1-9f1b-4cfb-8e14-087ef7d69595@sirena.org.uk>
Hi Mark, Thanks for going through my patch.
On 4/18/2023 6:22 PM, Mark Brown wrote:
> On Mon, Apr 17, 2023 at 02:40:26PM +0530, Dhruva Gole wrote:
>
>> -static const struct dev_pm_ops cqspi__dev_pm_ops = {
>> - .suspend = cqspi_suspend,
>> - .resume = cqspi_resume,
>> -};
>> +static SIMPLE_DEV_PM_OPS(cqspi__dev_pm_ops, cqspi_suspend, cqspi_resume);
>>
>> #define CQSPI_DEV_PM_OPS (&cqspi__dev_pm_ops)
>> #else
> These days you should use DEFINE_SIMPLE_DEV_PM_OPS() instead.
Sure, I can respin this series with this macro instead,
https://elixir.bootlin.com/linux/v6.1/source/include/linux/pm.h#L399
So essentially it will look like,
static DEFINE_SIMPLE_DEV_PM_OPS(cqspi__dev_pm_ops, cqspi_suspend, cqspi_resume);
Are there any other improvements you'd like me to make in my next revision of this series?
--
Regards,
Dhruva Gole <d-gole@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Gole, Dhruva" <d-gole@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vaishnav Achath <vaishnav.a@ti.com>, Vignesh <vigneshr@ti.com>,
Apurva Nandan <a-nandan@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>
Subject: Re: [PATCH 1/2] spi: cadence-quadspi: use macro SIMPLE_DEV_PM_OPS
Date: Tue, 18 Apr 2023 19:47:57 +0530 [thread overview]
Message-ID: <c2cc4f31-97e0-fa1a-befd-f0dfad751022@ti.com> (raw)
In-Reply-To: <e65683c1-9f1b-4cfb-8e14-087ef7d69595@sirena.org.uk>
Hi Mark, Thanks for going through my patch.
On 4/18/2023 6:22 PM, Mark Brown wrote:
> On Mon, Apr 17, 2023 at 02:40:26PM +0530, Dhruva Gole wrote:
>
>> -static const struct dev_pm_ops cqspi__dev_pm_ops = {
>> - .suspend = cqspi_suspend,
>> - .resume = cqspi_resume,
>> -};
>> +static SIMPLE_DEV_PM_OPS(cqspi__dev_pm_ops, cqspi_suspend, cqspi_resume);
>>
>> #define CQSPI_DEV_PM_OPS (&cqspi__dev_pm_ops)
>> #else
> These days you should use DEFINE_SIMPLE_DEV_PM_OPS() instead.
Sure, I can respin this series with this macro instead,
https://elixir.bootlin.com/linux/v6.1/source/include/linux/pm.h#L399
So essentially it will look like,
static DEFINE_SIMPLE_DEV_PM_OPS(cqspi__dev_pm_ops, cqspi_suspend, cqspi_resume);
Are there any other improvements you'd like me to make in my next revision of this series?
--
Regards,
Dhruva Gole <d-gole@ti.com>
_______________________________________________
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:[~2023-04-18 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:10 [PATCH 0/2] Fix PM Hooks in the Cadence Quad SPI Driver Dhruva Gole
2023-04-17 9:10 ` Dhruva Gole
2023-04-17 9:10 ` [PATCH 1/2] spi: cadence-quadspi: use macro SIMPLE_DEV_PM_OPS Dhruva Gole
2023-04-17 9:10 ` Dhruva Gole
2023-04-18 12:52 ` Mark Brown
2023-04-18 12:52 ` Mark Brown
2023-04-18 14:17 ` Gole, Dhruva [this message]
2023-04-18 14:17 ` Gole, Dhruva
2023-04-18 16:19 ` Mark Brown
2023-04-18 16:19 ` Mark Brown
2023-04-17 9:10 ` [PATCH 2/2] spi: cadence-quadspi: fix suspend-resume implementations Dhruva Gole
2023-04-17 9:10 ` Dhruva Gole
2023-04-18 16:21 ` (subset) [PATCH 0/2] Fix PM Hooks in the Cadence Quad SPI Driver Mark Brown
2023-04-18 16:21 ` Mark Brown
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=c2cc4f31-97e0-fa1a-befd-f0dfad751022@ti.com \
--to=d-gole@ti.com \
--cc=a-nandan@ti.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.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.