mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: jpanis@baylibre.com
Cc: devicetree@vger.kernel.org, jic23@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, lars@metafoo.de,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	mranostay@ti.com, robh+dt@kernel.org
Subject: Re: [PATCH v3 2/2] iio: time: capture-tiecap: capture driver support for ECAP
Date: Thu, 28 Jul 2022 22:02:05 +0200	[thread overview]
Message-ID: <3033c2bb-bfe7-459c-2a2b-e99bf33b28b5@wanadoo.fr> (raw)
In-Reply-To: <20220728175124.468461-3-jpanis@baylibre.com>

Le 28/07/2022 à 19:51, Julien Panis a écrit :
> 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-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>

[...]

> +static int ecap_iio_remove(struct platform_device *pdev)
> +{
> +	struct iio_dev *indio_dev = platform_get_drvdata(pdev);
> +	struct ecap_iio_dev *ecap_dev = iio_priv(indio_dev);
> +
> +	if (ecap_dev->enabled)
> +		ecap_iio_capture_disable(indio_dev);
> +
> +	regmap_exit(ecap_dev->regmap);
> +
> +	pm_runtime_disable(&pdev->dev);

Hi,

should these 2 functions be part of an error handling path of the probe, 
or handled with a devm_add_action_or_reset()?

Just my 2c,

CJ

> +
> +	return 0;
> +}
> +

  reply	other threads:[~2022-07-28 20:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 17:51 [PATCH v3 0/2] ECAP support on TI AM62x SoC Julien Panis
2022-07-28 17:51 ` [PATCH v3 1/2] dt-binding: iio: time: add ti,am62-ecap-capture.yaml Julien Panis
2022-07-28 17:55   ` Krzysztof Kozlowski
2022-07-28 17:51 ` [PATCH v3 2/2] iio: time: capture-tiecap: capture driver support for ECAP Julien Panis
2022-07-28 20:02   ` Christophe JAILLET [this message]
2022-07-29  7:50     ` Julien Panis
2022-07-31 15:41   ` Jonathan Cameron
2022-08-01 14:08     ` Julien Panis
2022-08-02 13:28       ` Julien Panis
2022-08-06 17:01         ` Jonathan Cameron
2022-08-08  0:30         ` William Breathitt Gray
2022-08-08  8:58           ` Julien Panis
2022-08-08 16:19             ` William Breathitt Gray
2022-08-09  6:19               ` Julien Panis
2022-08-09  6:23                 ` Julien Panis
2022-08-06 16:45       ` Jonathan Cameron

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=3033c2bb-bfe7-459c-2a2b-e99bf33b28b5@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=jpanis@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mranostay@ti.com \
    --cc=robh+dt@kernel.org \
    /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

all inboxes | Powered by JetHome®