From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/5] OpenRISC de0 nano single and multicore boards
Date: Sun, 14 Dec 2025 18:01:40 +0000 [thread overview]
Message-ID: <20251214180158.3955285-1-shorne@gmail.com> (raw)
The patches add support for OpenRISC systems running on the De0 Nano FPGA
development board. We have two SoCs which are available here:
- https://github.com/olofk/de0_nano - Single core
- https://github.com/stffrdhrn/de0_nano-multicore - Multicore
As I work on tutorials to help other get started with OpenRISC I would like to
have these defconfig and devicetree definitions in the upstream kernel to avoid
losing them.
When I was working on resurrecting these old setup's I found a major bug in
OpenRISC SMP which is fixed in this series as well.
Link: https://openrisc.io/tutorials/
Stafford Horne (5):
dt-bindings: Add compatible string opencores,gpio to gpio-mmio
openrisc: dts: Add de0 nano config and devicetree
openrisc: Fix IPIs on simple multicore systems
openrisc: dts: Split simple smp dts to dts and dtsi
openrisc: dts: Add de0 nano multicore config and devicetree
.../devicetree/bindings/gpio/gpio-mmio.yaml | 1 +
arch/openrisc/boot/dts/de0-nano-common.dtsi | 41 +++++++++
arch/openrisc/boot/dts/de0-nano-multicore.dts | 25 +++++
arch/openrisc/boot/dts/de0-nano.dts | 54 +++++++++++
arch/openrisc/boot/dts/simple-smp.dts | 25 +++++
.../dts/{simple_smp.dts => simple-smp.dtsi} | 12 +--
arch/openrisc/configs/de0_nano_defconfig | 79 ++++++++++++++++
.../configs/de0_nano_multicore_defconfig | 92 +++++++++++++++++++
arch/openrisc/configs/simple_smp_defconfig | 2 +-
arch/openrisc/include/asm/smp.h | 3 +-
arch/openrisc/kernel/smp.c | 22 ++++-
drivers/irqchip/irq-ompic.c | 15 ++-
drivers/irqchip/irq-or1k-pic.c | 27 +++++-
13 files changed, 384 insertions(+), 14 deletions(-)
create mode 100644 arch/openrisc/boot/dts/de0-nano-common.dtsi
create mode 100644 arch/openrisc/boot/dts/de0-nano-multicore.dts
create mode 100644 arch/openrisc/boot/dts/de0-nano.dts
create mode 100644 arch/openrisc/boot/dts/simple-smp.dts
rename arch/openrisc/boot/dts/{simple_smp.dts => simple-smp.dtsi} (89%)
create mode 100644 arch/openrisc/configs/de0_nano_defconfig
create mode 100644 arch/openrisc/configs/de0_nano_multicore_defconfig
--
2.51.0
next reply other threads:[~2025-12-14 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 18:01 Stafford Horne [this message]
2025-12-14 18:01 ` [PATCH 1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio Stafford Horne
2025-12-15 16:57 ` Conor Dooley
2025-12-15 18:40 ` Stafford Horne
2025-12-15 19:34 ` Stafford Horne
2025-12-16 0:05 ` Conor Dooley
2025-12-14 18:01 ` [PATCH 2/5] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2025-12-14 18:01 ` [PATCH 3/5] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2025-12-14 18:01 ` [PATCH 4/5] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2025-12-15 7:30 ` Stafford Horne
2025-12-15 16:58 ` Conor Dooley
2025-12-15 18:19 ` Stafford Horne
2025-12-14 18:01 ` [PATCH 5/5] openrisc: dts: Add de0 nano multicore config and devicetree Stafford Horne
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=20251214180158.3955285-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.