From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: William-tw Lin <william-tw.lin@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v4 3/3] nvmem: mtk-efuse: Register MediaTek socinfo driver from efuse
Date: Tue, 2 Jan 2024 10:48:49 +0100 [thread overview]
Message-ID: <94bbcec7-b587-4c19-8d81-44749885968c@collabora.com> (raw)
In-Reply-To: <20231222080739.21706-4-william-tw.lin@mediatek.com>
Il 22/12/23 09:07, William-tw Lin ha scritto:
> The socinfo driver reads chip information from eFuses and does not need
> any devicetree node. Register it from mtk-efuse.
>
> While at it, also add the name for this driver's nvmem_config.
>
> Signed-off-by: William-tw Lin <william-tw.lin@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2024-01-02 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 8:07 [PATCH v4 0/3] mtk-socinfo driver implementation William-tw Lin
2023-12-22 8:07 ` [PATCH v4 1/3] arm64: dts: mediatek: Add socinfo efuses to MT8173/83/96/92/95 SoCs William-tw Lin
2024-01-02 9:49 ` AngeloGioacchino Del Regno
2024-01-29 10:27 ` AngeloGioacchino Del Regno
2023-12-22 8:07 ` [PATCH v4 2/3] soc: mediatek: mtk-socinfo: Add driver for getting chip information William-tw Lin
2024-01-02 9:48 ` AngeloGioacchino Del Regno
2024-01-29 10:27 ` AngeloGioacchino Del Regno
2023-12-22 8:07 ` [PATCH v4 3/3] nvmem: mtk-efuse: Register MediaTek socinfo driver from efuse William-tw Lin
2024-01-02 9:48 ` AngeloGioacchino Del Regno [this message]
2024-01-27 11:29 ` (subset) [PATCH v4 0/3] mtk-socinfo driver implementation Srinivas Kandagatla
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=94bbcec7-b587-4c19-8d81-44749885968c@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=william-tw.lin@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®