From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Tim Chang <jia-wei.chang@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Roger Lu <roger.lu@mediatek.com>,
Kevin Hilman <khilman@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
hsinyi@google.com
Subject: Re: [PATCH 2/2] soc: mediatek: svs: add support for mt8186
Date: Tue, 12 Apr 2022 17:30:34 +0200 [thread overview]
Message-ID: <138aad1c-63d7-371a-ff41-4fd7022d365d@collabora.com> (raw)
In-Reply-To: <20220412112127.21570-3-jia-wei.chang@mediatek.com>
Il 12/04/22 13:21, Tim Chang ha scritto:
> From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>
> MT8186 svs has a number of banks which used as optimization of opp
> voltage table for corresponding dvfs drivers.
> MT8186 svs big core uses 2-line high bank and low bank to optimize the
> voltage of opp table for higher and lower frequency respectively.
>
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
For the code only, as I am unable to test:
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2022-04-12 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 11:21 [PATCH 0/2] " Tim Chang
2022-04-12 11:21 ` [PATCH 1/2] dt-bindings: soc: mediatek: add mt8186 svs dt-bindings Tim Chang
2022-04-12 12:08 ` Krzysztof Kozlowski
2022-04-14 5:32 ` Jia-Wei Chang
2022-04-12 11:21 ` [PATCH 2/2] soc: mediatek: svs: add support for mt8186 Tim Chang
2022-04-12 15:30 ` AngeloGioacchino Del Regno [this message]
2022-04-14 6:25 ` Jia-Wei Chang
2022-04-12 22:58 ` Kevin Hilman
2022-04-14 6:09 ` Jia-Wei Chang
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=138aad1c-63d7-371a-ff41-4fd7022d365d@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@google.com \
--cc=jia-wei.chang@mediatek.com \
--cc=khilman@kernel.org \
--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=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=roger.lu@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
all inboxes | Powered by JetHome®