From: "Andreas Färber" <afaerber@suse.de>
To: Andreas Klinger <ak@it-klinger.de>
Cc: arnd@arndb.de, davem@davemloft.net, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, jic23@kernel.org, johan@kernel.org,
khilman@baylibre.com, knaack.h@gmx.de, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, martin.blumenstingl@googlemail.com,
mchehab+samsung@kernel.org, m.othacehe@gmail.com,
nicolas.ferre@microchip.com, pmeerw@pmeerw.net,
robh+dt@kernel.org, robh@kernel.org, songqiang1304521@gmail.com,
treding@nvidia.com
Subject: Re: [PATCH 1/4] maxbotix,mb12x2.txt: add dt doc for maxbotix,mb12x2
Date: Sun, 24 Feb 2019 17:51:53 +0100 [thread overview]
Message-ID: <5c2efbb1-e243-a272-5106-9cd279d1c973@suse.de> (raw)
In-Reply-To: <20190224162208.esbrzartgfqxptsw@arbad>
Hi Andreas,
Am 24.02.19 um 17:22 schrieb Andreas Klinger:
> add dt doc for maxbotix,mb12x2 and also a new vendor prefix maxbotix
Please don't mix the two.
The subject prefix should be "dt-bindings:". Please compare git log.
And please avoid putting the whole world in To rather than CC.
>
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>
> ---
> .../bindings/iio/proximity/maxbotix,mb12x2.txt | 22 ++++++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 23 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/proximity/maxbotix,mb12x2.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/proximity/maxbotix,mb12x2.txt b/Documentation/devicetree/bindings/iio/proximity/maxbotix,mb12x2.txt
> new file mode 100644
> index 000000000000..29f7fc09cfdc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/proximity/maxbotix,mb12x2.txt
> @@ -0,0 +1,22 @@
You're aware that a conversion from txt to YAML was under way?
> +* MaxSonar-I2CXL ultrasonic distance sensor of type mb12x2 using the i2c
> + interface for ranging
> +
> +Required properties:
> + - compatible: Should be "maxbotix,mb12x2"
Is that really the model name with x? No wildcards as compatible please.
> +
> + - reg: i2c address of the device
> +
> +Optional properties:
> + - status-gpios: Definition of the status gpio (input) which is used
> + to announce the preceding reading request has
> + finished and that data is available. If no status
> + gpio is specified the device driver falls back to
> + wait a certain amount of time (15 ms) until data
> + can be retrieved.
That sounds like an implementation detail that should not be part of the
binding? It at least needs to be reworded.
> +
> +Example:
> +mb@70 {
Please use a generic node name - maybe proximity? Check other examples.
> + compatible = "maxbotix,mb12x2";
> + reg = <0x70>;
> + status-gpios = <&gpio2 2 GPIO_ACTIVE_HIGH>;
> +};
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 389508584f48..added54a1108 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -225,6 +225,7 @@ lsi LSI Corp. (LSI Logic)
> lwn Liebherr-Werk Nenzing GmbH
> macnica Macnica Americas
> marvell Marvell Technology Group Ltd.
> +maxbotix MaxBotix Inc.
> maxim Maxim Integrated Products
> mbvl Mobiveil Inc.
> mcube mCube
This part looks fine and could get my Reviewed-by if you split it off as
"dt-bindings: Add vendor prefix for MaxBotix" and add a sentence about
the company in its commit message.
You might want to CC the vendor, if you're not contracted by them.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2019-02-24 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 16:22 Andreas Klinger
2019-02-24 16:51 ` Andreas Färber [this message]
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=5c2efbb1-e243-a272-5106-9cd279d1c973@suse.de \
--to=afaerber@suse.de \
--cc=ak@it-klinger.de \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=johan@kernel.org \
--cc=khilman@baylibre.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=songqiang1304521@gmail.com \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®