All of lore.kernel.org
 help / color / mirror / Atom feed
From: wmb@firmworks.com (Mitch Bradley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 7/7] Document: devicetree: add OF documents for arch-mmp
Date: Mon, 02 Apr 2012 13:21:53 -1000	[thread overview]
Message-ID: <4F7A3491.2060003@firmworks.com> (raw)
In-Reply-To: <1330950111-30797-8-git-send-email-haojian.zhuang@marvell.com>

There are some inconsistencies in this patch as indicated in-line below:


On 3/5/2012 2:21 AM, Haojian Zhuang wrote:
> Add OF support in Document/devicetree directory.
>
> Signed-off-by: Haojian Zhuang<haojian.zhuang@marvell.com>
> ---
>   Documentation/devicetree/bindings/arm/mrvl.txt     |    6 +++
>   .../devicetree/bindings/gpio/mrvl-gpio.txt         |   23 ++++++++++++
>   Documentation/devicetree/bindings/i2c/mrvl-i2c.txt |   37 ++++++++++++++++++++
>   .../devicetree/bindings/rtc/sa1100-rtc.txt         |   17 +++++++++
>   .../devicetree/bindings/serial/mrvl-serial.txt     |    4 ++
>   5 files changed, 87 insertions(+), 0 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/arm/mrvl.txt
>   create mode 100644 Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
>   create mode 100644 Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
>   create mode 100644 Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
>   create mode 100644 Documentation/devicetree/bindings/serial/mrvl-serial.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/mrvl.txt b/Documentation/devicetree/bindings/arm/mrvl.txt
> new file mode 100644
> index 0000000..d8de933
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/mrvl.txt
> @@ -0,0 +1,6 @@
> +Marvell Platforms Device Tree Bindings
> +----------------------------------------------------
> +
> +PXA168 Aspenite Board
> +Required root node properties:
> +	- compatible = "mrvl,pxa168-aspenite", "mrvl,pxa168";
> diff --git a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
> new file mode 100644
> index 0000000..1e34cfe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
> @@ -0,0 +1,23 @@
> +* Marvell PXA GPIO controller
> +
> +Required properties:
> +- compatible : Should be "mrvl,pxa-gpio" or "mrvl,mmp-gpio"
> +- reg : Address and length of the register set for the device
> +- interrupts : Should be the port interrupt shared by all gpio pins, if

This sentence is incomplete.  Maybe the "one number." two lines below is 
part of this sentence?  If so, I'm not sure I understand the meaning.  
Did you mean to say "If a single interrupt is shared by all GPIO pins, 
the value is a single integer." ?  What is the meaning if there are 
multiple integers in the value?
>
> +- interrupt-name : Should be the name of irq resource.

"The name" implies that there is a single value, but the example below 
shows multiple values.

>
> +  one number.

See above.

>
> +- gpio-controller : Marks the device node as a gpio controller.
> +- #gpio-cells : Should be one.  It is the pin number.
> +
> +Example:
> +
> +	gpio: gpio at d4019000 {
> +		compatible = "mrvl,mmp-gpio", "mrvl,pxa-gpio";

The text above says "mrvl,pxa-gpio" *or* "mrvl,mmp-gpio", but the 
example has both.  If both are necessary, the word "and" would be more 
appropriate.

What is the point of having both names in the device tree?  If the Linux 
driver is known to support the MMP version of the GPIO hardware, there 
is no need for a "fallback" to the PXA version.   Fallback names are 
rarely needed for Linux, because new customized Linux kernels are easy 
to develop for new hardware.  Fallback names were intended for 
commercial operating systems where the hardware vendor must work with an 
OS version that is already in the field.

>
> +		reg =<0xd4019000 0x1000>;
> +		interrupts =<49>,<17>,<18>;
> +		interrupt-name = "gpio_mux", "gpio0", "gpio1";
> +		gpio-controller;
> +		#gpio-cells =<1>;
> +		interrupt-controller;
> +		#interrupt-cells =<1>;

The text above does not mention "interrupt-controller" and 
"#interrupt-cells" properties for this node.

>
> +      };
> diff --git a/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt b/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
> new file mode 100644
> index 0000000..071eb3c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
> @@ -0,0 +1,37 @@
> +* I2C
> +
> +Required properties :
> +
> + - reg : Offset and length of the register set for the device
> + - compatible : should be "mrvl,mmp-twsi" where CHIP is the name of a

"CHIP" makes no sense in this sentence.  I presume that you meant to 
refer to a template name that contains "CHIP", but "mrvl,mmp-twsi" does 
not contain "CHIP".

