From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Valentin Sitdikov <valentin_sitdikov@mentor.com>,
<lee.jones@linaro.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Andrei Dranitca <Andrei_Dranitca@mentor.com>
Subject: Re: [PATCH 1/2] dt-bindings: mfd: Add DT bindings documentation for the max7360 mfd driver
Date: Tue, 13 Jun 2017 16:28:52 +0300 [thread overview]
Message-ID: <a476aafe-a75f-35bb-bfff-fc73a7f862cc@mentor.com> (raw)
In-Reply-To: <20170613122051.6061-2-valentin_sitdikov@mentor.com>
Hi Valentin,
On 06/13/2017 03:20 PM, Valentin Sitdikov wrote:
> This patch adds documentation for the max7360 bindings.
> The max7360 is Multi-functional Device containing gpio,
> keypad, pwm and rotary encoder submodules.
>
> Signed-off-by: Andrei Dranitca <Andrei_Dranitca@mentor.com>
> Signed-off-by: Valentin Sitdikov <valentin_sitdikov@mentor.com>
> ---
> Documentation/devicetree/bindings/mfd/max7360.txt | 74 +++++++++++++++++++++++
> 1 file changed, 74 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/max7360.txt
>
> diff --git a/Documentation/devicetree/bindings/mfd/max7360.txt b/Documentation/devicetree/bindings/mfd/max7360.txt
> new file mode 100644
> index 0000000..c2ceaf9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/max7360.txt
> @@ -0,0 +1,74 @@
> +* Maxim MAX7360 Multi-function Device
> +
> +The Maxim MAX7360 is a Multi-function Device which includes
> +64 key switches, 8 LED drivers/GPIOs, PWM intensity control,
> +and rotary switch control.
> +
> +Required properties:
> +- compatible: Should be the following: "maxim,max7360".
> +- reg: Specifies the I2C slave address of the max7360 block.
> + It can be 0x38, 0x3a, 0x3c or 0x3e IIUC.
"IIUC" note is highly undesirable ;)
> +
> +Optional properties:
> +- interrupt-parent: Specifies the phandle of the interrupt controller to
> + which the interrupts from MAX7360 are routed to.
> +- interrupts: List of IRQ lines specifiers.
> +- interrupt-names: List of "inti" and "intk".
> +- interrupt-controller: Identifies the device as an interrupt controller.
> +- #interrupt-cells : Number of cells to encode an interrupt source,
> + shall be 1.
> +
> +Examples:
> +
> +Without subnodes:
> + max7360@38 {
> + compatible = "maxim,max7360";
> + reg = <0x38>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <23 IRQ_TYPE_LEVEL_LOW>, <23 IRQ_TYPE_LEVEL_LOW>;
> + interrupt-names = "inti", "intk";
> + interrupt-controller;
> + #interrupt-cells = <0x1>;
> + };
Can you drop the example above? It does not bring any new information.
> +
> +With subnodes:
> + max7360@38 {
Commonly for device node names generic/device class names are utilized,
however I can not suggest what name is better.
> + compatible = "maxim,max7360";
> + reg = <0x38>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <23 IRQ_TYPE_LEVEL_LOW>, <23 IRQ_TYPE_LEVEL_LOW>;
> + interrupt-names = "inti", "intk";
> + interrupt-controller;
> + #interrupt-cells = <0x1>;
For #*-cells properties plese specify plain integers, #interrupt-cells = <1>;
> +
> + gpio {
> + compatible = "maxim,max7360-gpio";
> + gpio-controller;
> + #gpio-cells = <0x2>;
Please use a plain integer.
> + interrupt-controller;
> + #interrupt-cells = <0x2>;
Please use a plain integer.
> + interrupts = <0>;
> + };
> +
> + keypad {
> + compatible = "maxim,max7360-keypad";
> + maxim,debounce_reg = /bits/ 8 <0xef>;
> + maxim,ports_reg = /bits/ 8 <0xae>;
Here I'd rather suggest
1) use 32-bit values,
2) rename properties by replacing underscore by a hyphen.
> + linux,keymap = < MATRIX_KEY(0, 0, KEY_F5)
> + MATRIX_KEY(1, 0, KEY_F4) >;
> + keypad,num-rows = <2>;
> + keypad,num-columns = <1>;
> + interrupts = <1>;
> + };
> +
> + pwm {
> + compatible = "maxim,max7360-pwm";
> + #pwm-cells = <0x2>;
Please use a plain integer.
> + };
> +
> + rotary-encoder {
> + compatible = "maxim,max7360-rotary";
> + interrupts = <2>;
> + };
> +
Please drop an empty line above.
> + };
>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2017-06-13 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:20 [PATCH v4 0/2] dt-bindings: mfd: Add max7360 mfd driver and DT documentation Valentin Sitdikov
2017-06-13 12:20 ` [PATCH 1/2] dt-bindings: mfd: Add DT bindings documentation for the max7360 mfd driver Valentin Sitdikov
2017-06-13 13:28 ` Vladimir Zapolskiy [this message]
2017-06-13 12:20 ` [PATCH 2/2] mfd: max7360: Add mfd core device driver Valentin Sitdikov
2017-06-13 13:41 ` Vladimir Zapolskiy
-- strict thread matches above, loose matches on Subject: below --
2017-06-02 16:21 [PATCH v3 0/2] dt-bindings: mfd: Add max7360 mfd driver and DT documentation Valentin Sitdikov
2017-06-02 16:21 ` [PATCH 1/2] dt-bindings: mfd: Add DT bindings documentation for the max7360 mfd driver Valentin Sitdikov
2017-06-05 9:23 ` Lee Jones
2017-05-18 8:46 [PATCH v2 0/2] dt-bindings: mfd: Add max7360 mfd driver and DT documentation Valentin Sitdikov
2017-05-18 8:46 ` [PATCH 1/2] dt-bindings: mfd: Add DT bindings documentation for the max7360 mfd driver Valentin Sitdikov
2017-05-22 11:11 ` Lee Jones
2017-05-23 14:24 ` Rob Herring
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=a476aafe-a75f-35bb-bfff-fc73a7f862cc@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=Andrei_Dranitca@mentor.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=valentin_sitdikov@mentor.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®