From: Neil Armstrong <narmstrong@baylibre.com>
To: Alexander Stein <alexander.stein@mailbox.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: amlogic: meson-g12: Fix GPU operating point table node name
Date: Mon, 25 Oct 2021 10:19:48 +0200 [thread overview]
Message-ID: <fdacca3e-a35f-ac88-8a57-1fa5bb049e68@baylibre.com> (raw)
In-Reply-To: <20211023214856.30097-3-alexander.stein@mailbox.org>
On 23/10/2021 23:48, Alexander Stein wrote:
> Starting with commit 94274f20f6bf ("dt-bindings: opp: Convert to DT
> schema") the opp node name has a mandatory pattern. This change
> fixes the dtbs_check warning:
> gpu-opp-table: $nodename:0: 'gpu-opp-table' does not match
> '^opp-table(-[a-z0-9]+)?$'
> Put the 'gpu' part at the end to match the pattern.
>
> Fixes: 916a0edc43f0 ("arm64: dts: amlogic: meson-g12: add the Mali OPP table and use DVFS")
> Signed-off-by: Alexander Stein <alexander.stein@mailbox.org>
> ---
> Same as with patch 2/4 about the 'Fixes' tag: At the time when
> gpu-opp-table was added there was no schema present. So there was no bug at
> the time of writing. I'm ok either way.
>
> arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> index ff987e7ccff2..517519e6e87f 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> @@ -58,7 +58,7 @@ efuse: efuse {
> secure-monitor = <&sm>;
> };
>
> - gpu_opp_table: gpu-opp-table {
> + gpu_opp_table: opp-table-gpu {
> compatible = "operating-points-v2";
>
> opp-124999998 {
>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-10-25 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 21:48 [PATCH 1/4] dt-bindings: sound: amlogic: t9015: Add missing AVDD-supply property Alexander Stein
2021-10-23 21:48 ` [PATCH 2/4] arm64: dts: amlogic: meson-g12: Fix thermal-zones indent Alexander Stein
2021-10-26 7:27 ` Neil Armstrong
2021-10-26 16:21 ` Alexander Stein
2021-10-23 21:48 ` [PATCH 3/4] arm64: dts: amlogic: meson-g12: Fix GPU operating point table node name Alexander Stein
2021-10-25 8:19 ` Neil Armstrong [this message]
2021-10-23 21:48 ` [PATCH 4/4] arm64: dts: amlogic: Fix SPI NOR flash node name for ODROID N2/N2+ Alexander Stein
2021-10-25 8:20 ` Neil Armstrong
2021-10-24 14:27 ` [PATCH 1/4] dt-bindings: sound: amlogic: t9015: Add missing AVDD-supply property Rob Herring
2021-10-25 9:44 ` Mark Brown
2021-10-25 15:53 ` Jerome Brunet
2021-10-26 16:30 ` Alexander Stein
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=fdacca3e-a35f-ac88-8a57-1fa5bb049e68@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=alexander.stein@mailbox.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.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