From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>, Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: rockchip: add new ARCH_ROCKCHIP_{V7,V8} symbols
Date: Fri, 14 Jan 2022 10:33:25 +0100 [thread overview]
Message-ID: <176bb9ec-8382-de2e-5109-17d519730aa8@pengutronix.de> (raw)
In-Reply-To: <20220114092128.GT26619@pengutronix.de>
On 14.01.22 10:21, Sascha Hauer wrote:
> On Fri, Jan 14, 2022 at 09:38:23AM +0100, Ahmad Fatoum wrote:
>> In preparation for adding rk3399 support, which is another SoC with
>> ARMv8 CPUs, add new ARCH_ROCKCHIP_{V7,V8} symbols for the common
>> functionality.
>>
>> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
>> ---
>> arch/arm/mach-rockchip/Kconfig | 18 ++++++++++++------
>> arch/arm/mach-rockchip/Makefile | 5 +++--
>> 2 files changed, 15 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig
>> index 2e855714f7da..596de663f9e3 100644
>> --- a/arch/arm/mach-rockchip/Kconfig
>> +++ b/arch/arm/mach-rockchip/Kconfig
>> @@ -12,24 +12,30 @@ config RK_TIMER
>> hex
>> default 1
>>
>> -config ARCH_RK3188
>> +config ARCH_ROCKCHIP_V7
>> bool
>> select CPU_V7
>> select ARM_SMP_TWD
>> select ARCH_HAS_L2X0
>>
>> +config ARCH_RK3188
>> + bool
>> + select ARCH_ROCKCHIP_V7
>> +
>> config ARCH_RK3288
>> bool
>> - select CPU_V7
>> - select ARM_SMP_TWD
>> - select ARCH_HAS_L2X0
>> + select ARCH_ROCKCHIP_V7
>> select CLOCKSOURCE_ROCKCHIP
>>
>> -config ARCH_RK3568
>> +config ARCH_ROCKCHIP_V8
>> bool
>> select CPU_V8
>> - select ARM_ATF
>> select SYS_SUPPORTS_64BIT_KERNEL
>> + select ARM_ATF
>> +
>> +config ARCH_RK3568
>> + bool
>> + select ARCH_ROCKCHIP_V8
>>
>> comment "select Rockchip boards:"
>>
>> diff --git a/arch/arm/mach-rockchip/Makefile b/arch/arm/mach-rockchip/Makefile
>> index 72bf77c1e124..474b8629d13f 100644
>> --- a/arch/arm/mach-rockchip/Makefile
>> +++ b/arch/arm/mach-rockchip/Makefile
>> @@ -1,9 +1,10 @@
>> # SPDX-License-Identifier: GPL-2.0-only
>>
>> obj-y += rockchip.o
>> -pbl-$(CONFIG_ARCH_RK3568) += atf.o
>> +pbl-$(CONFIG_ARCH_ROCKCHIP_V8) += atf.o
>> obj-$(CONFIG_ARCH_RK3188) += rk3188.o
>> obj-$(CONFIG_ARCH_RK3288) += rk3288.o
>> +obj-pbl-$(CONFIG_ARCH_RK3399) += rk3399.o
>
> We don't have this yet, removed this hunk while applying.
Thanks, missed that during the rebase. I want to polish that
a bit before sending out in the following weeks.
Thanks,
Ahmad
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-01-14 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 8:38 Ahmad Fatoum
2022-01-14 8:38 ` [PATCH 2/3] ARM64: rockchip: add config symbol for ARMv8-based rk3399 SoC Ahmad Fatoum
2022-01-14 8:38 ` [PATCH 3/3] clk: rockchip: extend for rk3399 support Ahmad Fatoum
2022-01-14 9:21 ` [PATCH 1/3] ARM: rockchip: add new ARCH_ROCKCHIP_{V7,V8} symbols Sascha Hauer
2022-01-14 9:33 ` Ahmad Fatoum [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=176bb9ec-8382-de2e-5109-17d519730aa8@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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