From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
Loic PALLARDY <loic.pallardy@st.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] dt-bindings: bus: Add firewall bindings
Date: Tue, 28 Apr 2020 13:13:45 +0000 [thread overview]
Message-ID: <13b16e13-690b-ad3f-a800-28c7805cbb96@st.com> (raw)
In-Reply-To: <CACRpkdatGwWyruTLC=+BUtnunvqyxnXAYDhcHqy26oeud8Bs1w@mail.gmail.com>
On 4/28/20 1:24 PM, Linus Walleij wrote:
> Hi Benjamin,
>
> On Mon, Apr 20, 2020 at 3:48 PM Benjamin Gaignard
> <benjamin.gaignard@st.com> wrote:
>> Add schemas for firewall consumer and provider.
>>
>> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
>> +$id: http://devicetree.org/schemas/bus/stm32/firewall-consumer.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Common Bus Firewall consumer binding
>> +
>> +maintainers:
>> + - Benjamin Gaignard <benjamin.gaignard@st.com>
> This really needs a description: to tell what is going on and what
> these firewalls
> are for and how they are supposed to work.
Hi Linus,
Does the following description sound good for you:
Firewall properties provide the possible firewall bus controller
configurations for a device.
Bus firewall controllers are typically used to control if a hardware
block can perform read or write operations on bus.
The contents of the firewall bus configuration properties are defined by
the binding for the individual firewall controller device.
The first configuration 'firewall-0' or the one named 'default' is
applied before probing the device itself.
Regards,
Benjamin
>
> I suppose just a bit of cut'n'paste from the cover letter :D
>
> Otherwise it looks good to me.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2020-04-28 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:47 [PATCH 0/5] STM32 ETZPC bus controller Benjamin Gaignard
2020-04-20 13:47 ` [PATCH 1/5] dt-bindings: bus: Add firewall bindings Benjamin Gaignard
2020-04-28 11:24 ` Linus Walleij
2020-04-28 13:13 ` Benjamin GAIGNARD [this message]
2020-04-28 14:32 ` Linus Walleij
2020-04-20 13:47 ` [PATCH 2/5] bus: stm32: Introduce firewall controller helpers Benjamin Gaignard
2020-04-20 13:47 ` [PATCH 3/5] dt-bindings: bus: Add STM32 ETZPC firewall controller Benjamin Gaignard
2020-04-20 17:58 ` Rob Herring
2020-04-20 13:47 ` [PATCH 4/5] bus: stm32: Add stm32 ETZPC firewall bus controller Benjamin Gaignard
2020-04-20 13:48 ` [PATCH 5/5] ARM: dts: stm32: Use ETZPC firewall bus 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=13b16e13-690b-ad3f-a800-28c7805cbb96@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=loic.pallardy@st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).