From: Mark Brown <broonie@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "robh@kernel.org" <robh@kernel.org>,
"stefano.stabellini@xilinx.com" <stefano.stabellini@xilinx.com>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lkml@metux.net" <lkml@metux.net>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"fabio.estevam@nxp.com" <fabio.estevam@nxp.com>,
Loic PALLARDY <loic.pallardy@st.com>,
"system-dt@lists.openampproject.org"
<system-dt@lists.openampproject.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/7] bus: Introduce firewall controller framework
Date: Wed, 29 Jan 2020 11:17:17 +0000 [thread overview]
Message-ID: <20200129111717.GA3928@sirena.org.uk> (raw)
In-Reply-To: <20200129095240.GA3852081@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 337 bytes --]
On Wed, Jan 29, 2020 at 10:52:40AM +0100, Greg KH wrote:
> It just needs to be part of the bus logic for the specific bus that this
> "firewall" is on. Just like we do the same thing for USB or thunderbolt
> devices. Put this in the bus-specific code please.
I'd expect that this is going to affect at least platform and AMBA
buses.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-29 11:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:37 [PATCH v2 0/7] Introduce bus firewall controller framework Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 1/7] dt-bindings: bus: Add firewall bindings Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 2/7] bus: Introduce firewall controller framework Benjamin Gaignard
2020-01-28 15:52 ` Greg KH
2020-01-28 16:41 ` Benjamin GAIGNARD
2020-01-28 16:57 ` Greg KH
2020-01-28 20:29 ` Benjamin GAIGNARD
2020-01-29 5:49 ` Greg KH
2020-01-29 9:42 ` Linus Walleij
2020-01-29 9:52 ` Greg KH
2020-01-29 11:17 ` Mark Brown [this message]
2020-01-31 8:37 ` Benjamin GAIGNARD
2020-01-31 9:06 ` Greg KH
2020-02-14 16:05 ` Linus Walleij
2020-02-14 21:40 ` Greg KH
2020-02-15 12:41 ` Benjamin GAIGNARD
2020-02-16 7:21 ` Greg KH
2020-01-28 15:38 ` [PATCH v2 3/7] base: Add calls to firewall controller Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 4/7] dt-bindings: bus: Add STM32 ETZPC " Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 5/7] bus: firewall: Add driver for STM32 ETZPC controller Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 6/7] ARM: dts: stm32: Add firewall node for stm32mp157 SoC Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 7/7] ARM: dts: stm32: enable firewall controller node on stm32mp157c-ed1 Benjamin Gaignard
2020-01-28 16:36 ` [PATCH v2 0/7] Introduce bus firewall controller framework Sudeep Holla
2020-01-28 16:46 ` Benjamin GAIGNARD
2020-01-28 17:17 ` Sudeep Holla
2020-01-28 20:06 ` Benjamin GAIGNARD
2020-01-28 22:06 ` Robin Murphy
2020-01-29 13:40 ` Benjamin GAIGNARD
2020-01-31 18:25 ` Robin Murphy
2020-02-03 13:16 ` Benjamin GAIGNARD
2020-01-31 20:51 ` Florian Fainelli
2020-02-03 13:41 ` Benjamin GAIGNARD
2020-01-31 20:48 ` Florian Fainelli
2020-02-02 12:23 ` Mark Brown
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=20200129111717.GA3928@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=loic.pallardy@st.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=sudeep.holla@arm.com \
--cc=system-dt@lists.openampproject.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).