From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: EastL Lee <EastL.Lee@mediatek.com>, Sean Wang <sean.wang@mediatek.com>
Cc: vkoul@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
matthias.bgg@gmail.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
wsd_upstream@mediatek.com, cc.hwang@mediatek.com,
joane.wang@mediatek.com, adrian-cj.hung@mediatek.com
Subject: Re: [PATCH v1 1/3] memory: Add support for MediaTek External Memory Interface driver
Date: Tue, 4 May 2021 10:15:28 -0400 [thread overview]
Message-ID: <2cf92fc2-ccac-312f-f4a6-9a4dfd9aee9c@canonical.com> (raw)
In-Reply-To: <1611746924-12287-2-git-send-email-EastL.Lee@mediatek.com>
On 27/01/2021 07:28, EastL Lee wrote:
> MediaTek External Memory Interface(emi) on MT6779 SoC controls all the
> transitions from master to dram, there are emi-cen & emi-mpu drivers.
>
> emi-cen driver provides phy addr to dram rank, bank, column and other
> information, as well as the currently used dram channel number, rank
> number, rank size.
>
> emi-mpu (memory protect unit) driver provides an interface to set emi
> regions, need to enter the secure world setting and the violation irq
> isr will collect mpu violation information, after all regions have
> protected their respective regions, emi-mpu will set the ap region to
> protect all the remaining dram.
>
> Signed-off-by: EastL Lee <EastL.Lee@mediatek.com>
> ---
> drivers/memory/Kconfig | 1 +
> drivers/memory/Makefile | 1 +
> drivers/memory/mediatek/Kconfig | 23 +
> drivers/memory/mediatek/Makefile | 4 +
> drivers/memory/mediatek/emi-cen.c | 1305 ++++++++++++++++++++++++++++++
> drivers/memory/mediatek/emi-mpu.c | 908 +++++++++++++++++++++
> include/linux/soc/mediatek/mtk_sip_svc.h | 3 +
> include/soc/mediatek/emi.h | 101 +++
> 8 files changed, 2346 insertions(+)
> create mode 100644 drivers/memory/mediatek/Kconfig
> create mode 100644 drivers/memory/mediatek/Makefile
> create mode 100644 drivers/memory/mediatek/emi-cen.c
> create mode 100644 drivers/memory/mediatek/emi-mpu.c
> create mode 100644 include/soc/mediatek/emi.h
>
Use scripts/get_maintainers.pl to get list of people you need to Cc.
Run checkpatch, smatch, sparse and coccinelle on your new driver. I can
easily see that some of these steps were missing (e.g. OWNER field...).
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-05-04 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 11:28 [PATCH v1] memory: mediatek emi: add MediaTek EMI driver EastL Lee
2021-01-27 11:28 ` [PATCH v1 1/3] memory: Add support for MediaTek External Memory Interface driver EastL Lee
2021-05-04 14:15 ` Krzysztof Kozlowski [this message]
2021-01-27 11:28 ` [PATCH v1 2/3] arm64: dts: mt6779: add emi node EastL Lee
2021-01-27 11:28 ` [PATCH v1 3/3] arm64: configs: mt6779: enable HAVE_MTK_MC config EastL Lee
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=2cf92fc2-ccac-312f-f4a6-9a4dfd9aee9c@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=EastL.Lee@mediatek.com \
--cc=adrian-cj.hung@mediatek.com \
--cc=cc.hwang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=joane.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vkoul@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
all inboxes | Powered by JetHome®