From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Pablo Sun <pablo.sun@mediatek.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 3/6] dt-bindings: nvmem: mediatek: efuse: Reuse mt8186-efuse in mt8188
Date: Wed, 2 Oct 2024 16:11:30 -0500 [thread overview]
Message-ID: <20241002211130.GA1316112-robh@kernel.org> (raw)
In-Reply-To: <559fc2a5-631c-440a-812f-2907f84b16b4@collabora.com>
On Wed, Oct 02, 2024 at 09:42:32AM +0200, AngeloGioacchino Del Regno wrote:
> Il 02/10/24 08:11, Krzysztof Kozlowski ha scritto:
> > On Wed, Oct 02, 2024 at 10:21:35AM +0800, Pablo Sun wrote:
> > > mt8188 has the same GPU speed binning efuse field just
> > > like mt8186, which requires post-processing to convert to the
> > > bit field format specified by OPP table.
What about all the other efuses? The fallback needs to be a subset of
the 1st compatible.
> > >
> > > Add the binding for the compatible list:
> > > "mediatek,mt8188-efuse", "mediatek,mt8186-efuse"
> > > so mt8188 uses the same conversion.
> > >
> > > Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > Signed-off-by: Pablo Sun <pablo.sun@mediatek.com>
> > > ---
> > > Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > > index 32b8c1eb4e80..70815a3329bf 100644
> > > --- a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > > +++ b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > > @@ -39,6 +39,10 @@ properties:
> > > - mediatek,mt8195-efuse
> > > - mediatek,mt8516-efuse
> > > - const: mediatek,efuse
> > > + - items:
> > > + - enum:
> > > + - mediatek,mt8188-efuse
> > > + - const: mediatek,mt8186-efuse
> >
> > And this is not compatible with generic one? This is confusing. Why are
> > you adding generic fallbacks if they are not valid?
> >
>
> It was my suggestion to start dropping the usage of the generic "mediatek,efuse"
> fallback, as I've seen multiple times feedback saying to not use generic fallbacks.
>
> Was that wrong?
No, but any fallback seems seems a bit odd here. It's one of those
things that's going to change with every chip.
Rob
next prev parent reply other threads:[~2024-10-02 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 2:21 [PATCH v3 0/6] Enable Mali GPU on MediaTek Genio 700 EVK Pablo Sun
2024-10-02 2:21 ` [PATCH v3 1/6] arm64: dts: mediatek: mt8188: Fix wrong clock provider in MFG1 power domain Pablo Sun
2024-10-02 2:21 ` [PATCH v3 2/6] clk: mediatek: clk-mt8188-topckgen: Remove univpll from parents of mfg_core_tmp Pablo Sun
2024-10-02 2:21 ` [PATCH v3 3/6] dt-bindings: nvmem: mediatek: efuse: Reuse mt8186-efuse in mt8188 Pablo Sun
2024-10-02 6:11 ` Krzysztof Kozlowski
2024-10-02 7:42 ` AngeloGioacchino Del Regno
2024-10-02 21:11 ` Rob Herring [this message]
2024-10-04 11:08 ` Pablo Sun
2024-10-03 8:13 ` Krzysztof Kozlowski
2024-10-03 8:52 ` AngeloGioacchino Del Regno
2024-10-02 2:21 ` [PATCH v3 4/6] arm64: dts: mediatek: mt8188: Add efuse for GPU speed binning Pablo Sun
2024-10-02 2:21 ` [PATCH v3 5/6] soc: mediatek: mediatek-regulator-coupler: Support mt8188 Pablo Sun
2024-10-02 2:21 ` [PATCH v3 6/6] arm64: dts: mediatek: mt8390-genio-700-evk: Enable Mali GPU Pablo Sun
2024-10-02 9:08 ` (subset) [PATCH v3 0/6] Enable Mali GPU on MediaTek Genio 700 EVK AngeloGioacchino Del Regno
2024-10-02 9:33 ` 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=20241002211130.GA1316112-robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.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=pablo.sun@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;
as well as URLs for NNTP newsgroup(s).