From: Shawn Guo <shawnguo@kernel.org>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: jun.nie@linaro.org, wim@iguana.be, linux@roeck-us.net,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, xie.baoyou@zte.com.cn,
chen.chaokai@zte.com.cn, wang.qiang01@zte.com.cn
Subject: Re: [PATCH v2 1/3] dt: bindings: add documentation for zx2967 family watchdog controller
Date: Fri, 20 Jan 2017 09:53:39 +0800 [thread overview]
Message-ID: <20170120015337.GA17299@dragon> (raw)
In-Reply-To: <1484791192-31674-1-git-send-email-baoyou.xie@linaro.org>
On Thu, Jan 19, 2017 at 09:59:50AM +0800, Baoyou Xie wrote:
> This patch adds dt-binding documentation for zx2967 family
> watchdog controller.
>
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
It seems that the comments I put on v1 remains unresolved.
> ---
> .../bindings/watchdog/zte,zx2967-wdt.txt | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
>
> diff --git a/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> new file mode 100644
> index 0000000..6e35ce7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> @@ -0,0 +1,32 @@
> +ZTE zx2967 Watchdog timer
> +
> +Required properties:
> +
> +- compatible : should be one of the following.
> + * zte,zx296718-wdt
> +- reg : Specifies base physical address and size of the registers.
> +- clocks : Pairs of phandle and specifier referencing the controller's clocks.
> +- clock-names: "wdtclk" for the watchdog clock.
> +- resets : Reference to the reset controller controlling the watchdog
> + controller.
> +- reset-names : Must include the following entries:
> + * wdtrst
I do not think clock-names and reset-names are really necessary, since
there is only one clock and reset signal.
> +
> +Optional properties:
> +
> +- wdt-reset-sysctrl : should include following fields.
We need a vendor prefix for vendor specific property.
> + * phandle of aon-sysctrl.
> + * configuare value that be wrote to aon-sysctrl.
s/configuare/configure, s/wrote/written
> + * bit mask, corresponding bits will be affected.
I think we need some comments for bindings users to understand the
different role between "resets" and "wdt-reset-sysctrl". Also, why is
wdt-reset-sysctrl is optional? Does it still work well without this
property.
FYI. I have a similar bindings for TVENC below, which you may find
useful.
http://www.spinics.net/lists/devicetree/msg159668.html
> +
> +Example:
> +
> +wdt_ares: watchdog@1465000 {
What does the suffix "ares" mean? I guess "wdt" is good enough as the
label name.
Shawn
> + compatible = "zte,zx296718-wdt";
> + reg = <0x1465000 0x1000>;
> + clocks = <&topcrm WDT_WCLK>;
> + clock-names = "wdtclk";
> + resets = <&toprst 35>;
> + reset-names = "wdtrst";
> + wdt-reset-sysctrl = <&aon_sysctrl 1 0x115>;
> +};
> --
> 2.7.4
>
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] dt: bindings: add documentation for zx2967 family watchdog controller
Date: Fri, 20 Jan 2017 09:53:39 +0800 [thread overview]
Message-ID: <20170120015337.GA17299@dragon> (raw)
In-Reply-To: <1484791192-31674-1-git-send-email-baoyou.xie@linaro.org>
On Thu, Jan 19, 2017 at 09:59:50AM +0800, Baoyou Xie wrote:
> This patch adds dt-binding documentation for zx2967 family
> watchdog controller.
>
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
It seems that the comments I put on v1 remains unresolved.
> ---
> .../bindings/watchdog/zte,zx2967-wdt.txt | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
>
> diff --git a/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> new file mode 100644
> index 0000000..6e35ce7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> @@ -0,0 +1,32 @@
> +ZTE zx2967 Watchdog timer
> +
> +Required properties:
> +
> +- compatible : should be one of the following.
> + * zte,zx296718-wdt
> +- reg : Specifies base physical address and size of the registers.
> +- clocks : Pairs of phandle and specifier referencing the controller's clocks.
> +- clock-names: "wdtclk" for the watchdog clock.
> +- resets : Reference to the reset controller controlling the watchdog
> + controller.
> +- reset-names : Must include the following entries:
> + * wdtrst
I do not think clock-names and reset-names are really necessary, since
there is only one clock and reset signal.
> +
> +Optional properties:
> +
> +- wdt-reset-sysctrl : should include following fields.
We need a vendor prefix for vendor specific property.
> + * phandle of aon-sysctrl.
> + * configuare value that be wrote to aon-sysctrl.
s/configuare/configure, s/wrote/written
> + * bit mask, corresponding bits will be affected.
I think we need some comments for bindings users to understand the
different role between "resets" and "wdt-reset-sysctrl". Also, why is
wdt-reset-sysctrl is optional? Does it still work well without this
property.
FYI. I have a similar bindings for TVENC below, which you may find
useful.
http://www.spinics.net/lists/devicetree/msg159668.html
> +
> +Example:
> +
> +wdt_ares: watchdog at 1465000 {
What does the suffix "ares" mean? I guess "wdt" is good enough as the
label name.
Shawn
> + compatible = "zte,zx296718-wdt";
> + reg = <0x1465000 0x1000>;
> + clocks = <&topcrm WDT_WCLK>;
> + clock-names = "wdtclk";
> + resets = <&toprst 35>;
> + reset-names = "wdtrst";
> + wdt-reset-sysctrl = <&aon_sysctrl 1 0x115>;
> +};
> --
> 2.7.4
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: jun.nie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org,
linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xie.baoyou-Th6q7B73Y6EnDS1+zs4M5A@public.gmane.org,
chen.chaokai-Th6q7B73Y6EnDS1+zs4M5A@public.gmane.org,
wang.qiang01-Th6q7B73Y6EnDS1+zs4M5A@public.gmane.org
Subject: Re: [PATCH v2 1/3] dt: bindings: add documentation for zx2967 family watchdog controller
Date: Fri, 20 Jan 2017 09:53:39 +0800 [thread overview]
Message-ID: <20170120015337.GA17299@dragon> (raw)
In-Reply-To: <1484791192-31674-1-git-send-email-baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Thu, Jan 19, 2017 at 09:59:50AM +0800, Baoyou Xie wrote:
> This patch adds dt-binding documentation for zx2967 family
> watchdog controller.
>
> Signed-off-by: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
It seems that the comments I put on v1 remains unresolved.
> ---
> .../bindings/watchdog/zte,zx2967-wdt.txt | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
>
> diff --git a/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> new file mode 100644
> index 0000000..6e35ce7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/watchdog/zte,zx2967-wdt.txt
> @@ -0,0 +1,32 @@
> +ZTE zx2967 Watchdog timer
> +
> +Required properties:
> +
> +- compatible : should be one of the following.
> + * zte,zx296718-wdt
> +- reg : Specifies base physical address and size of the registers.
> +- clocks : Pairs of phandle and specifier referencing the controller's clocks.
> +- clock-names: "wdtclk" for the watchdog clock.
> +- resets : Reference to the reset controller controlling the watchdog
> + controller.
> +- reset-names : Must include the following entries:
> + * wdtrst
I do not think clock-names and reset-names are really necessary, since
there is only one clock and reset signal.
> +
> +Optional properties:
> +
> +- wdt-reset-sysctrl : should include following fields.
We need a vendor prefix for vendor specific property.
> + * phandle of aon-sysctrl.
> + * configuare value that be wrote to aon-sysctrl.
s/configuare/configure, s/wrote/written
> + * bit mask, corresponding bits will be affected.
I think we need some comments for bindings users to understand the
different role between "resets" and "wdt-reset-sysctrl". Also, why is
wdt-reset-sysctrl is optional? Does it still work well without this
property.
FYI. I have a similar bindings for TVENC below, which you may find
useful.
http://www.spinics.net/lists/devicetree/msg159668.html
> +
> +Example:
> +
> +wdt_ares: watchdog@1465000 {
What does the suffix "ares" mean? I guess "wdt" is good enough as the
label name.
Shawn
> + compatible = "zte,zx296718-wdt";
> + reg = <0x1465000 0x1000>;
> + clocks = <&topcrm WDT_WCLK>;
> + clock-names = "wdtclk";
> + resets = <&toprst 35>;
> + reset-names = "wdtrst";
> + wdt-reset-sysctrl = <&aon_sysctrl 1 0x115>;
> +};
> --
> 2.7.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-20 1:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 1:59 [PATCH v2 1/3] dt: bindings: add documentation for zx2967 family watchdog controller Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-19 1:59 ` [PATCH v2 2/3] MAINTAINERS: add zx2967 watchdog controller driver to ARM ZTE architecture Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-19 1:59 ` [PATCH v2 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-19 1:59 ` Baoyou Xie
2017-01-20 6:08 ` Shawn Guo
2017-01-20 6:08 ` Shawn Guo
2017-01-20 6:08 ` Shawn Guo
2017-01-20 1:53 ` Shawn Guo [this message]
2017-01-20 1:53 ` [PATCH v2 1/3] dt: bindings: add documentation for zx2967 family watchdog controller Shawn Guo
2017-01-20 1:53 ` Shawn Guo
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=20170120015337.GA17299@dragon \
--to=shawnguo@kernel.org \
--cc=baoyou.xie@linaro.org \
--cc=chen.chaokai@zte.com.cn \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wang.qiang01@zte.com.cn \
--cc=wim@iguana.be \
--cc=xie.baoyou@zte.com.cn \
/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.