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 v3 0/6] OpenRISC de0 nano single and multicore boards
Date: Fri, 9 Jan 2026 13:43:51 +0000 [thread overview]
Message-ID: <20260109134409.2153333-1-shorne@gmail.com> (raw)
Since v2:
- Fixup gpio-mmio patch to update driver compatible list and just
add opencores,gpio to mmio-gpio bindings. Discussed with Geert and
Linus W [1].
- Update new device trees to use proper ordering, remove debug options, remove
unneeded "status" properties. Suggested by Geert.
Since v1:
- Use proper schema in gpio-mmio suggsted by Conor Dooley
- Remove 0 clock-frequency definitions in dtsi file
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 [2] 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.
[1] https://lore.kernel.org/lkml/20251217080843.70621-1-shorne@gmail.com/
[2] https://openrisc.io/tutorials/
Stafford Horne (6):
gpio: mmio: Add compatible for opencores GPIO
dt-bindings: gpio-mmio: Add opencores GPIO
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 | 9 ++
arch/openrisc/boot/dts/de0-nano-common.dtsi | 42 +++++++++
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} | 11 +--
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/gpio/gpio-mmio.c | 1 +
drivers/irqchip/irq-ompic.c | 15 ++-
drivers/irqchip/irq-or1k-pic.c | 27 +++++-
14 files changed, 393 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} (90%)
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:[~2026-01-09 13:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 13:43 Stafford Horne [this message]
2026-01-09 13:43 ` [PATCH v3 1/6] gpio: mmio: Add compatible for opencores GPIO Stafford Horne
2026-01-09 23:19 ` Linus Walleij
2026-01-10 14:03 ` Geert Uytterhoeven
2026-01-09 13:43 ` [PATCH v3 2/6] dt-bindings: gpio-mmio: Add " Stafford Horne
2026-01-09 23:20 ` Linus Walleij
2026-01-10 14:03 ` Geert Uytterhoeven
2026-01-11 10:18 ` Krzysztof Kozlowski
2026-01-11 16:46 ` Stafford Horne
2026-01-12 7:31 ` Krzysztof Kozlowski
2026-01-12 8:32 ` Stafford Horne
2026-01-11 10:20 ` Krzysztof Kozlowski
2026-01-11 16:34 ` Stafford Horne
2026-01-12 7:32 ` Krzysztof Kozlowski
2026-01-09 13:43 ` [PATCH v3 3/6] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2026-01-09 13:43 ` [PATCH v3 4/6] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2026-01-09 13:43 ` [PATCH v3 5/6] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2026-01-09 13:43 ` [PATCH v3 6/6] 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=20260109134409.2153333-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox