From: Christopher Obbard <chris.obbard@collabora.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
matthias.bgg@gmail.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wenst@chromium.org
Subject: Re: [PATCH] soc: mediatek: mtk-socinfo: Add entry for MT8395AV/ZA Genio 1200
Date: Thu, 04 Apr 2024 13:46:16 +0100 [thread overview]
Message-ID: <10127a05c2c6b7ac3ec4331a3e590c122335800e.camel@collabora.com> (raw)
In-Reply-To: <20240404082056.93454-1-angelogioacchino.delregno@collabora.com>
Hi Angelo,
On Thu, 2024-04-04 at 10:20 +0200, AngeloGioacchino Del Regno wrote:
> Add an entry for the MT8395 SoC with commercial name Genio 1200.
>
> Signed-off-by: AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com>
Reviewed-by: Christopher Obbard <chris.obbard@collabora.com>
Tested-by: Christopher Obbard <chris.obbard@collabora.com>
> ---
> drivers/soc/mediatek/mtk-socinfo.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/soc/mediatek/mtk-socinfo.c b/drivers/soc/mediatek/mtk-
> socinfo.c
> index 4494cca1d075..6943ab29f095 100644
> --- a/drivers/soc/mediatek/mtk-socinfo.c
> +++ b/drivers/soc/mediatek/mtk-socinfo.c
> @@ -56,6 +56,7 @@ static struct socinfo_data socinfo_data_table[] = {
> MTK_SOCINFO_ENTRY("MT8195", "MT8195GV/EHZA", "Kompanio 1200",
> 0x81950304, CELL_NOT_USED),
> MTK_SOCINFO_ENTRY("MT8195", "MT8195TV/EZA", "Kompanio 1380",
> 0x81950400, CELL_NOT_USED),
> MTK_SOCINFO_ENTRY("MT8195", "MT8195TV/EHZA", "Kompanio 1380",
> 0x81950404, CELL_NOT_USED),
> + MTK_SOCINFO_ENTRY("MT8395", "MT8395AV/ZA", "Genio 1200",
> 0x83950100, CELL_NOT_USED),
> };
>
> static int mtk_socinfo_create_socinfo_node(struct mtk_socinfo
> *mtk_socinfop)
next prev parent reply other threads:[~2024-04-04 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 8:20 [PATCH] soc: mediatek: mtk-socinfo: Add entry for MT8395AV/ZA Genio 1200 AngeloGioacchino Del Regno
2024-04-04 12:46 ` Christopher Obbard [this message]
2024-04-04 17:24 ` Alexandre Mergnat
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=10127a05c2c6b7ac3ec4331a3e590c122335800e.camel@collabora.com \
--to=chris.obbard@collabora.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 \
--cc=wenst@chromium.org \
/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