From: Robin Murphy <robin.murphy@arm.com>
To: Heiko Stuebner <heiko@sntech.de>, Johan Jonker <jbx6244@gmail.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [RFC PATCH] arm64: dts: rockchip: add core devicetree for rk3318
Date: Fri, 17 Apr 2020 12:51:15 +0100 [thread overview]
Message-ID: <6d5a1d27-8d32-eca2-007c-aa0bed81af46@arm.com> (raw)
In-Reply-To: <2141402.AJMLQ3pQEO@phil>
On 2020-04-17 12:05 pm, Heiko Stuebner wrote:
> Hi Johan,
>
> Am Freitag, 17. April 2020, 12:57:39 CEST schrieb Johan Jonker:
>> The rk3318 is basically a rk3328 with improved gpu,
>> so add a dtsi based on that.
>>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>
> Please don't add dangling dtsi files.
> I'd expect at least a board dts to actually use that and
> also the updated gpu node.
>
> From a cursory glance it looks like it gets upgraded from
> 450-MP2 to 450MP3 or so, so that would at least mean
> another set of interrupts.
I'm not sure anything's "improved" - as far as the internet can tell
it's a special low-cost variant of RK3328 for low-end TV box vendors
that Rockchip don't want to talk about. The DTB for my H96 Max 3318
shows no appreciable difference from the BSP DT for RK3328, although I
wouldn't be surprised if some of the unused stuff like the external GMAC
was actually missing or broken. The board itself is the exact same one
used in a lot of other cheap RK3328 boxes (and I mean literally, it's
silkscreened "RK3328_8D4_V1.2").
Thanks to one unexpectedly honest Aliexpress listing I stumbled across,
the "penta-core GPU" apparently translates from TV-box-marketing-speak
to mean Mali-450 MP2 (1GP + 2PP) plus the RGA plus the VOP ;)
Robin.
>
> Heiko
>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3318.dtsi | 3 +++
>> 1 file changed, 3 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/rockchip/rk3318.dtsi
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3318.dtsi b/arch/arm64/boot/dts/rockchip/rk3318.dtsi
>> new file mode 100644
>> index 000000000..a32f771bc
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/rockchip/rk3318.dtsi
>> @@ -0,0 +1,3 @@
>> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>> +
>> +#include "rk3328.dtsi"
>>
>
>
>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-17 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 10:57 [RFC PATCH] arm64: dts: rockchip: add core devicetree for rk3318 Johan Jonker
2020-04-17 11:05 ` Heiko Stuebner
2020-04-17 11:51 ` Robin Murphy [this message]
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=6d5a1d27-8d32-eca2-007c-aa0bed81af46@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@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