From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 4/4] [RFC] Documentation: pwm: rework documentation for the framework
Date: Fri, 26 Jul 2019 11:39:12 +0200 [thread overview]
Message-ID: <20190726093912.q6m6syroot2eqie6@pengutronix.de> (raw)
In-Reply-To: <20190107194938.3004-5-u.kleine-koenig@pengutronix.de>
Hello Thierry,
On Mon, Jan 07, 2019 at 08:49:43PM +0100, Uwe Kleine-König wrote:
> This is a draft for an in my eyes improved documentation describing
> consumers, providers and backend drivers of the PWM framework.
>
> The bigger changes include:
>
> - sysfs description is split into a separate document (otherwise unchanged)
> - Only the new style functions and callbacks are described; the legacy
> stuff is just mentioned shortly in a dedicated paragraph.
> - The expectations for the different callbacks (most importantly .apply)
> are mentioned explicitly.
>
> There is a gap in the documentation because I didn't understand the
> .capture callback. There is no documentation about it, just two drivers
> implementing it. I guess it is about measuring an input signal, so it seems
> to be misplaced in the PWM framework which otherwise is just about an
> output pin.
I'm still waiting for feedback here. AFAICT there is nothing that should
be controversial as I intended to just describe the status quo.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2019-07-26 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:49 [PATCH 0/4] pwm patches for the next merge window Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 1/4] pwm: don't use memcmp to compare struct state variables Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 2/4] pwm: drop per-chip dbg_show callback Uwe Kleine-König
2019-01-10 8:36 ` Thierry Reding
2019-01-10 8:52 ` Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 3/4] pwm: rearrange structures to group members by purpose Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 4/4] [RFC] Documentation: pwm: rework documentation for the framework Uwe Kleine-König
2019-07-26 9:39 ` Uwe Kleine-König [this message]
2019-09-24 12:00 ` Uwe Kleine-König
2019-01-10 8:35 ` [PATCH 0/4] pwm patches for the next merge window Thierry Reding
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=20190726093912.q6m6syroot2eqie6@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).