From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Vadym Kochan <vadym.kochan@plvision.eu>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: marvell: fix non-existed cpu referrence in armada-ap806-dual.dtsi
Date: Sun, 01 Mar 2020 08:44:19 +0100 [thread overview]
Message-ID: <647B367B-4278-4D00-98D3-1FCA76D87488@bootlin.com> (raw)
In-Reply-To: <20200229230648.GA21220@plvision.eu>
Le 1 mars 2020 00:06:56 GMT+01:00, Vadym Kochan <vadym.kochan@plvision.eu> a écrit :
>Hi,
>
Hello
>Just softly ping if I sent it to the right direction.
It looks ok, and was on the list of patches to apply
Sorry for the delay
>
>On Sun, Feb 09, 2020 at 11:20:30PM +0200, Vadym Kochan wrote:
>> armada-ap806-dual.dtsi includes armada-ap806.dtsi which describes
>> thermal zones for 4 cpus but only cpu0 and cpu1 only exists for dual
>> configuration, this makes dtb compilation fail. Fix it by removing
>> thermal zone nodes for non-existed cpus for dual configuration.
>>
>> Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
>> ---
>> arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi
>b/arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi
>> index 09849558a776..fcab5173fe67 100644
>> --- a/arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi
>> +++ b/arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi
>> @@ -53,4 +53,9 @@
>> cache-sets = <512>;
>> };
>> };
>> +
>> + thermal-zones {
>> + /delete-node/ ap-thermal-cpu2;
>> + /delete-node/ ap-thermal-cpu3;
>> + };
>> };
>> --
>> 2.17.1
>>
>
>Regards,
>Vadym Kochan
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2020-03-01 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 21:20 Vadym Kochan
2020-02-29 23:06 ` Vadym Kochan
2020-03-01 7:44 ` Gregory CLEMENT [this message]
2020-03-13 20:35 ` Gregory CLEMENT
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=647B367B-4278-4D00-98D3-1FCA76D87488@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=vadym.kochan@plvision.eu \
/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®