From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ben Dooks <ben.dooks@sifive.com>
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Greentime Hu <greentime.hu@sifive.com>,
jarkko.nikula@linux.intel.com,
William Salmon <william.salmon@sifive.com>,
Jude Onyenegecha <jude.onyenegecha@sifive.com>
Subject: Re: [PATCH v6 04/10] pwm: dwc: move memory alloc to own function
Date: Thu, 10 Nov 2022 16:35:11 +0100 [thread overview]
Message-ID: <20221110153511.6ymoier2sd3fmepy@pengutronix.de> (raw)
In-Reply-To: <20221020151610.59443-5-ben.dooks@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
Hello,
On Thu, Oct 20, 2022 at 04:16:04PM +0100, Ben Dooks wrote:
> In preparation for adding other bus support, move the allocation
> of the pwm struct out of the main driver code.
>
> Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
> ---
> drivers/pwm/pwm-dwc.c | 24 +++++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/pwm/pwm-dwc.c b/drivers/pwm/pwm-dwc.c
> index c706ef9a7ba1..61f11e0a9319 100644
> --- a/drivers/pwm/pwm-dwc.c
> +++ b/drivers/pwm/pwm-dwc.c
> @@ -196,13 +196,29 @@ static const struct pwm_ops dwc_pwm_ops = {
> .owner = THIS_MODULE,
> };
>
> +static struct dwc_pwm *dwc_pwm_alloc(struct device *dev)
> +{
> + struct dwc_pwm *dwc;
> +
> + dwc = devm_kzalloc(dev, sizeof(*dwc), GFP_KERNEL);
> + if (!dwc)
> + return NULL;
> +
> + dwc->chip.dev = dev;
> + dwc->chip.ops = &dwc_pwm_ops;
> + dwc->chip.npwm = DWC_TIMERS_TOTAL;
> +
> + dev_set_drvdata(dev, dwc);
This was a pci_set_drvdata before. While it's common knowledge (and
implicitly used in several code parts) that pci_set_drvdata(pdev, data)
is just the same as dev_set_drvdata(&pdev->dev, data), it would be nice
if the driver only used either dev_[sg]et_drvdata or pci_[sg]et_drvdata.
Using the former in dwc_pwm_resume and dwc_pwm_suspend is even a tad
shorter.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-10 15:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:16 [PATCH v6 00/10] Designware PWM driver updates for OF Ben Dooks
2022-10-20 15:16 ` [PATCH v6 01/10] dt-bindings: pwm: Document Synopsys DesignWare snps,pwm-dw-apb-timers-pwm2 Ben Dooks
2022-10-20 15:36 ` Krzysztof Kozlowski
2022-10-24 15:45 ` Ben Dooks
2022-10-20 15:39 ` Uwe Kleine-König
2022-11-17 16:10 ` Uwe Kleine-König
2022-10-20 15:16 ` [PATCH v6 02/10] pwm: dwc: allow driver to be built with COMPILE_TEST Ben Dooks
2022-10-20 15:51 ` Uwe Kleine-König
2022-10-20 15:16 ` [PATCH v6 03/10] pwm: dwc: change &pci->dev to dev in probe Ben Dooks
2022-10-20 15:16 ` [PATCH v6 04/10] pwm: dwc: move memory alloc to own function Ben Dooks
2022-11-10 15:35 ` Uwe Kleine-König [this message]
2022-10-20 15:16 ` [PATCH v6 05/10] pwm: dwc: use devm_pwmchip_add Ben Dooks
2022-10-20 15:55 ` Uwe Kleine-König
2022-10-20 15:16 ` [PATCH v6 06/10] pwm: dwc: split pci out of core driver Ben Dooks
2022-11-10 15:29 ` Uwe Kleine-König
2022-11-10 16:35 ` Ben Dooks
2022-11-17 16:15 ` Uwe Kleine-König
2022-10-20 15:16 ` [PATCH v6 07/10] pwm: dwc: make timer clock configurable Ben Dooks
2022-11-10 15:39 ` Uwe Kleine-König
2022-10-20 15:16 ` [PATCH v6 08/10] pwm: dwc: add of/platform support Ben Dooks
2022-10-20 15:16 ` [PATCH v6 09/10] pwm: dwc: add PWM bit unset in get_state call Ben Dooks
2022-10-20 15:16 ` [PATCH v6 10/10] pwm: dwc: use clock rate in hz to avoid rounding issues Ben Dooks
2022-11-10 15:42 ` Uwe Kleine-König
2022-11-10 16:29 ` Ben Dooks
2022-10-24 8:39 ` [PATCH v6 00/10] Designware PWM driver updates for OF Jarkko Nikula
2022-10-24 15:40 ` Ben Dooks
2022-11-08 11:19 ` Ben Dooks
2022-11-08 11:48 ` 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=20221110153511.6ymoier2sd3fmepy@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=ben.dooks@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=greentime.hu@sifive.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jude.onyenegecha@sifive.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=william.salmon@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;
as well as URLs for NNTP newsgroup(s).