From: Conor Dooley <conor@kernel.org>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: regulator: mt6315: Document MT6319 PMIC
Date: Thu, 20 Jun 2024 17:12:24 +0100 [thread overview]
Message-ID: <20240620-opal-reopen-f2aeffc9b041@spud> (raw)
In-Reply-To: <20240620094746.2404753-2-wenst@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Thu, Jun 20, 2024 at 05:47:36PM +0800, Chen-Yu Tsai wrote:
> The MT6319 is a pin-compatible drop-in replacement for MT6315 with
> slightly better electrical characteristics.
>
> It's unclear whether there are any differences, since the downstream
> implementation doesn't describe the MT6319 separately. Neither does the
> implementation check chip IDs, even though those are available.
>
> Add a new compatible for the MT6319 just in case differences are
> discovered later and fall back to the MT6315 compatible.
>
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-20 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:47 [PATCH 0/3] arm64: dts: mediatek: Add MT8186 Voltorb Chromebooks Chen-Yu Tsai
2024-06-20 9:47 ` [PATCH 1/3] dt-bindings: regulator: mt6315: Document MT6319 PMIC Chen-Yu Tsai
2024-06-20 16:12 ` Conor Dooley [this message]
2024-06-20 9:47 ` [PATCH 2/3] dt-bindings: arm: mediatek: Add MT8186 Voltorb Chromebooks Chen-Yu Tsai
2024-06-20 16:13 ` Conor Dooley
2024-06-24 7:45 ` Chen-Yu Tsai
2024-06-20 9:47 ` [PATCH 3/3] arm64: dts: " Chen-Yu Tsai
2024-06-21 0:49 ` (subset) [PATCH 0/3] " Mark Brown
2024-06-24 10:51 ` AngeloGioacchino Del Regno
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=20240620-opal-reopen-f2aeffc9b041@spud \
--to=conor@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hsin-hsiung.wang@mediatek.com \
--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@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).