From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/7] Add Cortina Access basic DM drivers
Date: Fri, 24 Jan 2020 13:30:13 -0500 [thread overview]
Message-ID: <20200124183013.GU26536@bill-the-cat> (raw)
In-Reply-To: <84ED7BF2-CF79-4F2C-936C-289CDC4DFCCF@cortina-access.com>
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)
>
> 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
>
> correct? or should we simply create a arch/arm/mach-caxxxx, arch/mips/mach-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 SoC variation within each architecture?
> What’s best to avoid maintaining duplicate code across SoC variations 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?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200124/1dae24a1/attachment.sig>
next prev parent reply other threads:[~2020-01-24 18:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 10:19 [PATCH v2 0/7] Add Cortina Access basic DM drivers Alex Nemirovsky
2020-01-21 10:19 ` [PATCH v2 1/7] MAINTAINERS, git-mailrc: cortina: add Custodian for Cortina Access Inc Alex Nemirovsky
2020-01-21 10:19 ` [PATCH v2 2/7] cortina: common: armv8: add custom init for CA ARMv8 based SoCs Alex Nemirovsky
2020-01-21 10:19 ` [PATCH v2 3/7] gpio: do not include <asm/arch/gpio.h> for Cortina CAxxxx SoCs Alex Nemirovsky
2020-01-21 10:19 ` [PATCH v2 4/7] gpio: cortina_gpio: add DM_GPIO driver for " Alex Nemirovsky
2020-01-22 20:57 ` Daniel Schwierzeck
2020-01-21 10:19 ` [PATCH v2 5/7] watchdog: cortina_wdt: add support for HW WDT on " Alex Nemirovsky
2020-01-22 20:58 ` Daniel Schwierzeck
2020-01-21 10:19 ` [PATCH v2 6/7] serial: serial_cortina: add UART DM driver for " Alex Nemirovsky
2020-01-22 21:09 ` Daniel Schwierzeck
2020-01-21 10:19 ` [PATCH v2 7/7] board: presidio-asic: Add basic G3 engr. development board support Alex Nemirovsky
2020-01-22 21:24 ` Daniel Schwierzeck
2020-01-22 23:15 ` Alex Nemirovsky
2020-01-23 1:11 ` Alex Nemirovsky
2020-01-24 15:13 ` [PATCH v2 0/7] Add Cortina Access basic DM drivers Tom Rini
2020-01-24 17:22 ` Alex Nemirovsky
2020-01-24 17:37 ` Tom Rini
2020-01-24 17:55 ` Alex Nemirovsky
2020-01-24 18:30 ` Tom Rini [this message]
2020-01-24 18:34 ` Alex Nemirovsky
2020-01-24 18:42 ` Tom Rini
2020-01-24 18:58 ` Alex Nemirovsky
2020-01-24 19:52 ` Tom Rini
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=20200124183013.GU26536@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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