[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <5E6274D4-B437-4ABD-B5A7-CCB38F282309@codeaurora.org>
Date: Mon, 28 Mar 2016 17:22:33 -0500
From: Matthew McClintock <mmcclint@...eaurora.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Rob Herring <robh@...nel.org>, andy.gross@...aro.org,
linux-arm-msm@...r.kernel.org,
qca-upstream.external@....qualcomm.com,
linux-watchdog@...r.kernel.org, Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding
On Mar 28, 2016, at 1:15 PM, Guenter Roeck <linux@...ck-us.net> wrote:
>
>>> What SoC(s) is this in. Use SoC specific compatible strings please.
>>
>> So ipq4019 wins the race because we are the first to try to enable watchdog for this block?
>>
>> qcom,kpss-ipq4019 ?
>>
> It is a dedicated watchdog block, isn't it ? "qcom,kpss-ipq4019" would not
> refer to a specific block. Devicetree maintainers may have a better idea,
> but it seems to me that there should be 'wdt' or 'watchdog' in the property
> name.
Sounds fine to me, if no one has any other comments I’ll use this one in the next spin of the patch.
-M
Powered by blists - more mailing lists