From: Chen-Yu Tsai <wenst@chromium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Lee Jones <lee@kernel.org>,
linux-mediatek@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, matthias.bgg@gmail.com,
lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
igor.belwon@mentallysanemainliners.org
Subject: Re: [PATCH v11 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD
Date: Thu, 26 Mar 2026 13:34:49 +0800 [thread overview]
Message-ID: <20260326053449.GA910813@google.com> (raw)
In-Reply-To: <701b6abc-71e8-43fc-adfd-211a62dbec64@collabora.com>
On Fri, Nov 07, 2025 at 10:01:56AM +0100, AngeloGioacchino Del Regno wrote:
> Il 06/11/25 17:11, Lee Jones ha scritto:
> > On Mon, 27 Oct 2025, AngeloGioacchino Del Regno wrote:
> >
> > > Changes in v11:
> > > - Removed unnecessary #address-cells in all mt6316 bindings
> > >
> > > Changes in v10:
> > > - Added "struct" prefix to structs kerneldoc
> > > - Renamed struct mtk_spmi_pmic_pdata to mtk_spmi_pmic_variant
> > > - Added "REG_" to MT6363/73 mfd register definitions to disambiguate
> > > - Expanded MTK_SPMI_PMIC_IRQ_GROUP macro parameter names as suggested
> > > - Some rewording of comments as suggested, addition of more comments
> > > - Refactored IRQ domain handling due to deprecation of function
> > > irq_domain_add_tree() to use the new irq_domain_create_tree()
> > > - Fixed to use generic_handle_domain_irq_safe() to avoid races
> > > - Added support for two interrupt cells in translation
> > > - Removed .irq_lock() and .irq_unlock() in favor of lockdep classes
> > > - Added support for handling PMICs without IRQ Group register for
> > > upcoming MT6685 implementation
> >
> > The MFD part looks okay.
> >
> > Let me know when you have all the Acks and the set is ready to be merged.
> >
>
>
> Lee, the regulators part was picked by Mark, so I guess you can take the MFD part
> through your tree.
>
> I'm not sure if you can also take patch [7/9] (auxadc binding), but it would be
> great if you could, because there is an auxadc example in the mfd binding that
> needs that commit in order to succeed the binding check.
Friendly ping. You might want to resend the remaining patches. Looks
like they are all ready to be merged?
ChenYu
next prev parent reply other threads:[~2026-03-26 5:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 11:05 [PATCH v11 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators AngeloGioacchino Del Regno
2025-10-27 16:43 ` Conor Dooley
2025-10-27 11:05 ` [PATCH v11 2/9] regulator: Add support for MediaTek MT6316 SPMI " AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 3/9] dt-bindings: regulator: Document MediaTek MT6363 " AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 4/9] regulator: Add support for MediaTek MT6363 SPMI " AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 5/9] dt-bindings: regulator: Document MediaTek MT6373 " AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 6/9] regulator: Add support for MediaTek MT6373 SPMI " AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 7/9] dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 8/9] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC AngeloGioacchino Del Regno
2025-10-27 11:05 ` [PATCH v11 9/9] mfd: Add support for MediaTek SPMI PMICs and MT6363/73 AngeloGioacchino Del Regno
2025-11-06 16:11 ` [PATCH v11 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD Lee Jones
2025-11-07 9:01 ` AngeloGioacchino Del Regno
2026-03-26 5:34 ` Chen-Yu Tsai [this message]
2026-03-26 9:25 ` Lee Jones
2025-11-06 23:54 ` (subset) " Mark Brown
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=20260326053449.GA910813@google.com \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.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=robh@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