From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Karl.Li" <karl.li@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Chungying Lu <chungying.lu@mediatek.com>,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH 1/1] soc: mediatek: Add command for APU SMC call
Date: Thu, 24 Oct 2024 12:27:10 +0200 [thread overview]
Message-ID: <9ace7c33-7e45-4d87-869c-8d45afb47750@collabora.com> (raw)
In-Reply-To: <20241024092712.431605-2-karl.li@mediatek.com>
Il 24/10/24 11:27, Karl.Li ha scritto:
> 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/soc/mediatek/mtk_apu_secure.h | 32 +++++++++++++++++++++
This is firmware stuff!
Please move this file to
include/linux/firmware/mediatek/apu.h or apusys.h
If you expect that the APU will *never* have any non-secure commands, then you
can add the "-secure" suffix (apu-secure.h) - but if there will ever be any
commands that aren't secured, you should not call it xxxx-secure.h
> 1 file changed, 32 insertions(+)
> create mode 100644 include/linux/soc/mediatek/mtk_apu_secure.h
>
> diff --git a/include/linux/soc/mediatek/mtk_apu_secure.h b/include/linux/soc/mediatek/mtk_apu_secure.h
> new file mode 100644
> index 000000000000..ea491bc24adb
> --- /dev/null
> +++ b/include/linux/soc/mediatek/mtk_apu_secure.h
> @@ -0,0 +1,32 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * Copyright (c) 2024 MediaTek Inc.
> + */
> +
> +#ifndef __MTK_APU_SECURE_H__
> +#define __MTK_APU_SECURE_H__
Please, __MTK --> __MEDIATEK (also because the folder is called "mediatek", anyway)
> +
> +enum mtk_apusys_kernel_op {
here you can keep the prefix as mtk_
> + MTK_APUSYS_KERNEL_OP_APUSYS_PWR_TOP_ON, /* 0 */
and MTK_ is ok for those definitions too.
Cheers,
Angelo
> + 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
prev parent reply other threads:[~2024-10-24 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 9:27 [PATCH 0/1] Add MediaTek APU SMC call Definition Karl.Li
2024-10-24 9:27 ` [PATCH 1/1] soc: mediatek: Add command for APU SMC call Karl.Li
2024-10-24 10:27 ` AngeloGioacchino Del Regno [this message]
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=9ace7c33-7e45-4d87-869c-8d45afb47750@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chungying.lu@mediatek.com \
--cc=karl.li@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®