From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"alexandre.torgue@st.com" <alexandre.torgue@st.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"tomase@xilinx.com" <tomase@xilinx.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"fabio.estevam@nxp.com" <fabio.estevam@nxp.com>,
"loic.pallardy@st.com" <loic.pallardy@st.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
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>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>
Subject: Re: [PATCH v4 0/2] dt-bindings: Intorduce domain-controller
Date: Tue, 26 Jul 2022 09:45:58 +0200 [thread overview]
Message-ID: <CACRpkdaOT=CzyZ5UOXS-CGQJLBeyiE9VrSPy-tZH-1f9NmORqg@mail.gmail.com> (raw)
In-Reply-To: <20220720213221.GA3987398-robh@kernel.org>
On Wed, Jul 20, 2022 at 11:32 PM Rob Herring <robh@kernel.org> wrote:
> On Thu, Jul 07, 2022 at 10:25:08AM +0000, Oleksii Moisieiev wrote:
> > Introducing the domain controller provider/consumenr bindngs which allow to
> > divided system on chip into multiple domains that can be used to select
> > by who hardware blocks could be accessed.
> > A domain could be a cluster of CPUs, a group of hardware blocks or the
> > set of devices, passed-through to the Guest in the virtualized systems.
>
> 'domain' is entirely to ambiguous. We have clock domains, power domains,
> interrupt domains, etc. already. This needs to be specific about what is
> controlled/provided.
Good point.
This should be something like bus-domain, as it controls what the bus
can access.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-07-26 7:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 10:25 [PATCH v4 0/2] dt-bindings: Intorduce domain-controller Oleksii Moisieiev
2022-07-07 10:25 ` [PATCH v4 2/2] dt-bindings: Update scmi node description Oleksii Moisieiev
2022-07-07 10:25 ` [PATCH v4 1/2] dt-bindings: Document common device controller bindings Oleksii Moisieiev
2022-07-11 12:49 ` [PATCH v4 0/2] dt-bindings: Intorduce domain-controller Linus Walleij
2022-07-20 21:32 ` Rob Herring
2022-07-26 7:45 ` Linus Walleij [this message]
2022-08-15 16:37 ` Ahmad Fatoum
2022-08-17 7:09 ` Loic PALLARDY
2022-08-18 9:31 ` Oleksii Moisieiev
2022-08-18 9:05 ` Oleksii Moisieiev
2022-08-30 7:34 ` Ahmad Fatoum
2022-09-06 9:27 ` Oleksii Moisieiev
2022-09-01 9:28 ` Peng Fan
2023-04-04 6:02 ` Peng Fan
2022-11-10 8:57 Oleksii Moisieiev
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='CACRpkdaOT=CzyZ5UOXS-CGQJLBeyiE9VrSPy-tZH-1f9NmORqg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@collabora.com \
--cc=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sstabellini@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tomase@xilinx.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).