From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] nvmem: mtk-efuse: Enable GPU speed bin post-processing for MT8188
Date: Mon, 23 Dec 2024 12:43:21 +0100 [thread overview]
Message-ID: <bbc6aa2a-fe48-4e06-b070-fd66dbd00e15@collabora.com> (raw)
In-Reply-To: <CAGXv+5Fj5s9FUyaxmEkGimxjEcS6OEfm4_5Zso+YocSi+Vt4pg@mail.gmail.com>
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@collabora.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".
Cheers!
> Fine by me. :D
>
> ChenYu
>
>> instead :-)
>>
>> Cheers,
>> Angelo
>>
>>> Cc: <stable@vger.kernel.org>
>>> Fixes: ff1df1886f43 ("dt-bindings: nvmem: mediatek: efuse: Add support for MT8188")
>>> Signed-off-by: Chen-Yu Tsai <wenst@chromium.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 */},
>>> };
>>
next prev parent reply other threads:[~2024-12-23 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 10:06 [PATCH] nvmem: mtk-efuse: Enable GPU speed bin post-processing for MT8188 Chen-Yu Tsai
2024-12-23 11:11 ` AngeloGioacchino Del Regno
2024-12-23 11:24 ` Chen-Yu Tsai
2024-12-23 11:43 ` AngeloGioacchino Del Regno [this message]
2024-12-23 15:57 ` Chen-Yu Tsai
2024-12-23 16:08 ` AngeloGioacchino Del Regno
2024-12-23 16:15 ` Chen-Yu Tsai
2025-01-07 13:12 ` AngeloGioacchino Del Regno
2025-01-08 6:36 ` Chen-Yu Tsai
2025-01-09 11:46 ` 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=bbc6aa2a-fe48-4e06-b070-fd66dbd00e15@collabora.com \
--to=angelogioacchino.delregno@collabora.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=srinivas.kandagatla@linaro.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.