From: Rob Herring <robh@kernel.org>
To: Fabio Baltieri <fabiobaltieri@chromium.org>
Cc: "Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee.jones@linaro.org>,
chrome-platform@lists.linux.dev, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: update google,cros-ec-pwm documentation
Date: Thu, 7 Apr 2022 11:49:09 -0500 [thread overview]
Message-ID: <Yk8WBXBH53rtZsBF@robh.at.kernel.org> (raw)
In-Reply-To: <Yk73f9yyxy5LBC+V@google.com>
On Thu, Apr 07, 2022 at 02:38:55PM +0000, Fabio Baltieri wrote:
> Hi Rob,
>
> On Wed, Apr 06, 2022 at 10:41:45AM -0500, Rob Herring wrote:
> > On Thu, Mar 31, 2022 at 12:58:17PM +0000, Fabio Baltieri wrote:
> > > Update google,cros-ec-pwm node documentation to mention the
> > > google,use_pwm_type property.
> > >
> > > Signed-off-by: Fabio Baltieri <fabiobaltieri@chromium.org>
> > > ---
> > > .../devicetree/bindings/pwm/google,cros-ec-pwm.yaml | 6 ++++++
> > > 1 file changed, 6 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml b/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml
> > > index 4cfbffd8414a..9c895c990ed8 100644
> > > --- a/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml
> > > +++ b/Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml
> > > @@ -19,6 +19,12 @@ description: |
> > > properties:
> > > compatible:
> > > const: google,cros-ec-pwm
> > > +
> > > + google,use-pwm-type:
> > > + description:
> > > + Use PWM types (CROS_EC_PWM_DT_<...>) instead of generic channels.
> > > + type: boolean
> >
> > Either do a new compatible string if the cell interpretation is mutually
> > exclusive (channel number vs. type) or split the number space for the
> > 1st cell between type and channel number. IOW, set a bit (31?) to
> > signify the number is a type, not a channel.
>
> Split the number space was my first (tentative) implementation as well,
> but it turns out that the PWM subsystem really wants channels to be
> zero-based[1], so I don't think flags or bitmasks are really an option.
Fix the PWM subsystem then...
> New compatible sounds good though, I'll rework a v3 with that change.
>
> Thanks!
> Fabio
>
> [1] https://elixir.bootlin.com/linux/v5.17/source/drivers/pwm/core.c#L423
>
> --
> Fabio Baltieri
next prev parent reply other threads:[~2022-04-07 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:58 [PATCH v2 0/4] Add channel type support to pwm-cros-ec Fabio Baltieri
2022-03-31 12:58 ` [PATCH v2 1/4] dt-bindings: add mfd/cros_ec definitions Fabio Baltieri
2022-03-31 12:58 ` [PATCH v2 2/4] drivers: pwm: pwm-cros-ec: add channel type support Fabio Baltieri
2022-04-06 3:07 ` Tzung-Bi Shih
2022-03-31 12:58 ` [PATCH v2 3/4] dt-bindings: update google,cros-ec-pwm documentation Fabio Baltieri
2022-04-06 15:41 ` Rob Herring
2022-04-07 14:38 ` Fabio Baltieri
2022-04-07 16:49 ` Rob Herring [this message]
2022-04-07 19:36 ` Fabio Baltieri
2022-03-31 12:58 ` [PATCH v2 4/4] arm64: dts: address cros-ec-pwm channels by type Fabio Baltieri
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=Yk8WBXBH53rtZsBF@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=fabiobaltieri@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.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