From: Rob Herring <robh@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andreas Klinger <ak@it-klinger.de>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
mark.rutland@arm.com, afaerber@suse.de, arnd@arndb.de,
davem@davemloft.net, gregkh@linuxfoundation.org,
johan@kernel.org, khilman@baylibre.com, knaack.h@gmx.de,
lars@metafoo.de, linux-kernel@vger.kernel.org,
martin.blumenstingl@googlemail.com, mchehab+samsung@kernel.org,
m.othacehe@gmail.com, nicolas.ferre@microchip.com,
pmeerw@pmeerw.net, songqiang1304521@gmail.com,
treding@nvidia.com, techsupport@maxbotix.com
Subject: Re: [PATCH v2 2/4] dt-bindings: maxbotix,i2cxl: Add MaxBotix i2c ultrasonic rangers
Date: Tue, 12 Mar 2019 11:39:30 -0500 [thread overview]
Message-ID: <20190312163930.GA30288@bogus> (raw)
In-Reply-To: <20190302182639.48e73885@archlinux>
On Sat, Mar 02, 2019 at 06:26:39PM +0000, Jonathan Cameron wrote:
> On Fri, 1 Mar 2019 14:42:27 +0100
> Andreas Klinger <ak@it-klinger.de> wrote:
>
> > Add doc for dt binding maxbotix,i2cxl. This binding is for MaxBotix
> > I2CXL-MaxSonar ultrasonic rangers which share a common i2c interface.
>
> I'm a bit confused on the naming. Certainly the binding should have
> separate entries for each supported part, rather than a group one
> for their i2cxl naming. Having said that they do have a wide
> range of parts with only the one datasheet.
>
> Rob, what do you think? Go with this i2cxl naming
> or list the individual supported parts?
Looks like the difference is mainly just the range. Is that something
s/w needs to know about?
>
> mb1202, mb1212, mb1222, mb1232, mb1242, mb7040,
> mb7137?
OTOH, that's not really too many.
Rob
prev parent reply other threads:[~2019-03-12 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 13:42 [PATCH v2 2/4] dt-bindings: maxbotix,i2cxl: Add MaxBotix i2c ultrasonic rangers Andreas Klinger
2019-03-02 18:26 ` Jonathan Cameron
2019-03-12 16:39 ` Rob Herring [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=20190312163930.GA30288@bogus \
--to=robh@kernel.org \
--cc=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=songqiang1304521@gmail.com \
--cc=techsupport@maxbotix.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 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.