From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: devicetree@vger.kernel.org,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Will Deacon" <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files
Date: Wed, 4 Nov 2020 07:09:08 -0800 [thread overview]
Message-ID: <12213635-05d2-ec04-7ba1-ea00e0f8a981@gmail.com> (raw)
In-Reply-To: <10118193-225a-05a8-e73d-7370e1866ea2@gmail.com>
On 11/4/2020 4:07 AM, Rafał Miłecki wrote:
> On 04.11.2020 11:35, Robin Murphy wrote:
>> On 2020-10-28 10:11, Rafał Miłecki wrote:
>> [...]
>>> + cpu0: cpu@0 {
>>> + device_type = "cpu";
>>> + compatible = "brcm,cortex-b53", "arm,cortex-a53";
>>
>> Erm, there's no binding for that - did you mean "brcm,brahma-b53"?
>
> I'm not sure if that's the same thing. Unfortunately I don't have access to
> any Broadcom documentation.
>
> Florian: could you try to verify that, please?
It should be "brcm,brahma-b53", that is the CPU design that this SoC uses.
--
Florian
prev parent reply other threads:[~2020-11-04 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 10:11 [PATCH 1/2] arm64: add config for Broadcom BCM4908 SoCs Rafał Miłecki
2020-10-28 10:11 ` [PATCH 2/2] arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files Rafał Miłecki
2020-11-04 3:33 ` Florian Fainelli
2020-11-04 8:02 ` Rafał Miłecki
2020-11-04 12:21 ` Rafał Miłecki
2020-11-04 10:35 ` Robin Murphy
2020-11-04 12:07 ` Rafał Miłecki
2020-11-04 15:09 ` Florian Fainelli [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=12213635-05d2-ec04-7ba1-ea00e0f8a981@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).