From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [1/4] arm64: Broadcom Vulcan support
Date: Fri, 19 Feb 2016 11:24:57 -0800 [thread overview]
Message-ID: <56C76C09.50800@gmail.com> (raw)
In-Reply-To: <0c75ddd6-d353-bb73-62e4-bae0ff95a3b0@broadcom.com>
On 18/02/16 10:15, Ray Jui wrote:
> + bcm-kernel-feedback-list mailing list
>
> On 2/13/2016 10:46 AM, Jayachandran C. wrote:
>> From: Zi Shen Lim <zlim@broadcom.com>
>>
>> Add a configuration option and a device tree for Broadcom's Vulcan
>> ARM64 processor. brcm-vulcan.dtsi has the on-chip blocks like the
>> PCIe controller, GICv3 with ITS, PMU, system timer and pl011 UART.
>> brcm-vulcan-eval.dts has definitions for a basic evaluation board.
>> The firmware supports PSCI 0.2 for cpu wakeup.
>>
>> Signed-off-by: Zi Shen Lim <zlim@broadcom.com>
>> [ updated and split dts - jchandra at broadcom.com ]
>> Signed-off-by: Jayachandran C <jchandra@broadcom.com>
>>
>> ---
>> arch/arm64/Kconfig.platforms | 5 +
>> arch/arm64/boot/dts/broadcom/Makefile | 1 +
>> arch/arm64/boot/dts/broadcom/brcm-vulcan-eval.dts | 33 +++++
>> arch/arm64/boot/dts/broadcom/brcm-vulcan.dtsi | 146
>> ++++++++++++++++++++++
>> 4 files changed, 185 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/broadcom/brcm-vulcan-eval.dts
>> create mode 100644 arch/arm64/boot/dts/broadcom/brcm-vulcan.dtsi
>
> Could you please name the files "vulcan.dtsi" and "vulcan-eval.dts" so
> it's consistent with the rest of files in the same directory?
I would like to take these patches ASAP so I can include them in our
upcoming 4.6 pull requests, can you do a quick respin adressing Ray's
feedback and adding a MAINTAINERS file?
Thanks!
--
Florian
next prev parent reply other threads:[~2016-02-19 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 18:46 [PATCH 0/4] Support for Broadcom Vulcan ARM64 processor Jayachandran C
2016-02-13 18:46 ` [PATCH 1/4] arm64: Broadcom Vulcan support Jayachandran C
2016-02-17 1:22 ` Florian Fainelli
2016-02-17 17:16 ` Mark Rutland
2016-02-19 6:58 ` Jayachandran Chandrashekaran Nair
2016-02-18 18:15 ` [1/4] " Ray Jui
2016-02-19 19:24 ` Florian Fainelli [this message]
2016-02-13 18:46 ` [PATCH 2/4] dt-bindings: Add documentation for Broadcom Vulcan Jayachandran C
2016-02-17 17:17 ` Mark Rutland
2016-02-13 18:46 ` [PATCH 3/4] arm64: defconfig: Add Broadcom Vulcan to defconfig Jayachandran C
2016-02-13 18:46 ` [PATCH 4/4] arm64: cputype info for Broadcom Vulcan Jayachandran C
2016-02-15 10:12 ` Will Deacon
2016-02-17 1:16 ` Florian Fainelli
2016-02-17 17:26 ` Catalin Marinas
2016-02-17 7:32 ` Zi Shen Lim
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=56C76C09.50800@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).