From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pwm: st: convert sti-pwm to DT schema
Date: Thu, 3 Aug 2023 09:18:14 +0200 [thread overview]
Message-ID: <8e74af01-36c6-3a41-6d31-91b09ea62026@gmail.com> (raw)
In-Reply-To: <20230802080238.d3nam6elnern65rb@pengutronix.de>
Hi
Le 02/08/2023 à 10:02, Uwe Kleine-König a écrit :
> Hello,
>
> On Wed, Aug 02, 2023 at 12:05:59AM +0200, Raphael Gallais-Pou wrote:
>> + st,capture-num-chan:
>> + $ref: "/schemas/types.yaml#/definitions/uint32"
>> + description: Number of available Capture channels.
>
> I have the theory that nobody actually uses the capture feature and I'd
> like to get rid of it. People who do use it, should better switch to the
> counter driver.
TBH I only found two drivers using it, including this one.
$ grep -rinI "\.capture" drivers/pwm/ | wc -l
2
While I agree that there is not much drivers using capture feature, I
have mixed feelings about removing it.
>
> I wonder if this is the opportunity to drop st,capture-num-chan. There
> is no mainline user.
If there is no opposition about removing this feature I suggest to do it
in a second time, in a serie.
Regards,
Raphaël
>
> Best regards
> Uwe
>
next prev parent reply other threads:[~2023-08-03 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 22:05 [PATCH] dt-bindings: pwm: st: convert sti-pwm to DT schema Raphael Gallais-Pou
2023-08-02 8:02 ` Uwe Kleine-König
2023-08-03 7:18 ` Raphaël Gallais-Pou [this message]
2023-08-03 8:56 ` Uwe Kleine-König
2023-08-03 16:09 ` Conor Dooley
2023-08-03 17:19 ` Raphaël Gallais-Pou
2023-08-11 19:29 ` Rob Herring
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=8e74af01-36c6-3a41-6d31-91b09ea62026@gmail.com \
--to=rgallaispou@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=patrice.chotard@foss.st.com \
--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