>
> +   compatible processor, e.g. pxa168, pxa910, mmp2, mmp3.
> +   For the pxa2xx/pxa3xx, an additional node "mrvl,pxa-i2c" is required
> +   as shown in the example below.
> +
> +Recommended properties :
> +
> + - interrupts :<a b>  where a is the interrupt number and b is a
> +   field that represents an encoding of the sense and level
> +   information for the interrupt.  This should be encoded based on
> +   the information in section 2) depending on the type of interrupt
> +   controller you have.

Was this text copied from somewhere else and not edited?  It doesn't 
make sense here, and the example below has only a single number, so <a 
b> cannot be correct.

>
> + - interrupt-parent : the phandle for the interrupt controller that
> +   services interrupts for this device.

There is no interrupt-parent property in the example below.  I presume 
you mean to use the default where the device tree parent node is the 
interrupt parent.  If so, you should say that.
>
> + - mrvl,i2c-polling : Disable interrupt of i2c controller. Polling
> +   status register of i2c controller instead.
> + - mrvl,i2c-fast-mode : Enable fast mode of i2c controller.
> +
> +Examples:
> +	twsi1: i2c at d4011000 {
> +		compatible = "mrvl,mmp-twsi", "mrvl,pxa-i2c";

No need for two different values, as discussed above.

>
> +		reg =<0xd4011000 0x1000>;
> +		interrupts =<7>;
> +		mrvl,i2c-fast-mode;
> +	};
> +	
> +	twsi2: i2c at d4025000 {
> +		compatible = "mrvl,mmp-twsi", "mrvl,pxa-i2c";

No need for two different values, as discussed above.

>
> +		reg =<0xd4025000 0x1000>;
> +		interrupts =<58>;
> +	};
> +
> diff --git a/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt b/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
> new file mode 100644
> index 0000000..0cda19a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
> @@ -0,0 +1,17 @@
> +* Marvell Real Time Clock controller
> +
> +Required properties:
> +- compatible: should be "mrvl,sa1100-rtc"
> +- reg: physical base address of the controller and length of memory mapped
> +  region.
> +- interrupts: Should be two. The first interrupt number is the rtc alarm
> +  interrupt and the second interrupt number is the rtc hz interrupt.
> +- interrupt-names: Assign name of irq resource.
> +
> +Example:
> +	rtc: rtc at d4010000 {
> +		compatible = "mrvl,mmp-rtc";
> +		reg =<0xd4010000 0x1000>;
> +		interrupts =<5>,<6>;
> +		interrupt-name = "rtc 1Hz", "rtc alarm";
> +	};
> diff --git a/Documentation/devicetree/bindings/serial/mrvl-serial.txt b/Documentation/devicetree/bindings/serial/mrvl-serial.txt
> new file mode 100644
> index 0000000..d744340
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/mrvl-serial.txt
> @@ -0,0 +1,4 @@
> +PXA UART controller
> +
> +Required properties:
> +- compatible : should be "mrvl,mmp-uart" or "mrvl,pxa-uart".

WARNING: multiple messages have this Message-ID (diff)
From: Mitch Bradley <wmb@firmworks.com>
To: Haojian Zhuang <haojian.zhuang@marvell.com>
Cc: eric.y.miao@gmail.com, arnd@arndb.de,
	devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
	linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 7/7] Document: devicetree: add OF documents for arch-mmp
Date: Mon, 02 Apr 2012 13:21:53 -1000	[thread overview]
Message-ID: <4F7A3491.2060003@firmworks.com> (raw)
In-Reply-To: <1330950111-30797-8-git-send-email-haojian.zhuang@marvell.com>

There are some inconsistencies in this patch as indicated in-line below:


On 3/5/2012 2:21 AM, Haojian Zhuang wrote:
> Add OF support in Document/devicetree directory.
>
> Signed-off-by: Haojian Zhuang<haojian.zhuang@marvell.com>
> ---
>   Documentation/devicetree/bindings/arm/mrvl.txt     |    6 +++
>   .../devicetree/bindings/gpio/mrvl-gpio.txt         |   23 ++++++++++++
>   Documentation/devicetree/bindings/i2c/mrvl-i2c.txt |   37 ++++++++++++++++++++
>   .../devicetree/bindings/rtc/sa1100-rtc.txt         |   17 +++++++++
>   .../devicetree/bindings/serial/mrvl-serial.txt     |    4 ++
>   5 files changed, 87 insertions(+), 0 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/arm/mrvl.txt
>   create mode 100644 Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
>   create mode 100644 Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
>   create mode 100644 Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
>   create mode 100644 Documentation/devicetree/bindings/serial/mrvl-serial.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/mrvl.txt b/Documentation/devicetree/bindings/arm/mrvl.txt
> new file mode 100644
> index 0000000..d8de933
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/mrvl.txt
> @@ -0,0 +1,6 @@
> +Marvell Platforms Device Tree Bindings
> +----------------------------------------------------
> +
> +PXA168 Aspenite Board
> +Required root node properties:
> +	- compatible = "mrvl,pxa168-aspenite", "mrvl,pxa168";
> diff --git a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
> new file mode 100644
> index 0000000..1e34cfe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
> @@ -0,0 +1,23 @@
> +* Marvell PXA GPIO controller
> +
> +Required properties:
> +- compatible : Should be "mrvl,pxa-gpio" or "mrvl,mmp-gpio"
> +- reg : Address and length of the register set for the device
> +- interrupts : Should be the port interrupt shared by all gpio pins, if

