From: Jonathan Cameron <jic23@kernel.org>
To: Julien Panis <jpanis@baylibre.com>
Cc: vilhelm.gray@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
mranostay@ti.com
Subject: Re: [PATCH v4 3/3] counter: capture-tiecap: capture driver support for ECAP
Date: Sun, 14 Aug 2022 15:48:48 +0100 [thread overview]
Message-ID: <20220814154848.24442d4c@jic23-huawei> (raw)
In-Reply-To: <20220810140724.182389-4-jpanis@baylibre.com>
On Wed, 10 Aug 2022 16:07:24 +0200
Julien Panis <jpanis@baylibre.com> wrote:
> ECAP hardware on AM62x SoC supports capture feature. It can be used
> to timestamp events (falling/rising edges) detected on signal input pin.
>
> This commit adds capture driver support for ECAP hardware on AM62x SoC.
>
> In the ECAP hardware, capture pin can also be configured to be in
> PWM mode. Current implementation only supports capture operating mode.
> Hardware also supports timebase sync between multiple instances, but
> this driver supports simple independent capture functionality.
>
> Signed-off-by: Julien Panis <jpanis@baylibre.com>
> ---
Hi Julien,
Been too long since I reviewed a counter driver, so I'll have
to leave that side of things to William (or find a spare few days
to remind myself of the details!)
A few superficial things I notice below whilst taking a quick look.
It might be worth adding a bit of description around what the
result of the various runtime pm calls is (what's actually getting
powered down?)
Jonathan
> +static int ecap_cnt_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct ecap_cnt_dev *ecap_dev;
> + struct counter_device *counter_dev;
> + void __iomem *mmio_base;
> + int ret;
> +
> + counter_dev = devm_counter_alloc(dev, sizeof(*ecap_dev));
> + if (IS_ERR(counter_dev))
> + return PTR_ERR(counter_dev);
> +
> + counter_dev->name = ECAP_DRV_NAME;
> + counter_dev->parent = dev;
> + counter_dev->ops = &ecap_cnt_ops;
> + counter_dev->signals = ecap_cnt_signals;
> + counter_dev->num_signals = ARRAY_SIZE(ecap_cnt_signals);
> + counter_dev->counts = ecap_cnt_counts;
> + counter_dev->num_counts = ARRAY_SIZE(ecap_cnt_counts);
> +
> + ecap_dev = counter_priv(counter_dev);
> +
> + ecap_dev->clk = devm_clk_get(dev, "fck");
> + if (IS_ERR(ecap_dev->clk))
> + return dev_err_probe(dev, PTR_ERR(ecap_dev->clk), "failed to get clock\n");
> +
> + ret = clk_prepare_enable(ecap_dev->clk);
We now have dev_clk_get_enabled() in upstream - finally!
Text book usecase for it here.
> + if (ret) {
> + dev_err(dev, "failed to enable clock\n");
> + return ret;
> + }
> +
> + ret = devm_add_action_or_reset(dev, ecap_cnt_clk_disable, ecap_dev->clk);
> + if (ret) {
> + dev_err(dev, "failed to add clock disable action\n");
> + return ret;
> + }
> +
> + ecap_dev->clk_rate = clk_get_rate(ecap_dev->clk);
> + if (!ecap_dev->clk_rate) {
> + dev_err(dev, "failed to get clock rate\n");
> + return -EINVAL;
> + }
> +
> + mmio_base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(mmio_base))
> + return PTR_ERR(mmio_base);
> +
> + ecap_dev->regmap = devm_regmap_init_mmio(dev, mmio_base, &ecap_cnt_regmap_config);
> + if (IS_ERR(ecap_dev->regmap))
> + return dev_err_probe(dev, PTR_ERR(ecap_dev->regmap), "failed to init regmap\n");
> +
> + spin_lock_init(&ecap_dev->lock);
> +
> + ret = platform_get_irq(pdev, 0);
> + if (ret < 0) {
> + dev_err(dev, "failed to get irq\n");
> + return ret;
> + }
> +
> + ret = devm_request_irq(dev, ret, ecap_cnt_isr, 0, pdev->name, counter_dev);
> + if (ret) {
> + dev_err(dev, "failed to request irq\n");
> + return ret;
> + }
> +
> + platform_set_drvdata(pdev, counter_dev);
> + pm_runtime_enable(dev);
> +
> + ecap_dev->enabled = 0;
> + ecap_cnt_capture_set_evmode(counter_dev, 0);
> +
> + ret = devm_counter_add(dev, counter_dev);
> + if (ret) {
> + dev_err(dev, "failed to add counter\n");
> + pm_runtime_disable(dev);
Unless there is a very good reason to mix devm and unmanaged
code, it's best to not do so as it leads to much head scratching over
whether there are race conditions. Here I can't see a reason not
to use devm_add_action_or_reset() to make the pm_runtime_disabled()
into devm managed.
Any setting of enabled occured after probe() was done so that's
fine as unmanaged or you could register another devm_ callback
if you prefer, but with a comment explaining the path to it needing
to do anything.
> + }
> +
> + return ret;
> +}
> +
> +static int ecap_cnt_remove(struct platform_device *pdev)
> +{
> + struct counter_device *counter_dev = platform_get_drvdata(pdev);
> + struct ecap_cnt_dev *ecap_dev = counter_priv(counter_dev);
> +
> + if (ecap_dev->enabled)
> + ecap_cnt_capture_disable(counter_dev);
> +
> + pm_runtime_disable(&pdev->dev);
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2022-08-14 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 14:07 [PATCH v4 0/3] ECAP support on TI AM62x SoC Julien Panis
2022-08-10 14:07 ` [PATCH v4 1/3] dt-binding: counter: add ti,am62-ecap-capture.yaml Julien Panis
2022-08-10 14:40 ` Krzysztof Kozlowski
2022-08-10 14:07 ` [PATCH v4 2/3] Documentation: ABI: add sysfs-bus-counter-ecap Julien Panis
2022-08-13 22:47 ` William Breathitt Gray
2022-08-10 14:07 ` [PATCH v4 3/3] counter: capture-tiecap: capture driver support for ECAP Julien Panis
2022-08-14 14:48 ` Jonathan Cameron [this message]
2022-08-14 17:03 ` William Breathitt Gray
2022-08-15 11:20 ` William Breathitt Gray
2022-08-16 8:11 ` Julien Panis
2022-08-16 15:22 ` William Breathitt Gray
2022-08-16 7:58 ` Julien Panis
2022-08-16 15:12 ` William Breathitt Gray
2022-08-16 15:28 ` Julien Panis
2022-08-14 18:00 ` [PATCH v4 0/3] ECAP support on TI AM62x SoC William Breathitt Gray
2022-08-16 8:26 ` Julien Panis
2022-08-17 13:48 ` Julien Panis
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=20220814154848.24442d4c@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jpanis@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@ti.com \
--cc=robh+dt@kernel.org \
--cc=vilhelm.gray@gmail.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