From: Krzysztof Kozlowski <krzk@kernel.org>
To: Emekcan Aras <emekcan.aras@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Miguel Silva <rui.silva@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] arm: dts: arm: add arm corstone500 device tree
Date: Fri, 23 Dec 2022 09:26:54 +0100 [thread overview]
Message-ID: <36611392-5bdd-4f08-6748-d36c6ffcd470@kernel.org> (raw)
In-Reply-To: <20221222123244.147238-2-emekcan.aras@arm.com>
On 22/12/2022 13:32, Emekcan Aras wrote:
> Corstone500[0] is a platform from arm, which includes Cortex-A cores and
> ideal starting point for feature rich System on Chip (SoC) designs
> based on the Cortex-A5 core.
>
> These device trees contains the necessary bits to support the
> Corstone 500 FVP (Fixed Virtual Platform) and the
> FPGA MPS3 board.
>
> 0: https://developer.arm.com/documentation/102262/0000
>
> Signed-off-by: Emekcan Aras <emekcan.aras@arm.com>
> ---
> arch/arm/boot/dts/Makefile | 3 +-
> arch/arm/boot/dts/corstone500.dts | 182 ++++++++++++++++++++++++++++++
> 2 files changed, 184 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm/boot/dts/corstone500.dts
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index 6aa7dc4db2fc..4dc4df0707dc 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -1465,7 +1465,8 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += \
> vexpress-v2p-ca5s.dtb \
> vexpress-v2p-ca9.dtb \
> vexpress-v2p-ca15-tc1.dtb \
> - vexpress-v2p-ca15_a7.dtb
> + vexpress-v2p-ca15_a7.dtb \
> + corstone500.dtb
Why this is vexpress platform? If it is true, then add it to vexpress
bindings... It's confusingi and looks disorganized - some bindings here,
some platform there. Who is overseeing it? Who is maintaining? Who keeps
it consistent with other Arm platforms?
> dtb-$(CONFIG_ARCH_VIRT) += \
> xenvm-4.2.dtb
> dtb-$(CONFIG_ARCH_VT8500) += \
> diff --git a/arch/arm/boot/dts/corstone500.dts b/arch/arm/boot/dts/corstone500.dts
> new file mode 100644
> index 000000000000..bcca7d736c85
> --- /dev/null
> +++ b/arch/arm/boot/dts/corstone500.dts
> @@ -0,0 +1,182 @@
> +// SPDX-License-Identifier: GPL-2.0 or MIT
> +/*
> + * Copyright (c) 2022, Arm Limited. All rights reserved.
> + *
> + */
> +
> +
kbuild reports that patch does not build. :(
Except that other topics which you did not solve from previous case:
1. Missing maintainers entry
2. One binding file for your Corstone platforms, not for each of it.
3. failing `dtbs_check` (at least failing due to non-compiling DTS).
4. Subject prefix not matching other arm platforms.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-23 8:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:32 [PATCH v3 0/2] adds corstone500 device tree Emekcan Aras
2022-12-22 12:32 ` [PATCH v3 1/2] arm: dts: arm: add arm " Emekcan Aras
2022-12-22 14:01 ` Krzysztof Kozlowski
[not found] ` <DBBPR08MB4838C52E20C5D6D0558FAA888EE89@DBBPR08MB4838.eurprd08.prod.outlook.com>
2022-12-22 15:24 ` Krzysztof Kozlowski
2022-12-22 22:20 ` kernel test robot
2022-12-23 0:01 ` kernel test robot
2022-12-23 8:26 ` Krzysztof Kozlowski [this message]
2022-12-23 11:14 ` Emekcan Aras
2022-12-30 23:24 ` kernel test robot
2022-12-22 12:32 ` [PATCH v3 2/2] dt-bindings: Add Arm corstone500 platform Emekcan Aras
2022-12-22 13:59 ` Krzysztof Kozlowski
2022-12-22 18:49 ` Rob Herring
2022-12-22 13:58 ` [PATCH v3 0/2] adds corstone500 device tree Krzysztof Kozlowski
2022-12-22 14:06 ` Krzysztof Kozlowski
2022-12-22 18:58 ` Rob Herring
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=36611392-5bdd-4f08-6748-d36c6ffcd470@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emekcan.aras@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.silva@linaro.org \
--cc=sudeep.holla@arm.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).