From: Sudeep Holla <sudeep.holla@arm.com>
To: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property description for SCMI
Date: Wed, 16 Mar 2022 18:59:07 +0000 [thread overview]
Message-ID: <YjIzeyNoWhVAY5HK@bogus> (raw)
In-Reply-To: <20220316164619.GA3489934@EPUAKYIW015D>
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.
--
Regards,
Sudeep
next prev parent reply other threads:[~2022-03-16 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 8:17 [PATCH v2 0/2] dt-bindings: xen: Add xen,scmi-devid parameter for Oleksii Moisieiev
2022-03-07 8:17 ` [PATCH v2 1/2] dt-bindings: Add vendor prefix for Xen hypervisor Oleksii Moisieiev
2022-03-07 23:30 ` Stefano Stabellini
2022-03-08 20:14 ` Rob Herring
2022-03-10 11:38 ` Oleksii Moisieiev
2022-03-10 17:20 ` Stefano Stabellini
2022-03-07 8:17 ` [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property description for SCMI Oleksii Moisieiev
2022-03-07 23:38 ` Stefano Stabellini
2022-03-08 20:13 ` Rob Herring
2022-03-16 16:46 ` Oleksii Moisieiev
2022-03-16 18:59 ` Sudeep Holla [this message]
2022-03-18 23:53 ` Stefano Stabellini
2022-03-22 11:12 ` Sudeep Holla
2022-03-22 19:21 ` Oleksii Moisieiev
2022-03-23 10:54 ` Sudeep Holla
2022-03-28 8:52 ` Oleksii Moisieiev
2022-04-12 22:42 ` Stefano Stabellini
2022-04-22 17:59 ` Sudeep Holla
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=YjIzeyNoWhVAY5HK@bogus \
--to=sudeep.holla@arm.com \
--cc=Oleksii_Moisieiev@epam.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sstabellini@kernel.org \
/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.