public inbox for linux-pwm@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Jonathan Cameron" <Jonathan.Cameron@Huawei.com>
Cc: linux-pwm@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 04/11] pwm: brcmstb: Use DEFINE_SIMPLE_DEV_PM_OPS for PM functions
Date: Wed, 11 Oct 2023 08:42:54 -0700	[thread overview]
Message-ID: <19a13327-e8b6-4bea-ac93-3b418f8845df@broadcom.com> (raw)
In-Reply-To: <20231011153112.44vfwedz4qxlunsa@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]



On 10/11/2023 8:31 AM, Uwe Kleine-König wrote:
> On Wed, Oct 11, 2023 at 12:21:52PM +0100, Jonathan Cameron wrote:
>> On Tue, 10 Oct 2023 09:51:05 +0200
>> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
>>
>>> This macro has the advantage over SIMPLE_DEV_PM_OPS that we don't have to
>>> care about when the functions are actually used, so the corresponding
>>> #ifdef can be dropped.
>>>
>>> Also make use of pm_ptr() to discard all PM related stuff if CONFIG_PM
>>> isn't enabled.
>>
>> The additional change to potentially return an error when not doing so before
>> wants to be called out in the description.
> 
> Indeed, good catch. Something like:
> 
> 	pwm: brcmstb: Use DEFINE_SIMPLE_DEV_PM_OPS for PM
> 
> 	This macro has the advantage over SIMPLE_DEV_PM_OPS that we don't have to
> 	care about when the functions are actually used, so the corresponding
> 	#ifdef can be dropped.
> 
> 	Also make use of pm_ptr() to discard all PM related stuff if CONFIG_PM
> 	isn't enabled.
> 
> 	While touching brcmstb_pwm_suspend() also propagate the return
> 	value of clk_enable() to the caller of .suspend().
> 
> 	Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> I fixed that in my tree, so if and when v2 happens, this comment will be
> addressed.

OK so that makes:

https://lore.kernel.org/all/20231005164728.1846726-1-florian.fainelli@broadcom.com/

void, and now I also need to re-submit:

https://lore.kernel.org/all/20231004175414.1738475-1-florian.fainelli@broadcom.com/

or is Thierry going to resolve that conflict for us?
-- 
Florian

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]

  reply	other threads:[~2023-10-11 15:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  7:51 [PATCH 00/11] pwm: Use DEFINE_SIMPLE_DEV_PM_OPS for PM functions Uwe Kleine-König
2023-10-10  7:51 ` [PATCH 01/11] pwm: atmel-hlcdc: " Uwe Kleine-König
2023-10-11 11:19   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 02/11] pwm: atmel-tcb: " Uwe Kleine-König
2023-10-11 11:20   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 03/11] pwm: berlin: " Uwe Kleine-König
2023-10-10  7:51 ` [PATCH 04/11] pwm: brcmstb: " Uwe Kleine-König
2023-10-11 11:21   ` Jonathan Cameron
2023-10-11 15:31     ` Uwe Kleine-König
2023-10-11 15:42       ` Florian Fainelli [this message]
2023-10-11 16:48         ` Uwe Kleine-König
2023-10-13 13:35           ` Thierry Reding
2023-10-11 16:48   ` Florian Fainelli
2023-10-10  7:51 ` [PATCH 05/11] pwm: dwc: " Uwe Kleine-König
2023-10-10  7:51 ` [PATCH 06/11] pwm: imx-tpm: " Uwe Kleine-König
2023-10-11 11:22   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 07/11] pwm: samsung: " Uwe Kleine-König
2023-10-11 11:22   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 08/11] pwm: stm32-lp: " Uwe Kleine-König
2023-10-11 11:23   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 09/11] pwm: stm32: " Uwe Kleine-König
2023-10-11 11:23   ` Jonathan Cameron
2023-10-10  7:51 ` [PATCH 10/11] pwm: tiecap: " Uwe Kleine-König
2023-10-10  7:51 ` [PATCH 11/11] pwm: tiehrpwm: " Uwe Kleine-König

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=19a13327-e8b6-4bea-ac93-3b418f8845df@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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