From: Jerome Brunet <jbrunet@baylibre.com>
To: George Stark <gnstark@salutedevices.com>
Cc: u.kleine-koenig@pengutronix.de, neil.armstrong@linaro.org,
khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, thierry.reding@gmail.com,
hkallweit1@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@salutedevices.com,
George Stark <gnstark@sberdevices.ru>,
Dmitry Rokosov <ddrokosov@salutedevices.com>
Subject: Re: [PATCH 2/2] pwm: meson: support meson A1 SoC family
Date: Tue, 23 Apr 2024 19:35:15 +0200 [thread overview]
Message-ID: <1jv848ezzo.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20240423161006.2522351-3-gnstark@salutedevices.com>
On Tue 23 Apr 2024 at 19:10, George Stark <gnstark@salutedevices.com> wrote:
> From: George Stark <gnstark@sberdevices.ru>
>
> Add a compatible string and configuration for the meson A1 SoC family
> PWM. Additionally, provide an external clock initialization helper
> specifically designed for these PWM IPs.
>
> Signed-off-by: George Stark <gnstark@sberdevices.ru>
> Signed-off-by: Dmitry Rokosov <ddrokosov@salutedevices.com>
> ---
> drivers/pwm/pwm-meson.c | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/drivers/pwm/pwm-meson.c b/drivers/pwm/pwm-meson.c
> index ea96c5973488..529a541ba7b6 100644
> --- a/drivers/pwm/pwm-meson.c
> +++ b/drivers/pwm/pwm-meson.c
> @@ -462,6 +462,33 @@ static int meson_pwm_init_channels_meson8b_v2(struct pwm_chip *chip)
> return meson_pwm_init_clocks_meson8b(chip, mux_parent_data);
> }
>
> +static int meson_pwm_init_channels_ext_clock(struct pwm_chip *chip)
That kind on naming (ext) is almost sure to clash with whatever comes next.
Just use the name of the first SoC using the method, a1 for instance.
> +{
> + struct device *dev = pwmchip_parent(chip);
> + struct meson_pwm *meson = to_meson_pwm(chip);
> + struct meson_pwm_channel *channels = meson->channels;
> + struct clk_bulk_data *clks = NULL;
> + unsigned int i;
> + int res;
> +
> + res = devm_clk_bulk_get_all(dev, &clks);
> + if (res < 0) {
> + dev_err(dev, "can't get device clocks\n");
> + return res;
> + }
I don't think allocating the 'clk_bulk_data *clks' is necessary or safe.
We know exactly how many clocks we expect, there is no need for a get all.
> +
> + if (res != MESON_NUM_PWMS) {
> + dev_err(dev, "clock count must be %d, got %d\n",
> + MESON_NUM_PWMS, res);
> + return -EINVAL;
> + }
... and this only catches the problem after the fact.
It is probably convinient but not necessary.
> +
> + for (i = 0; i < MESON_NUM_PWMS; i++)
> + channels[i].clk = clks[i].clk;
channels[i].clk could be assigned directly of_clk_get() using clock
indexes. No extra allocation needed.
> +
> + return 0;
> +}
> +
> static const struct meson_pwm_data pwm_meson8b_data = {
> .parent_names = { "xtal", NULL, "fclk_div4", "fclk_div3" },
> .channels_init = meson_pwm_init_channels_meson8b_legacy,
> @@ -500,11 +527,19 @@ static const struct meson_pwm_data pwm_meson8_v2_data = {
> .channels_init = meson_pwm_init_channels_meson8b_v2,
> };
>
> +static const struct meson_pwm_data pwm_meson_ext_clock_data = {
> + .channels_init = meson_pwm_init_channels_ext_clock,
> +};
> +
> static const struct of_device_id meson_pwm_matches[] = {
> {
> .compatible = "amlogic,meson8-pwm-v2",
> .data = &pwm_meson8_v2_data
> },
> + {
> + .compatible = "amlogic,meson-a1-pwm",
> + .data = &pwm_meson_ext_clock_data
> + },
> /* The following compatibles are obsolete */
> {
> .compatible = "amlogic,meson8b-pwm",
--
Jerome
_______________________________________________
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:[~2024-04-23 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 16:10 [PATCH 0/2] pwm: meson: add pwm support for A1 George Stark
2024-04-23 16:10 ` [PATCH 1/2] dt-bindings: pwm: amlogic: Add new bindings for meson A1 pwm George Stark
2024-04-23 16:56 ` Conor Dooley
2024-04-23 17:44 ` Jerome Brunet
2024-04-24 6:02 ` Kelvin Zhang
2024-04-24 12:08 ` Conor Dooley
2024-04-23 16:10 ` [PATCH 2/2] pwm: meson: support meson A1 SoC family George Stark
2024-04-23 17:35 ` Jerome Brunet [this message]
2024-04-23 23:00 ` George Stark
2024-04-24 9:02 ` Jerome Brunet
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=1jv848ezzo.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=ddrokosov@salutedevices.com \
--cc=devicetree@vger.kernel.org \
--cc=gnstark@salutedevices.com \
--cc=gnstark@sberdevices.ru \
--cc=hkallweit1@gmail.com \
--cc=kernel@salutedevices.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@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