From: Karl.Li <karl.li@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Karl Li <Karl.Li@mediatek.com>,
Chungying Lu <chungying.lu@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<chien-chih.tseng@mediatek.com>, <andy.teng@mediatek.com>,
Karl Li <karl.li@mediatek.com>
Subject: [PATCH v2 0/1] Add MediaTek APU SMC call Definition
Date: Wed, 30 Oct 2024 09:35:27 +0800 [thread overview]
Message-ID: <20241030013533.855696-1-karl.li@mediatek.com> (raw)
From: Karl Li <karl.li@mediatek.com>
Based on tag: next-20241029, linux-next/master
Hello,
This patch introduces the SMC calls for MediaTek APU.
The start and stop sequences of the APU microprocessor are managed within the ARM Trusted Firmware (ATF), which requires a secure and reliable communication channel to issue commands from the non-secure world. This patch adds the necessary infrastructure to issue these SMC calls, ensuring that the APU can be securely managed by the system's software.
Please review and provide feedback.
Best regards
---
Changes in v2:
- Move header file to include/linux/firmware/mediatek/
- Rename header file name to mtk-apu.h
- Update define macro name to __MEDIATEK
Karl Li (1):
soc: mediatek: Add command for APU SMC call
include/linux/firmware/mediatek/mtk-apu.h | 32 +++++++++++++++++++++++
1 file changed, 32 insertions(+)
create mode 100644 include/linux/firmware/mediatek/mtk-apu.h
--
2.18.0
next reply other threads:[~2024-10-30 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 1:35 Karl.Li [this message]
2024-10-30 1:35 ` [PATCH v2 1/1] soc: mediatek: Add command for APU SMC call Karl.Li
2024-12-05 6:49 ` Karl Li (李智嘉)
2024-12-05 7:34 ` Karl Li (李智嘉)
2024-12-10 8:30 ` AngeloGioacchino Del Regno
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=20241030013533.855696-1-karl.li@mediatek.com \
--to=karl.li@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andy.teng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chien-chih.tseng@mediatek.com \
--cc=chungying.lu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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®