linux-kernel - Re: [PATCH] nvmem: mtk-efuse: Enable GPU speed bin post-processing for MT8188

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGXv+5FoOM=ZUCWigdCaPbc4FCBtLVX2xnUJnVnVsBH=7yoZ=Q@mail.gmail.com>
Date: Mon, 23 Dec 2024 23:57:10 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
	Matthias Brugger <matthias.bgg@...il.com>, linux-kernel@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, 
	stable@...r.kernel.org
Subject: Re: [PATCH] nvmem: mtk-efuse: Enable GPU speed bin post-processing
 for MT8188

On Mon, Dec 23, 2024 at 7:43 PM AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com> wrote:
>
> Il 23/12/24 12:24, Chen-Yu Tsai ha scritto:
> > On Mon, Dec 23, 2024 at 7:11 PM AngeloGioacchino Del Regno
> > <angelogioacchino.delregno@...labora.com> wrote:
> >>
> >> Il 23/12/24 11:06, Chen-Yu Tsai ha scritto:
> >>> Like the MT8186, the MT8188 stores GPU speed binning data in its efuse.
> >>> The data needs post-processing into a format that the OPP framework can
> >>> use.
> >>>
> >>> Add a compatible match for MT8188 efuse with post-processing enabled.
> >>>
> >>
> >> Let's just change the MT8188 compatible list to
> >>
> >> compatible = "mediatek,mt8188-efuse", "mediatek,mt8186-efuse";
> >
> > That would be "mediatek,mt8188-efuse", "mediatek,mt8186-efuse", "mediatek,efuse"
> > then?
> >
>
> No, we're dropping the generic "mediatek,efuse".

That means we also drop it for MT8186?

Thinking about it more, I think it's stretching things a bit. The hardware
is clearly backwards compatible, or we wouldn't even be reading values
out correctly. The only difference now with MT8186 and MT8188 is that
they have a speed-bin field with a value that we want passed to the OPP
framework, and the interpretation of that value is not really part of
the efuse's hardware. We chose to do the conversion in the efuse driver,
but we could also have done it in the GPU driver.

What I'm saying is that we should not need to change the compatible strings
to make this work.


ChenYu

> Cheers!
>
> > Fine by me. :D
> >
> > ChenYu
> >
> >> instead :-)
> >>
> >> Cheers,
> >> Angelo
> >>
> >>> Cc: <stable@...r.kernel.org>
> >>> Fixes: ff1df1886f43 ("dt-bindings: nvmem: mediatek: efuse: Add support for MT8188")
> >>> Signed-off-by: Chen-Yu Tsai <wenst@...omium.org>
> >>> ---
> >>>
> >>> I'm not exactly sure about pointing to the dt bindings commit for the
> >>> fixes tag.
> >>> ---
> >>>    drivers/nvmem/mtk-efuse.c | 1 +
> >>>    1 file changed, 1 insertion(+)
> >>>
> >>> diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c
> >>> index af953e1d9230..e8409e1e7fac 100644
> >>> --- a/drivers/nvmem/mtk-efuse.c
> >>> +++ b/drivers/nvmem/mtk-efuse.c
> >>> @@ -112,6 +112,7 @@ static const struct mtk_efuse_pdata mtk_efuse_pdata = {
> >>>    static const struct of_device_id mtk_efuse_of_match[] = {
> >>>        { .compatible = "mediatek,mt8173-efuse", .data = &mtk_efuse_pdata },
> >>>        { .compatible = "mediatek,mt8186-efuse", .data = &mtk_mt8186_efuse_pdata },
> >>> +     { .compatible = "mediatek,mt8188-efuse", .data = &mtk_mt8186_efuse_pdata },
> >>>        { .compatible = "mediatek,efuse", .data = &mtk_efuse_pdata },
> >>>        {/* sentinel */},
> >>>    };
> >>
>
>