From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 24 Jan 2020 13:30:13 -0500 Subject: [PATCH v2 0/7] Add Cortina Access basic DM drivers In-Reply-To: <84ED7BF2-CF79-4F2C-936C-289CDC4DFCCF@cortina-access.com> References: <1579601912-27737-1-git-send-email-alex.nemirovsky@cortina-access.com> <20200124151330.GQ26536@bill-the-cat> <13D32E42-263A-4922-AF73-F5D284EA1295@cortina-access.com> <20200124173714.GT26536@bill-the-cat> <84ED7BF2-CF79-4F2C-936C-289CDC4DFCCF@cortina-access.com> Message-ID: <20200124183013.GU26536@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On Fri, Jan 24, 2020 at 05:55:29PM +0000, Alex Nemirovsky wrote: > Looking inside > grep -h CA board/cortina/common/armv8/lowlevel_init.S > #if defined(CONFIG_SOC_CA7774) > #if defined(CONFIG_SOC_CA8277B) >=20 > as we understand it, the alternative would lead to maintaining duplicate = but slightly different code for each ARM based SoC in > arch/arm/mach-ca7774 > arch/arm/mach-ca8277B > arch/arm/mach-ca7742 > arch/arm/mach-ca8279 > arch/arm/mach-caXnnn >=20 > correct? or should we simply create a arch/arm/mach-caxxxx, arch/mips/ma= ch-caxxxx, arch/xtensa/mach-axxxx, arch/riscv/mach-caxxxx, etc to maintain= similar > changes to each arch related custom code which varies slightly for each S= oC variation within each architecture? > What=E2=80=99s best to avoid maintaining duplicate code across SoC variat= ions within the same ISA family? I would hope we can get by with arch/arm/mach-caxxxx or so and board/cortina/common/. How are you handling common code in the linux kernel? --=20 Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: