From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V4 3/3] arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files
Date: Tue, 24 Nov 2020 14:41:35 -0800 [thread overview]
Message-ID: <20201124224135.2256474-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20201112150832.26474-3-zajec5@gmail.com>
On Thu, 12 Nov 2020 16:08:32 +0100, Rafał Miłecki <zajec5@gmail.com> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> They don't descibe hardware fully yet but it's enough to boot a system.
>
> Some missing blocks:
> 1. PMC (Power Management Controller?)
> 2. Ethernet
> 3. Crypto
> 4. Thermal
>
> Asus DTS is missing defining full NAND partitions layout and buttons.
>
> Further changes will fill those gaps as soon as required bindings will
> be found / tested / added.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
Applied to devicetree-arm64/next, thanks!
--
Florian
next prev parent reply other threads:[~2020-11-24 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 15:08 [PATCH V4 1/3] arm64: add config for Broadcom BCM4908 SoCs Rafał Miłecki
2020-11-12 15:08 ` [PATCH V4 2/3] dt-bindings: arm: bcm: document BCM4908 bindings Rafał Miłecki
2020-11-24 22:41 ` Florian Fainelli
2020-11-25 4:20 ` Florian Fainelli
2020-11-12 15:08 ` [PATCH V4 3/3] arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files Rafał Miłecki
2020-11-24 22:41 ` Florian Fainelli [this message]
2020-11-24 22:41 ` [PATCH V4 1/3] arm64: add config for Broadcom BCM4908 SoCs Florian Fainelli
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=20201124224135.2256474-1-f.fainelli@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=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).