From: Neal Liu <neal.liu@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: Neal Liu <neal.liu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: Re: Add MediaTek MT6873 devapc driver
Date: Wed, 24 Jun 2020 11:51:22 +0800 [thread overview]
Message-ID: <1592970682.14160.6.camel@mtkswgap22> (raw)
In-Reply-To: <20200609173204.GB1107294@bogus>
On Tue, 2020-06-09 at 11:32 -0600, Rob Herring wrote:
> On Tue, Jun 09, 2020 at 06:24:19PM +0800, Neal Liu wrote:
> > These patch series introduce a MediaTek MT6873 devapc driver.
> >
> > MT6873 bus frabric provides TrustZone security support and data
> > protection to prevent slaves from being accessed by unexpected
> > masters.
> > The security violations are logged and sent to the processor for
> > further analysis or countermeasures.
> >
> > Any occurrence of security violation would raise an interrupt, and
> > it will be handled by devapc-mt6873 driver. The violation
> > information is printed in order to find the murderer.
>
> There's also a proposed driver with similar functionality[1]. Come up
> with a common solution.
>
> Rob
>
> [1] https://lore.kernel.org/linux-arm-kernel/20200128153806.7780-1-benjamin.gaignard@st.com/
Actually, Mediatek devapc HW do the similar things. But the real
"firewall" functionality is implemented in TrustZone instread of REE.
This devapc-mt6873 driver is mainly handled the violation.
Bus firewall framework seems not cover this parts.
next prev parent reply other threads:[~2020-06-24 3:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:24 Add MediaTek MT6873 devapc driver Neal Liu
2020-06-09 10:24 ` [PATCH 1/2] dt-bindings: devapc: add bindings for devapc-mt6873 Neal Liu
2020-06-09 17:27 ` Rob Herring
2020-06-09 10:24 ` [PATCH 2/2] soc: mediatek: devapc: add devapc-mt6873 driver Neal Liu
2020-06-09 16:01 ` Chun-Kuang Hu
2020-06-11 9:26 ` Neal Liu
2020-06-11 11:01 ` Chun-Kuang Hu
2020-06-12 3:04 ` Neal Liu
2020-06-12 15:27 ` Chun-Kuang Hu
2020-06-15 2:12 ` Neal Liu
2020-06-12 23:20 ` Chun-Kuang Hu
2020-06-16 6:45 ` Neal Liu
2020-06-14 3:26 ` Chun-Kuang Hu
2020-06-15 2:43 ` Neal Liu
2020-06-15 14:14 ` Chun-Kuang Hu
2020-06-15 14:17 ` Chun-Kuang Hu
2020-06-16 6:09 ` Neal Liu
2020-06-15 15:51 ` Chun-Kuang Hu
2020-06-16 6:19 ` Neal Liu
2020-06-09 17:32 ` Add MediaTek MT6873 devapc driver Rob Herring
2020-06-24 3:51 ` Neal Liu [this message]
2020-06-19 9:41 Neal Liu
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=1592970682.14160.6.camel@mtkswgap22 \
--to=neal.liu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=wsd_upstream@mediatek.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).