From: slash.tmp@free•fr (Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: Steps to submit a new arch/arm port
Date: Mon, 21 Sep 2015 17:00:08 +0200 [thread overview]
Message-ID: <56001B78.2090001@free.fr> (raw)
Hello everyone,
I've been working on an arch/arm port for some time. I've removed
a lot of non-essential code, and currently, what I have is:
$ git diff --stat v4.2 my4.2
Makefile | 4 +-
arch/arm/Kconfig | 26 ++
arch/arm/Makefile | 1 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/tango.dts | 96 ++++++++
arch/arm/kernel/smp_twd.c | 3 +-
arch/arm/mach-tangox/Kconfig | 57 +++++
arch/arm/mach-tangox/Makefile | 10 +
arch/arm/mach-tangox/Makefile.boot | 3 +
arch/arm/mach-tangox/clock-tangox.c | 134 ++++++++++
arch/arm/mach-tangox/io.c | 18 ++
arch/arm/mach-tangox/setup.c | 22 ++
arch/arm/tools/mach-types | 1 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-tangox.c | 234 ++++++++++++++++++
drivers/net/ethernet/Kconfig | 1 +
drivers/net/ethernet/Makefile | 1 +
drivers/net/ethernet/sigmadesigns/Kconfig | 7 +
drivers/net/ethernet/sigmadesigns/Makefile | 5 +
drivers/net/ethernet/sigmadesigns/tangox/Kconfig | 21 ++
drivers/net/ethernet/sigmadesigns/tangox/Makefile | 5 +
drivers/net/ethernet/sigmadesigns/tangox/tangox_enet.c | 1158 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/net/ethernet/sigmadesigns/tangox/tangox_enet.h | 257 +++++++++++++++++++
drivers/tty/serial/8250/8250_core.c | 8 +-
drivers/tty/serial/of_serial.c | 2 +-
25 files changed, 2066 insertions(+), 10 deletions(-)
(The two drivers (irqchip and ethernet) are from Mans Rullgard's tree.)
TODO
Convert the clock registration code to device tree
Add PHY ISR to ethernet driver
Could you provide some pointers/links and guidance detailing the
steps required to submit a new port under arch/arm?
(With the current requirements: DT, ARCH_MULTIPLATFORM, etc)
Open questions:
1) Linux kernel runs in non-secure world. The port used to tweak
L2 cache configuration via custom SMC calls to the OS running in
secure world. I've removed that for now.
Is there a standard solution these days?
2) For now, only one core is enabled. The other core is supposed
to be enabled via custom SMC calls. Is there a standard solution
these days? A few months ago, ARM engineers suggested PSCI.
Are modern ports using that?
Regards.
next reply other threads:[~2015-09-21 15:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 15:00 Mason [this message]
2015-09-21 15:49 ` Steps to submit a new arch/arm port Arnd Bergmann
2015-09-22 14:36 ` Mason
2015-09-22 14:51 ` Arnd Bergmann
2015-09-22 14:56 ` Russell King - ARM Linux
2015-09-22 15:54 ` Mason
2015-09-22 16:29 ` Russell King - ARM Linux
2015-09-23 8:49 ` Mason
2015-09-23 9:13 ` Russell King - ARM Linux
2015-09-23 9:21 ` Mason
2015-09-23 9:26 ` Russell King - ARM Linux
2015-09-22 19:15 ` Arnd Bergmann
2015-09-23 9:26 ` Mason
2015-09-23 9:34 ` Arnd Bergmann
2015-09-25 13:06 ` Mason
2015-09-25 13:17 ` Arnd Bergmann
2015-09-25 13:35 ` Mason
2015-09-25 14:11 ` Arnd Bergmann
2015-09-25 15:28 ` Mason
2015-09-25 15:33 ` Mason
2015-09-25 15:49 ` Arnd Bergmann
2015-09-25 15:52 ` Arnd Bergmann
2015-09-25 16:09 ` Mason
2015-09-25 17:20 ` Arnd Bergmann
2015-09-28 13:48 ` Mason
2015-09-28 14:43 ` Måns Rullgård
2015-09-28 16:32 ` Mason
2015-09-28 17:29 ` Russell King - ARM Linux
2015-09-22 15:48 ` Måns Rullgård
2015-09-25 9:27 ` Mason
2015-09-25 9:46 ` Javier Martinez Canillas
2015-09-25 11:56 ` Arnd Bergmann
2015-09-25 12:06 ` Russell King - ARM Linux
2015-09-21 15:51 ` Måns Rullgård
2015-09-21 16:13 ` Russell King - ARM Linux
2015-09-22 16:08 ` Mason
2015-09-22 16:24 ` Russell King - ARM Linux
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=56001B78.2090001@free.fr \
--to=slash.tmp@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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