From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 3/3] ARM64: dts: meson-gx: Add MALI nodes for GXBB and GXL
Date: Thu, 2 Mar 2017 13:47:26 +0100 [thread overview]
Message-ID: <e80d9fb0-1d71-7cab-5e32-72316474fdfc@baylibre.com> (raw)
In-Reply-To: <e26cf584-dab2-2702-f7e6-b28f750fa00c@suse.de>
Hi Andreas,
On 03/02/2017 01:31 PM, Andreas F?rber wrote:
> Hi Neil,
>
> Am 01.03.2017 um 11:46 schrieb Neil Armstrong:
>> The same MALI-450 MP3 GPU is present in the GXBB and GXL SoCs.
>
> First of all, any reason you're upper-casing Mali in the commit message?
> ARM doesn't.
No reason, only a type, indeed it was lower-casing on the v1.
Will fix in v2.
>
>>
>> The node is simply added in the meson-gxbb.dtsi file.
>
> The GXBB part looks fine on a quick look.
>
>>
>> For GXL, since a lot is shared with the GXM that has a MALI-T820 IP, this
>> patch adds a new meson-gxl-mali.dtsi and is included in the SoC specific
>> dtsi files.
>
> This part is slightly confusing though.
>
> What exactly is the GXL vs. GXM difference that this can't be handled by
> overriding node properties compatible/interrupts/clocks? I am missing a
> GXM patch in this series as rationale for doing it this way.
>
> In particular I am wondering whether the whole GXM-inherits-from-GXL
> concept is flawed and should be adjusted if this leads to secondary
> .dtsi files like this: My proposal would be to instead create a
> meson-gxl-gxm.dtsi, that meson-gxl.dtsi and meson-gxm.dtsi can inherit
> the current common parts from, then the Mali bits can simply go into
> meson-gxl.dtsi without extra #includes needed in S905X and S905D. While
> it's slightly more work to split once again, I think it would be cleaner.
The GXL and GXM differences are very small :
- They share the same clock tree
- They share the same pinctrl and even the same pinout (S905D and S912 are pin-to-pin compatible)
- They share all the peripherals
The only changes are :
- Enhanced video encoding and decoding support, this will need a family-specific compatible when pushed
- Slightly differences in the Video Processing Unit, this is why I introduced family-specific compatibles
- A secondary Cortex-A53 cluster
- A secondary SCPI cpufreq clock entry
- A different Mali core, but with the same interrupts (less but they share the same lower interrupts), clocks and memory space
This is why it was decided to have a sub-dtsi, having a secondary dtsi will simply copy 99% of the GXL dtsi,
but surely we could also have an intermediate dtsi but for boards I'm ok with it, but less for a SoC dtsi,
since it could lead to some confusion.
Finally, yes I could have added the mali node to the GXL dtsi, but the midgard Mali dt-bindings are not upstream
and the family is too big and recent enough to consider having stable bindings for now.
Nevertheless, nothing is final, this gxl-mali.dtsi could be merged into the GXL dtsi in the future when we
have proper dt-bindings and a real support of the T820 Mali on the S912.
Kevin, what's your thought about this ?
Neil
> Regards,
> Andreas
>
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 37 ++++++++++++++++++++
>> arch/arm64/boot/dts/amlogic/meson-gxl-mali.dtsi | 43 ++++++++++++++++++++++++
>> arch/arm64/boot/dts/amlogic/meson-gxl-s905d.dtsi | 1 +
>> arch/arm64/boot/dts/amlogic/meson-gxl-s905x.dtsi | 1 +
>> 4 files changed, 82 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxl-mali.dtsi
> [...]
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl-s905d.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl-s905d.dtsi
>> index 615308e..5a90e30 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-gxl-s905d.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-gxl-s905d.dtsi
>> @@ -42,6 +42,7 @@
>> */
>>
>> #include "meson-gxl.dtsi"
>> +#include "meson-gxl-mali.dtsi"
>>
>> / {
>> compatible = "amlogic,s905d", "amlogic,meson-gxl";
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl-s905x.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl-s905x.dtsi
>> index 08237ee..0f78d83 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-gxl-s905x.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-gxl-s905x.dtsi
>> @@ -42,6 +42,7 @@
>> */
>>
>> #include "meson-gxl.dtsi"
>> +#include "meson-gxl-mali.dtsi"
>>
>> / {
>> compatible = "amlogic,s905x", "amlogic,meson-gxl";
>
next prev parent reply other threads:[~2017-03-02 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 10:46 [PATCH v2 0/3] meson-gx: Add mali-450 support Neil Armstrong
2017-03-01 10:46 ` [PATCH v2 1/3] clk: meson-gxbb: Add MALI clock IDS Neil Armstrong
2017-03-01 10:46 ` [PATCH v2 2/3] clk: meson-gxbb: Add MALI clocks Neil Armstrong
2017-03-01 19:11 ` Stephen Boyd
2017-03-02 11:07 ` Neil Armstrong
2017-03-02 11:28 ` Jerome Brunet
2017-03-01 10:46 ` [PATCH v2 3/3] ARM64: dts: meson-gx: Add MALI nodes for GXBB and GXL Neil Armstrong
2017-03-02 12:31 ` Andreas Färber
2017-03-02 12:47 ` Neil Armstrong [this message]
2017-03-02 17:45 ` Andreas Färber
2017-03-03 19:29 ` Kevin Hilman
2017-03-04 12:38 ` Andreas Färber
2017-03-06 8:58 ` Neil Armstrong
2017-03-06 17:27 ` Kevin Hilman
2017-03-07 10:36 ` Neil Armstrong
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=e80d9fb0-1d71-7cab-5e32-72316474fdfc@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®