linux-kernel - Re: [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property description for SCMI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 18 Mar 2022 16:53:20 -0700 (PDT)
From:   Stefano Stabellini <sstabellini@...nel.org>
To:     Sudeep Holla <sudeep.holla@....com>
cc:     Oleksii Moisieiev <Oleksii_Moisieiev@...m.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Rob Herring <robh@...nel.org>,
        Cristian Marussi <cristian.marussi@....com>,
        Stefano Stabellini <sstabellini@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property
 description for SCMI

On Wed, 16 Mar 2022, Sudeep Holla wrote:
> On Wed, Mar 16, 2022 at 04:46:20PM +0000, Oleksii Moisieiev wrote:
> > 
> > > + The reason I want to keep it xen specific at the moment as we had some
> > > plan to extended the device-id usage in the spec which hasn't progressed
> > > a bit(I must admit that before you ask), and this addition should not be
> > > obstruct that future development. If we align with what we define xen
> > > specific as part of $subject work, we can always define generic binding
> > > in the future and slowly make the other obsolete over the time.
> > 
> > IIUC you have some plans to provide device_id support to the device-tree
> > bindings from your side. Maybe we can discuss some of your plans here
> > and we can come up with the generic device-id binding?
> > So I will have something to base on in Xen.
> > 
> 
> Sorry if I wasn't clear in earlier emails. What I mentioned was that I would
> like to reserve the generic namespace(i.e. just device-id) for generic SCMI
> usage. Since we haven't defined it clearly in the spec, I don't want to
> introduce the generic definition and binding now.
> 
> As mentioned earlier, though Xen definition and generic once may be exactly
> same, but we won't know until then. So keep the xen usage and namespace
> separate for now to avoid any future conflicts.


Hi Sudeep,

I thought the specification already covered this device id, it simply
delegated the description of it to Device Tree or ACPI, which is common
behavior in ARM specs. What is missing in the SCMI spec from your point
of view?



Or would you like this scmi-devid Device Tree property (or similar) to
be described in the SCMI specification itself?

Typically Device Tree and ACPI descriptions are delegated to Device Tree
and ACPI respectively. Also specification updates are typically slow
(for good reason.) We might be waiting for a long time. It is usually
not a matter of days.