From: Neal Liu <neal.liu@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
wsd_upstream <wsd_upstream@mediatek.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
Neal Liu <neal.liu@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v8] Add MediaTek MT6779 devapc driver
Date: Thu, 15 Oct 2020 11:24:36 +0800 [thread overview]
Message-ID: <1602732276.13734.1.camel@mtkswgap22> (raw)
In-Reply-To: <1602732039-12179-1-git-send-email-neal.liu@mediatek.com>
add subject
On Thu, 2020-10-15 at 11:20 +0800, Neal Liu wrote:
> These patch series introduce a MediaTek MT6779 devapc driver.
>
> MediaTek bus fabric provides TrustZone security support and data protection to prevent slaves from being accessed by unexpected masters.
> The security violation is 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 mtk-devapc driver.
> The violation information is printed in order to find the murderer.
>
> changes since v7:
> - fix VIO_MOD_TO_REG_IND calculation wrong problem.
> - revise parameter type of ISR.
>
> changes since v6:
> - remove unnecessary mask/unmask module irq during ISR.
>
> changes since v5:
> - remove redundant write reg operation.
> - use static variable of vio_dbgs instead.
> - add stop_devapc() if driver is removed.
>
> changes since v4:
> - refactor data structure.
> - merge two simple functions into one.
> - refactor register setting to prevent too many function call overhead.
>
> changes since v3:
> - revise violation handling flow to make it more easily to understand
> hardware behavior.
> - add more comments to understand how hardware works.
>
> changes since v2:
> - pass platform info through DT data.
> - remove unnecessary function.
> - remove slave_type because it always equals to 1 in current support SoC.
> - use vio_idx_num instread of list all devices' index.
> - add more comments to describe hardware behavior.
>
> changes since v1:
> - move SoC specific part to DT data.
> - remove unnecessary boundary check.
> - remove unnecessary data type declaration.
> - use read_poll_timeout() instread of for loop polling.
> - revise coding style elegantly.
>
>
> *** BLURB HERE ***
>
> Neal Liu (2):
> dt-bindings: devapc: add bindings for mtk-devapc
> soc: mediatek: add mt6779 devapc driver
>
> .../bindings/soc/mediatek/devapc.yaml | 58 ++++
> drivers/soc/mediatek/Kconfig | 9 +
> drivers/soc/mediatek/Makefile | 1 +
> drivers/soc/mediatek/mtk-devapc.c | 308 ++++++++++++++++++
> 4 files changed, 376 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> create mode 100644 drivers/soc/mediatek/mtk-devapc.c
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-10-15 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 3:20 Neal Liu
2020-10-15 3:20 ` [PATCH v8 1/2] dt-bindings: devapc: add bindings for mtk-devapc Neal Liu
2020-10-21 15:05 ` Rob Herring
2020-10-15 3:20 ` [PATCH v8 2/2] soc: mediatek: add mt6779 devapc driver Neal Liu
2021-01-14 9:40 ` Pi-Hsun Shih
2020-10-15 3:24 ` Neal Liu [this message]
2020-11-02 7:24 ` [PATCH v8] Add MediaTek MT6779 " Neal Liu
2020-11-27 23:31 ` Matthias Brugger
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=1602732276.13734.1.camel@mtkswgap22 \
--to=neal.liu@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--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+dt@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).