This sentence is incomplete.  Maybe the "one number." two lines below is 
part of this sentence?  If so, I'm not sure I understand the meaning.  
Did you mean to say "If a single interrupt is shared by all GPIO pins, 
the value is a single integer." ?  What is the meaning if there are 
multiple integers in the value?
>
> +- interrupt-name : Should be the name of irq resource.

"The name" implies that there is a single value, but the example below 
shows multiple values.

>
> +  one number.

See above.

>
> +- gpio-controller : Marks the device node as a gpio controller.
> +- #gpio-cells : Should be one.  It is the pin number.
> +
> +Example:
> +
> +	gpio: gpio@d4019000 {
> +		compatible = "mrvl,mmp-gpio", "mrvl,pxa-gpio";

The text above says "mrvl,pxa-gpio" *or* "mrvl,mmp-gpio", but the 
example has both.  If both are necessary, the word "and" would be more 
appropriate.

What is the point of having both names in the device tree?  If the Linux 
driver is known to support the MMP version of the GPIO hardware, there 
is no need for a "fallback" to the PXA version.   Fallback names are 
rarely needed for Linux, because new customized Linux kernels are easy 
to develop for new hardware.  Fallback names were intended for 
commercial operating systems where the hardware vendor must work with an 
OS version that is already in the field.

>
> +		reg =<0xd4019000 0x1000>;
> +		interrupts =<49>,<17>,<18>;
> +		interrupt-name = "gpio_mux", "gpio0", "gpio1";
> +		gpio-controller;
> +		#gpio-cells =<1>;
> +		interrupt-controller;
> +		#interrupt-cells =<1>;

The text above does not mention "interrupt-controller" and 
"#interrupt-cells" properties for this node.

>
> +      };
> diff --git a/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt b/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
> new file mode 100644
> index 0000000..071eb3c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/mrvl-i2c.txt
> @@ -0,0 +1,37 @@
> +* I2C
> +
> +Required properties :
> +
> + - reg : Offset and length of the register set for the device
> + - compatible : should be "mrvl,mmp-twsi" where CHIP is the name of a

"CHIP" makes no sense in this sentence.  I presume that you meant to 
refer to a template name that contains "CHIP", but "mrvl,mmp-twsi" does 
not contain "CHIP".

>
> +   compatible processor, e.g. pxa168, pxa910, mmp2, mmp3.
> +   For the pxa2xx/pxa3xx, an additional node "mrvl,pxa-i2c" is required
> +   as shown in the example below.
> +
> +Recommended properties :
> +
> + - interrupts :<a b>  where a is the interrupt number and b is a
> +   field that represents an encoding of the sense and level
> +   information for the interrupt.  This should be encoded based on
> +   the information in section 2) depending on the type of interrupt
> +   controller you have.

Was this text copied from somewhere else and not edited?  It doesn't 
make sense here, and the example below has only a single number, so <a 
b> cannot be correct.

>
> + - interrupt-parent : the phandle for the interrupt controller that
> +   services interrupts for this device.

