From: "Karl Li (李智嘉)" <Karl.Li@mediatek.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Chungying Lu (呂忠穎)" <Chungying.Lu@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Andy Teng (鄧如宏)" <Andy.Teng@mediatek.com>,
"Chien-Chih Tseng (曾建智)" <Chien-Chih.Tseng@mediatek.com>
Subject: Re: [PATCH v2 1/1] soc: mediatek: Add command for APU SMC call
Date: Thu, 5 Dec 2024 07:34:08 +0000 [thread overview]
Message-ID: <94480dcb145fba89c41045cde374e1dd71a1e6af.camel@mediatek.com> (raw)
In-Reply-To: <b8de718de8d5b5357f67183c1d283180aff33f62.camel@mediatek.com>
On Thu, 2024-12-05 at 14:49 +0800, Karl Li wrote:
> Dead maintainers,
"Dear" maintainers. Really sorry for the typo...
>
> I hope you're doing well. Just a warm reminder that we're following
> up
> on this patch and really appreciate any feedback you might have.
>
> Thanks you in advance for your review.
>
> Regards,
> Karl
>
> On Wed, 2024-10-30 at 09:35 +0800, Karl.Li wrote:
> > From: Karl Li <karl.li@mediatek.com>
> >
> > Add command for APU SMC call.
> > The APU microprocess's start and stop sequence will process in ATF.
> >
> > Signed-off-by: Karl Li <karl.li@mediatek.com>
> > ---
> > include/linux/firmware/mediatek/mtk-apu.h | 32
> > +++++++++++++++++++++++
> > 1 file changed, 32 insertions(+)
> > create mode 100644 include/linux/firmware/mediatek/mtk-apu.h
> >
> > diff --git a/include/linux/firmware/mediatek/mtk-apu.h
> > b/include/linux/firmware/mediatek/mtk-apu.h
> > new file mode 100644
> > index 000000000000..a327e31d40fa
> > --- /dev/null
> > +++ b/include/linux/firmware/mediatek/mtk-apu.h
> > @@ -0,0 +1,32 @@
> > +/* SPDX-License-Identifier: GPL-2.0 */
> > +/*
> > + * Copyright (c) 2024 MediaTek Inc.
> > + */
> > +
> > +#ifndef __MEDIATEK_APU_H__
> > +#define __MEDIATEK_APU_H__
> > +
> > +enum mtk_apusys_kernel_op {
> > + MTK_APUSYS_KERNEL_OP_APUSYS_PWR_TOP_ON,
> > /* 0 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_PWR_TOP_OFF, /*
> >
> > 1 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_SETUP_REVISER, /*
> >
> > 2 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_RESET_MP, /*
> >
> > 3 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_SETUP_BOOT, /*
> >
> > 4 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_START_MP, /*
> >
> > 5 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_STOP_MP,
> > /* 6 */
> > + MTK_APUSYS_KERNEL_OP_DEVAPC_INIT_RCX, /*
> >
> > 7 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_SETUP_SEC_MEM, /*
> >
> > 8 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_DISABLE_WDT_ISR,
> > /* 9 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_CLEAR_WDT_ISR, /*
> > 10 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_CG_GATING, /*
> > 11 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_CG_UNGATING, /*
> > 12 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_RV_SETUP_APUMMU, /*
> > 13 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_LOGTOP_REG_DUMP, /*
> > 14 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_LOGTOP_REG_WRITE, /*
> > 15 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_LOGTOP_REG_W1C, /*
> > 16 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_COLD_BOOT_CLR_MBOX_DUMMY, /*
> > 17 */
> > + MTK_APUSYS_KERNEL_OP_APUSYS_SETUP_CE_BIN, /*
> > 18 */
> > + MTK_APUSYS_KERNEL_OP_NUM,
> > +};
> > +
> > +#endif
>
next prev parent reply other threads:[~2024-12-05 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 1:35 [PATCH v2 0/1] Add MediaTek APU SMC call Definition Karl.Li
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 (李智嘉) [this message]
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=94480dcb145fba89c41045cde374e1dd71a1e6af.camel@mediatek.com \
--to=karl.li@mediatek.com \
--cc=Andy.Teng@mediatek.com \
--cc=Chien-Chih.Tseng@mediatek.com \
--cc=Chungying.Lu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.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®