From: Thierry Reding <thierry.reding@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 3/3] pwm: Make capture support optional
Date: Wed, 22 Jun 2022 15:46:32 +0200 [thread overview]
Message-ID: <YrMdON4uOMfDFN8h@orome> (raw)
In-Reply-To: <20220523174502.987113-3-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Mon, May 23, 2022 at 07:45:02PM +0200, Uwe Kleine-König wrote:
> The only code making use of the capture functionality is the sysfs code
> in the PWM framework. I suspect there are no real users and would like to
> deprecate it in favor of the counter framework. So introduce a kconfig
> symbol to remove the capture support and make the sysfs file a stub.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> drivers/pwm/Kconfig | 12 ++++++++++++
> drivers/pwm/core.c | 3 ++-
> drivers/pwm/pwm-sti.c | 4 ++++
> drivers/pwm/pwm-stm32.c | 4 ++++
> drivers/pwm/sysfs.c | 4 ++++
> include/linux/pwm.h | 5 +++++
> 6 files changed, 31 insertions(+), 1 deletion(-)
I've applied patches 1-2 for now, but I'm not convinced about this yet.
The PWM capture is something that's typically useful for applications
served from userspace, which is why only the sysfs implementation
exists. So anything that's based on another framework is likely not
going to have in-kernel users either. Can you specify exactly how this
alternative implementation would look like and how it would be an
improvement over the current implementation?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-22 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 17:45 [PATCH 1/3] pwm: Reorder header file to get rid of struct pwm_capture forward declaration Uwe Kleine-König
2022-05-23 17:45 ` [PATCH 2/3] pwm: Drop unused forward declaration from pwm.h Uwe Kleine-König
2022-05-23 17:45 ` [PATCH 3/3] pwm: Make capture support optional Uwe Kleine-König
2022-06-22 13:46 ` Thierry Reding [this message]
2022-06-22 17:09 ` Uwe Kleine-König
2022-09-30 15:43 ` Uwe Kleine-König
2022-10-06 13:10 ` Thierry Reding
2022-10-06 14:35 ` Uwe Kleine-König
2022-10-07 9:58 ` Thierry Reding
2022-11-17 22:19 ` William Breathitt Gray
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=YrMdON4uOMfDFN8h@orome \
--to=thierry.reding@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.