[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d029a04-2a37-cbbe-1932-be34d34f6b69@gmail.com>
Date: Wed, 15 Apr 2020 20:48:04 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Julius Werner <jwerner@...omium.org>,
Evan Benn <evanbenn@...omium.org>
Cc: Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Yonghui Yu <yonghui.yu@...ogic.com>,
Leonard Crestez <leonard.crestez@....com>,
Will Deacon <will@...nel.org>,
Xingyu Chen <xingyu.chen@...ogic.com>,
Rob Herring <robh@...nel.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Anson Huang <Anson.Huang@....com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>,
Valentin Schneider <valentin.schneider@....com>,
Guenter Roeck <linux@...ck-us.net>, devicetree@...r.kernel.org,
LINUX-WATCHDOG <linux-watchdog@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Matthias Brugger <matthias.bgg@...il.com>,
"open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Jianxin Pan <jianxin.pan@...ogic.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Vinod Koul <vkoul@...nel.org>, Olof Johansson <olof@...om.net>,
Shawn Guo <shawnguo@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH v2 0/2] Add a watchdog driver that uses ARM Secure Monitor
Calls.
On 4/15/2020 5:56 PM, Julius Werner wrote:
>> Can anyone provide advice about making SMCWD_FUNC_ID a device tree
>> param directly, vs using the compatible to select from a table.
>
> Sounds like most people prefer the way with using different compatible
> strings? (Personally I don't really care either way.)
The PSCI binding itself has provision for specifying function IDs for
different functions, and this seems to be followed by other subsystems
as well like SCMI:
https://www.spinics.net/lists/arm-kernel/msg791270.html
I could easily imagine that a firmware would provide two functions IDs
(one for AArch32, one for AArch64) and that it could change those over
time while not changing the compatible string at all.
--
Florian
Powered by blists - more mailing lists