From: Peter Rosin <peda@axentia.se>
To: Rob Herring <robh@kernel.org>,
Mircea Caprioru <mircea.caprioru@analog.com>
Cc: davem@davemloft.net, mchehab+samsung@kernel.org,
akpm@linux-foundation.org, rdunlap@infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: dt-bindings: add adi,adgs140x doc
Date: Sat, 21 Jul 2018 11:20:14 +0200 [thread overview]
Message-ID: <bbf37fb4-3898-7293-eafd-b4969517333a@axentia.se> (raw)
In-Reply-To: <20180720152815.GA8645@rob-hp-laptop>
On 2018-07-20 17:28, Rob Herring wrote:
> On Fri, Jul 13, 2018 at 03:30:35PM +0300, Mircea Caprioru wrote:
>> Adding dt-bindings documentation for adgs1408/1409 multiplexer. The
>> bindings follow the standard SPI and mux bindings and do not require any
>> additional custom properties.
>
> Drop "Documentation: " from the subject.
Hi Rob,
All the issues reported here (and some more) have been addressed in
subsequent submissions. Please look at v5:
https://www.spinics.net/lists/devicetree/msg240309.html
Cheers,
Peter
>> Signed-off-by: Mircea Caprioru <mircea.caprioru@analog.com>
>> ---
>> .../devicetree/bindings/mux/adi,adgs140x.txt | 39 +++++++++++++++++++
>> MAINTAINERS | 1 +
>> 2 files changed, 40 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mux/adi,adgs140x.txt
>>
>> diff --git a/Documentation/devicetree/bindings/mux/adi,adgs140x.txt b/Documentation/devicetree/bindings/mux/adi,adgs140x.txt
>> new file mode 100644
>> index 000000000000..5f2c2b9e9781
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mux/adi,adgs140x.txt
>> @@ -0,0 +1,39 @@
>> +Bindings for Analog Devices ADGS1408/1409 8:1/Dual 4:1 Mux
>> +
>> +Required properties:
>> +- compatible : "adi,adgs1408" or "adi,adgs1409"
>> +- #mux-control-cells : <0>
>> +* Standard mux-controller bindings as described in mux-controller.txt
>
> What would these be because the only one you have in the example is
> already listed here.
>
>> +
>> +Optional properties:
>> +- idle-state : if present, array of states that the mux controllers will have
>> + when idle. The special state MUX_IDLE_AS_IS is the default and
>> + MUX_IDLE_DISCONNECT is also supported.
>> +
>> +States 0 through 7 correspond to signals S1 through S8 in the datasheet.
>> +
>> +Example:
>> +
>> + /*
>> + * One mux controller.
>> + * Mux 1 to 8 set to idle as is (no idle-state declared)
>> + */
>> + &spi0 {
>> + mux: mux-controller@2 {
>
> unit address should be 0.
>
>> + compatible = "adi,adgs1408";
>> + reg = <0>;
>> + spi-max-frequency = <1000000>;
>> + #mux-control-cells = <0>;
>> + };
>> + }
>> +
>> + adc-mux@3 {
>> + compatible = "io-channel-mux";
>> + io-channels = <&adc 1>;
>> + io-channel-names = "parent";
>> + mux-controls = <&mux>;
>> +
>> + channels = "out_a0", "out_a1", "test0", "test1",
>> + "out_b0", "out_b1", "testb0", "testb1";
>> +
>> + };
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7aa68f38ea4b..6e69c3e2d27a 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -816,6 +816,7 @@ W: http://wiki.analog.com/
>> W: http://ez.analog.com/community/linux-device-drivers
>> S: Supported
>> F: drivers/mux/adgs140x.c
>> +F: Documentation/devicetree/bindings/mux/adgs140x.txt
>>
>> ANALOG DEVICES INC ADV7180 DRIVER
>> M: Lars-Peter Clausen <lars@metafoo.de>
>> --
>> 2.17.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-07-21 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 12:30 [PATCH 2/2] Documentation: dt-bindings: add adi,adgs140x doc Mircea Caprioru
2018-07-20 15:28 ` Rob Herring
2018-07-21 9:20 ` Peter Rosin [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=bbf37fb4-3898-7293-eafd-b4969517333a@axentia.se \
--to=peda@axentia.se \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mircea.caprioru@analog.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
/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