There is no interrupt-parent property in the example below.  I presume 
you mean to use the default where the device tree parent node is the 
interrupt parent.  If so, you should say that.
>
> + - mrvl,i2c-polling : Disable interrupt of i2c controller. Polling
> +   status register of i2c controller instead.
> + - mrvl,i2c-fast-mode : Enable fast mode of i2c controller.
> +
> +Examples:
> +	twsi1: i2c@d4011000 {
> +		compatible = "mrvl,mmp-twsi", "mrvl,pxa-i2c";

No need for two different values, as discussed above.

>
> +		reg =<0xd4011000 0x1000>;
> +		interrupts =<7>;
> +		mrvl,i2c-fast-mode;
> +	};
> +	
> +	twsi2: i2c@d4025000 {
> +		compatible = "mrvl,mmp-twsi", "mrvl,pxa-i2c";

No need for two different values, as discussed above.

>
> +		reg =<0xd4025000 0x1000>;
> +		interrupts =<58>;
> +	};
> +
> diff --git a/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt b/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
> new file mode 100644
> index 0000000..0cda19a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/sa1100-rtc.txt
> @@ -0,0 +1,17 @@
> +* Marvell Real Time Clock controller
> +
> +Required properties:
> +- compatible: should be "mrvl,sa1100-rtc"
> +- reg: physical base address of the controller and length of memory mapped
> +  region.
> +- interrupts: Should be two. The first interrupt number is the rtc alarm
> +  interrupt and the second interrupt number is the rtc hz interrupt.
> +- interrupt-names: Assign name of irq resource.
> +
> +Example:
> +	rtc: rtc@d4010000 {
> +		compatible = "mrvl,mmp-rtc";
> +		reg =<0xd4010000 0x1000>;
> +		interrupts =<5>,<6>;
> +		interrupt-name = "rtc 1Hz", "rtc alarm";
> +	};
> diff --git a/Documentation/devicetree/bindings/serial/mrvl-serial.txt b/Documentation/devicetree/bindings/serial/mrvl-serial.txt
> new file mode 100644
> index 0000000..d744340
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/mrvl-serial.txt
> @@ -0,0 +1,4 @@
> +PXA UART controller
> +
> +Required properties:
> +- compatible : should be "mrvl,mmp-uart" or "mrvl,pxa-uart".

  parent reply	other threads:[~2012-04-02 23:21 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 12:21 [PATCH v2 0/7] ARM: mmp: support OF on pxa168 Haojian Zhuang
2012-03-05 12:21 ` Haojian Zhuang
2012-03-05 12:21 ` [PATCH v2 1/7] serial: pxa: add OF support Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 12:55   ` Arnd Bergmann
2012-03-05 12:55     ` Arnd Bergmann
2012-03-05 14:03     ` Haojian Zhuang
2012-03-05 14:03       ` Haojian Zhuang
2012-03-06  2:42     ` [PATCH v3 " Haojian Zhuang
2012-03-06  2:42       ` Haojian Zhuang
2012-03-06 15:02       ` Arnd Bergmann
2012-03-06 15:02         ` Arnd Bergmann
2012-03-06 15:04         ` Haojian Zhuang
2012-03-06 15:04           ` Haojian Zhuang
2012-03-07  1:42         ` [PATCH v3 1/6] " Haojian Zhuang
2012-03-07  1:42           ` Haojian Zhuang
2012-03-07  7:58           ` Arnd Bergmann
2012-03-07  7:58             ` Arnd Bergmann
2012-03-09 15:24   ` [PATCH v2 1/7] " Grant Likely
2012-03-09 15:24     ` Grant Likely
2012-04-03 15:45   ` Grant Likely
2012-04-03 15:45     ` Grant Likely
2012-03-05 12:21 ` [PATCH v2 2/7] rtc: sa1100: " Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:41   ` Arnd Bergmann
2012-03-05 14:41     ` Arnd Bergmann
2012-03-05 12:21 ` [PATCH v2 3/7] i2c: pxa: " Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:41   ` Arnd Bergmann
2012-03-05 14:41     ` Arnd Bergmann
2012-03-05 12:21 ` [PATCH v2 4/7] ARM: mmp: enable rtc clk in pxa168 Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:38   ` Arnd Bergmann
2012-03-05 14:38     ` Arnd Bergmann
2012-03-05 12:21 ` [PATCH v2 5/7] ARM: mmp: append OF support on pxa168 Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:37   ` Arnd Bergmann
2012-03-05 14:37     ` Arnd Bergmann
2012-04-09  1:36   ` Chris Ball
2012-04-09  1:36     ` Chris Ball
2012-04-09  1:46     ` Haojian Zhuang
2012-04-09  1:46       ` Haojian Zhuang
2012-04-09  1:51       ` Chris Ball
2012-04-09  1:51         ` Chris Ball
2012-04-09  2:04         ` Haojian Zhuang
2012-04-09  2:04           ` Haojian Zhuang
2012-04-09  1:43   ` Chris Ball
2012-04-09  1:43     ` Chris Ball
2012-04-09  1:47     ` Haojian Zhuang
2012-04-09  1:47       ` Haojian Zhuang
2012-03-05 12:21 ` [PATCH v2 6/7] ARM: dts: append DTS file of pxa168 Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:35   ` Arnd Bergmann
2012-03-05 14:35     ` Arnd Bergmann
2012-03-05 12:21 ` [PATCH v2 7/7] Document: devicetree: add OF documents for arch-mmp Haojian Zhuang
2012-03-05 12:21   ` Haojian Zhuang
2012-03-05 14:46   ` Arnd Bergmann
2012-03-05 14:46     ` Arnd Bergmann
2012-03-05 15:07     ` Rob Herring
2012-03-05 15:07       ` Rob Herring
2012-03-05 15:08     ` Cousson, Benoit
2012-03-05 15:08       ` Cousson, Benoit
2012-04-02 23:21   ` Mitch Bradley [this message]
2012-04-02 23:21     ` Mitch Bradley

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=4F7A3491.2060003@firmworks.com \
    --to=wmb@firmworks.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.