From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
javier@osg.samsung.com, mturquette@baylibre.com,
robh+dt@kernel.org, linux@armlinux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: [PATCH 2/5] clk: Combine DT binding doc for max77686 and max77802
Date: Thu, 16 Jun 2016 11:44:32 +0200 [thread overview]
Message-ID: <57627500.30209@samsung.com> (raw)
In-Reply-To: <1466000018-16784-3-git-send-email-ldewangan@nvidia.com>
On 06/15/2016 04:13 PM, Laxman Dewangan wrote:
> The clock driver for Maxim PMICs max77686 and max77802 are
> combined into single file to extend the support for same clock
> IP for different PMICs.
>
> Remove the separate DT binding document file for maxim,max77802 and
> move all information to maxim,max77686 DT binding document.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> CC: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> CC: Javier Martinez Canillas <javier@dowhile0.org>
> ---
> .../devicetree/bindings/clock/maxim,max77686.txt | 78 ++++++++++++++++------
> .../devicetree/bindings/clock/maxim,max77802.txt | 44 ------------
> 2 files changed, 58 insertions(+), 64 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/maxim,max77802.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/maxim,max77686.txt b/Documentation/devicetree/bindings/clock/maxim,max77686.txt
> index 9c40739..354e5ab 100644
> --- a/Documentation/devicetree/bindings/clock/maxim,max77686.txt
> +++ b/Documentation/devicetree/bindings/clock/maxim,max77686.txt
> @@ -1,11 +1,15 @@
> -Binding for Maxim MAX77686 32k clock generator block
> +Binding for Maxim MAX77686/MAX77802 32k clock generator block
>
> -This is a part of device tree bindings of MAX77686 multi-function device.
> -More information can be found in bindings/mfd/max77686.txt file.
> +This is a part of device tree bindings of MAX77686/MAX77802 multi-function
> +device. More information can be found in bindings/mfd/max77686.txt file for
> +MAX77686 and bindings/mfd/max77802.txt for MAX77802.
>
> The MAX77686 contains three 32.768khz clock outputs that can be controlled
> (gated/ungated) over I2C.
>
> +The MAX77802 contains two 32.768khz clock outputs that can be controlled
> +(gated/ungated) over I2C.
> +
> Following properties should be presend in main device node of the MFD chip.
>
> Required properties:
> @@ -21,26 +25,60 @@ to specify the clock which they consume. Following indices are allowed:
> - 1: 32khz_cp clock,
> - 2: 32khz_pmic clock.
>
> +For MAX77802, 32khz_pmic is not valid.
It is easier to find for which device which ID is allowed, so maybe:
- 1: 32khz_cp clock (max77686, max77802),
- 2: 32khz_pmic clock. (max77686)
> +
> Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77686.h
> -header and can be used in device tree sources.
> +header for MAX77686 and dt-bindings/clock/maxim,max77802.h for MAX77802 and can
> +be used in device tree sources.
> +
> +Example:
> +
> +1. With MAX77686:
> +
> +#include <dt-bindings/clock/maxim,max77686.h>
> +:::
I am not sure what the ":::" means here...
Best regards,
Krzysztof
> +
> + Node of the MFD chip
> + max77686: max77686@09 {
> + compatible = "maxim,max77686";
> + interrupt-parent = <&wakeup_eint>;
> + interrupts = <26 0>;
> + reg = <0x09>;
> + #clock-cells = <1>;
> +
> + /* ... */
> + };
> +
> + Clock consumer node
> +
> + foo@0 {
> + compatible = "bar,foo";
> + /* ... */
> + clock-names = "my-clock";
> + clocks = <&max77686 MAX77686_CLK_PMIC>;
> + };
> +
> +2. With MAX77802:
>
> -Example: Node of the MFD chip
> +#include <dt-bindings/clock/maxim,max77802.h>
> +:::
>
> - max77686: max77686@09 {
> - compatible = "maxim,max77686";
> - interrupt-parent = <&wakeup_eint>;
> - interrupts = <26 0>;
> - reg = <0x09>;
> - #clock-cells = <1>;
> + Node of the MFD chip
> + max77802: max77802@09 {
> + compatible = "maxim,max77802";
> + interrupt-parent = <&wakeup_eint>;
> + interrupts = <26 0>;
> + reg = <0x09>;
> + #clock-cells = <1>;
>
> - /* ... */
> - };
> + /* ... */
> + };
>
> -Example: Clock consumer node
> + Clock consumer node
>
> - foo@0 {
> - compatible = "bar,foo";
> - /* ... */
> - clock-names = "my-clock";
> - clocks = <&max77686 MAX77686_CLK_PMIC>;
> - };
> + foo@0 {
> + compatible = "bar,foo";
> + /* ... */
> + clock-names = "my-clock";
> + clocks = <&max77802 MAX77802_CLK_32K_AP>;
> + };
> diff --git a/Documentation/devicetree/bindings/clock/maxim,max77802.txt b/Documentation/devicetree/bindings/clock/maxim,max77802.txt
> deleted file mode 100644
> index c6dc783..0000000
> --- a/Documentation/devicetree/bindings/clock/maxim,max77802.txt
> +++ /dev/null
> @@ -1,44 +0,0 @@
> -Binding for Maxim MAX77802 32k clock generator block
> -
> -This is a part of device tree bindings of MAX77802 multi-function device.
> -More information can be found in bindings/mfd/max77802.txt file.
> -
> -The MAX77802 contains two 32.768khz clock outputs that can be controlled
> -(gated/ungated) over I2C.
> -
> -Following properties should be present in main device node of the MFD chip.
> -
> -Required properties:
> -- #clock-cells: From common clock binding; shall be set to 1.
> -
> -Optional properties:
> -- clock-output-names: From common clock binding.
> -
> -Each clock is assigned an identifier and client nodes can use this identifier
> -to specify the clock which they consume. Following indices are allowed:
> - - 0: 32khz_ap clock,
> - - 1: 32khz_cp clock.
> -
> -Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77802.h
> -header and can be used in device tree sources.
> -
> -Example: Node of the MFD chip
> -
> - max77802: max77802@09 {
> - compatible = "maxim,max77802";
> - interrupt-parent = <&wakeup_eint>;
> - interrupts = <26 0>;
> - reg = <0x09>;
> - #clock-cells = <1>;
> -
> - /* ... */
> - };
> -
> -Example: Clock consumer node
> -
> - foo@0 {
> - compatible = "bar,foo";
> - /* ... */
> - clock-names = "my-clock";
> - clocks = <&max77802 MAX77802_CLK_32K_AP>;
> - };
>
next prev parent reply other threads:[~2016-06-16 9:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 14:13 [PATCH 0/5] clk: Combine MAX77686 and MAX77802 driver and extend for MAX77620 Laxman Dewangan
2016-06-15 14:13 ` [PATCH 1/5] clk: max77686: Combine Maxim max77686 and max77802 driver Laxman Dewangan
2016-06-15 15:12 ` Javier Martinez Canillas
2016-06-15 15:35 ` kbuild test robot
2016-06-15 15:35 ` [PATCH] clk: max77686: fix semicolon.cocci warnings kbuild test robot
2016-06-16 9:31 ` [PATCH 1/5] clk: max77686: Combine Maxim max77686 and max77802 driver Krzysztof Kozlowski
2016-06-16 13:02 ` Krzysztof Kozlowski
2016-06-15 14:13 ` [PATCH 2/5] clk: Combine DT binding doc for max77686 and max77802 Laxman Dewangan
2016-06-15 15:19 ` Javier Martinez Canillas
2016-06-16 9:34 ` Krzysztof Kozlowski
2016-06-16 9:44 ` Krzysztof Kozlowski [this message]
2016-06-15 14:13 ` [PATCH 3/5] clk: max77686: Add DT binding details for PMIC MAX77620 Laxman Dewangan
2016-06-15 15:24 ` Javier Martinez Canillas
2016-06-16 9:49 ` Krzysztof Kozlowski
2016-06-15 14:13 ` [PATCH 4/5] clk: max77686: Add support for MAX77620 clocks Laxman Dewangan
2016-06-15 15:27 ` Javier Martinez Canillas
2016-06-16 9:54 ` Krzysztof Kozlowski
2016-06-16 9:52 ` Laxman Dewangan
2016-06-16 10:11 ` Krzysztof Kozlowski
2016-06-16 13:02 ` Krzysztof Kozlowski
2016-06-15 14:13 ` [PATCH 5/5] ARM: config: Get rid of config COMMON_CLK_MAX77802 Laxman Dewangan
2016-06-15 15:39 ` Javier Martinez Canillas
2016-06-16 12:25 ` Krzysztof Kozlowski
2016-06-16 13:06 ` Javier Martinez Canillas
2016-06-16 13:08 ` Laxman Dewangan
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=57627500.30209@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@dowhile0.org \
--cc=javier@osg.samsung.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).