From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Srinivas Kandagatla <srini@kernel.org>
Cc: rva333@protonmail.com, Sen Chu <sen.chu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Macpaul Lin <macpaul.lin@mediatek.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andy Shevchenko <andy@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Ben Grisdale <bengris32@protonmail.ch>
Subject: Re: [PATCH v4 2/3] nvmem: add mt6323 PMIC EFUSE driver
Date: Tue, 15 Sep 2026 11:11:34 +0300 [thread overview]
Message-ID: <aqj9ttde-cZXPm_Z@ashevche-desk.local> (raw)
In-Reply-To: <170bcc15-38fc-47cb-89f5-8fe7411111aa@kernel.org>
On Mon, Sep 14, 2026 at 11:08:36PM +0100, Srinivas Kandagatla wrote:
> On 9/11/26 7:33 AM, Roman Vivchar via B4 Relay wrote:
> > Add support for the EFUSE controller found in the Mediatek MT6323 PMIC.
> > The MT6323 EFUSE stores 24 bytes of hardware-related data, such as
> > thermal sensor calibration values.
...
> > +++ b/MAINTAINERS
> > F: drivers/iio/adc/mt6323-auxadc.c
> > F: include/dt-bindings/iio/adc/mediatek,mt6323-auxadc.h
> >
> > +MEDIATEK MT6323 PMIC NVMEM DRIVER
> > +M: Roman Vivchar <rva333@protonmail.com>
> > +S: Maintained
> > +F: drivers/nvmem/mt6323-efuse.c
>
> placement is in wrong order,
Can you elaborate on this? I do not see the issue.
> same in make file too.
> > MEDIATEK MT6735 CLOCK & RESET DRIVERS
> > M: Yassine Oudjana <y.oudjana@protonmail.com>
> > L: linux-clk@vger.kernel.org
...
> > +++ b/drivers/nvmem/Makefile
> > obj-$(CONFIG_NVMEM_MICROCHIP_OTPC) += nvmem-microchip-otpc.o
> > nvmem-microchip-otpc-y := microchip-otpc.o
> > obj-$(CONFIG_NVMEM_MTK_EFUSE) += nvmem_mtk-efuse.o
> > nvmem_mtk-efuse-y := mtk-efuse.o
> > +obj-$(CONFIG_NVMEM_MT6323_EFUSE) += nvmem_mt6323-efuse.o
> > +nvmem_mt6323-efuse-y := mt6323-efuse.o
Yes, here the digits should be before letters.
> > obj-$(CONFIG_NVMEM_MXS_OCOTP) += nvmem-mxs-ocotp.o
> > nvmem-mxs-ocotp-y := mxs-ocotp.o
> > obj-$(CONFIG_NVMEM_NINTENDO_OTP) += nvmem-nintendo-otp.o
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-15 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 6:32 [PATCH v4 0/3] nvmem: add support for the MediaTek mt6323 PMIC Roman Vivchar via B4 Relay
2026-09-11 6:32 ` [PATCH v4 1/3] dt-bindings: mfd: mediatek: mt6397: add mt6323 PMIC EFUSE Roman Vivchar via B4 Relay
2026-09-11 6:33 ` [PATCH v4 2/3] nvmem: add mt6323 PMIC EFUSE driver Roman Vivchar via B4 Relay
2026-09-14 22:08 ` Srinivas Kandagatla
2026-09-15 8:11 ` Andy Shevchenko [this message]
2026-09-11 6:33 ` [PATCH v4 3/3] ARM: dts: mediatek: mt6323: add EFUSE support Roman Vivchar via B4 Relay
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=aqj9ttde-cZXPm_Z@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bengris32@protonmail.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=rva333@protonmail.com \
--cc=sean.wang@mediatek.com \
--cc=sen.chu@mediatek.com \
--cc=srini@kernel.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