From: Thierry Reding <thierry.reding@gmail.com>
To: Wesley Terpstra <wesley@sifive.com>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"David Lechner" <david@lechnology.com>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
"SZ Lin" <sz.lin@moxa.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: added new pwm-sifive driver documentation
Date: Mon, 30 Apr 2018 10:19:46 +0200 [thread overview]
Message-ID: <20180430081946.GH2484@ulmo> (raw)
In-Reply-To: <CAMgXwThYN1E=awkd8yF2aNN+QOLwHkx=UyWqGrOnMxv5jyVj5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Sun, Apr 29, 2018 at 02:08:07PM -0700, Wesley Terpstra wrote:
> On Sun, Apr 29, 2018 at 2:01 PM, Andreas Färber <afaerber@suse.de> wrote:
> > "pwm0" sounds like a zero-indexed instance of some pwm block. If 0 is
> > the version here, I'd suggest to make it "pwm-0" for example - you might
> > want to take a look at the Xilinx bindings, which use a strict x.yy suffix.
>
> That's fine. I'll change it to pwm-0.00 in the next patch series.
This should match the version that you use. If you're internal
versioning uses single digits, or a single version number, then I think
there's no need to use 0.00, because that would just be confusing.
However I think it'd be good to make sure it is discernible as a version
number. Perhaps something like sifive,pwm-v0. That seems to be a fairly
common scheme.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-30 8:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 22:59 [PATCH 0/3] SiFive SoC PWM driver Wesley W. Terpstra
2018-04-27 22:59 ` [PATCH 1/3] dt-bindings: added new pwm-sifive driver documentation Wesley W. Terpstra
2018-04-29 5:54 ` Thierry Reding
2018-04-29 20:51 ` Wesley Terpstra
2018-04-29 21:01 ` Andreas Färber
2018-04-29 21:08 ` Wesley Terpstra
2018-04-30 8:19 ` Thierry Reding [this message]
2018-04-30 10:45 ` Andreas Färber
2018-05-01 16:11 ` Rob Herring
2018-04-30 8:27 ` Thierry Reding
2018-04-30 19:09 ` Wesley Terpstra
2018-04-30 9:42 ` Thierry Reding
2018-04-27 22:59 ` [PATCH 2/3] dt-bindings: Add "sifive" vendor prefix Wesley W. Terpstra
2018-04-28 11:21 ` Andreas Färber
2018-04-28 22:37 ` Wesley Terpstra
2018-05-01 16:14 ` Rob Herring
2018-05-01 16:32 ` Palmer Dabbelt
2018-04-27 22:59 ` [PATCH 3/3] pwm-sifive: add a driver for SiFive SoC PWM Wesley W. Terpstra
2018-04-30 9:39 ` Thierry Reding
2018-04-30 19:09 ` Wesley Terpstra
2018-05-04 8:43 ` kbuild test robot
2018-05-04 8:43 ` kbuild test robot
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=20180430081946.GH2484@ulmo \
--to=thierry.reding@gmail.com \
--cc=afaerber@suse.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=noralf@tronnes.org \
--cc=robh+dt@kernel.org \
--cc=sz.lin@moxa.com \
--cc=wesley@sifive.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 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.