[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 12 Dec 2019 21:05:34 +0100
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Xingyu Chen <xingyu.chen@...ogic.com>,
Rob Herring <robh+dt@...nel.org>
Cc: Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
Kevin Hilman <khilman@...libre.com>,
Neil Armstrong <narmstrong@...libre.com>,
Qianggui Song <qianggui.song@...ogic.com>,
devicetree@...r.kernel.org, linux-watchdog@...r.kernel.org,
Jianxin Pan <jianxin.pan@...ogic.com>,
linux-kernel@...r.kernel.org, Jian Hu <jian.hu@...ogic.com>,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org,
Jerome Brunet <jbrunet@...libre.com>
Subject: Re: [PATCH v5 2/4] dt-bindings: watchdog: add new binding for meson
secure watchdog
Hi Xingyu and Rob,
On Thu, Dec 12, 2019 at 1:20 PM Xingyu Chen <xingyu.chen@...ogic.com> wrote:
[...]
> +examples:
> + - |
> + watchdog {
> + compatible = "amlogic,meson-sec-wdt";
> + timeout-sec = <60>;
> + };
in v3 of this patch Rob commented that there shouldn't be an OF node
if there are no additional properties
with timeout-sec there's now an additional property so my
understanding is that it's fine to have an OF node
what I don't understand yet is where this node should be placed.
is it supposed to be a child node of the secure monitor node (for
which we already have a binding here:
Documentation/devicetree/bindings/firmware/meson/meson_sm.txt) or
where else would we place it inside the .dts?
Martin
[0] https://patchwork.kernel.org/patch/11211399/
Powered by blists - more mailing lists