From: Mark Brown <broonie@kernel.org>
To: Benjamin GAIGNARD <benjamin.gaignard@st.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Loic PALLARDY <loic.pallardy@st.com>,
"benjamin.gaignard@linaro.org" <benjamin.gaignard@linaro.org>
Subject: Re: [RFC 1/7] devicetree: bindings: Document domains controller bindings
Date: Thu, 17 Jan 2019 16:22:44 +0000 [thread overview]
Message-ID: <20190117162244.GC7003@sirena.org.uk> (raw)
In-Reply-To: <caeb0919-20ab-a27e-f2c1-10f97d868451@st.com>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
On Thu, Jan 17, 2019 at 01:20:45PM +0000, Benjamin GAIGNARD wrote:
> On 1/16/19 6:30 PM, Mark Brown wrote:
> > I suspect this is going to need a few more words about what a Domains
> > Controller is.
> Does the description of the framework in the cover letter looks better
> for you ?
Yes, that looks reasonable to me.
> I'm not comfortable to put it in bindings file but maybe I'm wrong.
I can't see how someone will understand the binding document as a
standalone document - it's not like domains controllers are a widely
understood concept in the industry.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-17 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:41 [RFC 0/7] Introduce bus domains controller framework Benjamin Gaignard
2019-01-14 14:41 ` [RFC 1/7] devicetree: bindings: Document domains controller bindings Benjamin Gaignard
2019-01-16 17:30 ` Mark Brown
2019-01-17 13:20 ` Benjamin GAIGNARD
2019-01-17 16:22 ` Mark Brown [this message]
2019-01-14 14:41 ` [RFC 2/7] domainsctrl: Introduce domains controller framework Benjamin Gaignard
2019-01-17 17:27 ` Mark Brown
2019-01-18 9:26 ` Benjamin GAIGNARD
2019-01-21 12:56 ` Mark Brown
2019-01-14 14:41 ` [RFC 3/7] base: Add calls to domains controller Benjamin Gaignard
2019-01-14 14:41 ` [RFC 4/7] devicetree: bindings: domainsctrl: Add STM32 ETZPC bindings Benjamin Gaignard
2019-01-14 14:42 ` [RFC 5/7] bus: domainsctrl: Add driver for STM32 ETZPC controller Benjamin Gaignard
2019-01-14 14:42 ` [RFC 6/7] ARM: dts: stm32: Add domainsctrl node for stm32mp157 SoC Benjamin Gaignard
2019-01-14 14:42 ` [RFC 7/7] ARM: dts: stm32: enable domains controller node on stm32mp157c-ed1 Benjamin Gaignard
2019-01-17 17:57 ` [RFC 0/7] Introduce bus domains controller framework Rob Herring
2019-01-18 9:56 ` Benjamin GAIGNARD
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=20190117162244.GC7003@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®