From: Stafford Horne <shorne@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/5] openrisc: dts: Add de0 nano config and devicetree
Date: Sat, 3 Jan 2026 06:16:59 +0000 [thread overview]
Message-ID: <aVi0W6syzK6buL_v@antec> (raw)
In-Reply-To: <CAMuHMdVCY=5UypK65Ver6UZM_m6DZuw9mhfANMx4+Y6PgNAdmA@mail.gmail.com>
On Thu, Dec 18, 2025 at 07:36:08PM +0100, Geert Uytterhoeven wrote:
> Hi Stafford,
>
> On Wed, 17 Dec 2025 at 09:23, Stafford Horne <shorne@gmail.com> wrote:
> > The de0 nano from Terasic is an FPGA board that we use in the OpenRISC
> > community to test OpenRISC configurations. Add a base configuration for
> > the board that runs an OpenRISC CPU at 50Mhz with 32MB ram, UART for
> > console and some GPIOs for LEDs and switches.
> >
> > There is an older version of this floating around that defines all of
> > the hardware on the board including SPI's, flash devices, sram, ADCs
> > etc. Eventually it would be good to get the full version upstream
> > but for now I think a minimal board is good to start with.
> >
> > Link: https://openrisc.io/tutorials/de0_nano/
> > Link: https://github.com/olofk/de0_nano
> >
> > Signed-off-by: Stafford Horne <shorne@gmail.com>
>
> Thanks for your patch!
>
> > --- /dev/null
> > +++ b/arch/openrisc/boot/dts/de0-nano-common.dtsi
> > @@ -0,0 +1,41 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +#include <dt-bindings/gpio/gpio.h>
> > +#include <dt-bindings/leds/common.h>
> > +
> > +/ {
> > + memory@0 {
> > + device_type = "memory";
> > + reg = <0x00000000 0x02000000>;
> > + };
> > +
> > + leds: leds {
>
> Move this up (or down), before (or after) all nodes with unit addresses?
OK.
> > + compatible = "gpio-leds";
> > + status = "okay";
>
> Missing blank line.
OK, also I can remove the "okay" line as well.
> > + led-heartbeat {
> > + gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>;
> > + color = <LED_COLOR_ID_GREEN>;
> > + function = LED_FUNCTION_HEARTBEAT;
> > + linux,default-trigger = "heartbeat";
> > + label = "heartbeat";
> > + };
> > + };
> > +
> > + gpio0: gpio@91000000 {
> > + compatible = "opencores,gpio", "brcm,bcm6345-gpio";
> > + reg = <0x91000000 0x1>, <0x91000001 0x1>;
> > + reg-names = "dat", "dirout";
> > + gpio-controller;
> > + #gpio-cells = <2>;
> > + status = "okay";
>
> "okay" is the default, so you could drop this line.
OK.
> > + };
> > +
> > + gpio1: gpio@92000000 {
> > + compatible = "opencores,gpio", "brcm,bcm6345-gpio";
> > + reg = <0x92000000 0x1>, <0x92000001 0x1>;
> > + reg-names = "dat", "dirout";
> > + gpio-controller;
> > + #gpio-cells = <2>;
> > + status = "disabled";
> > + };
> > +};
>
> > --- /dev/null
> > +++ b/arch/openrisc/boot/dts/de0-nano.dts
> > @@ -0,0 +1,54 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +/dts-v1/;
> > +
> > +#include "de0-nano-common.dtsi"
> > +
> > +/ {
> > + model = "Terasic DE0 Nano";
> > + compatible = "opencores,or1ksim";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + interrupt-parent = <&pic>;
> > +
> > + aliases {
> > + uart0 = &serial0;
> > + };
> > +
> > + chosen {
> > + bootargs = "earlycon";
>
> Do you need this?
What do you mean here? I want to keep "earlycon", and it is not supplied in
de0-nano-common.dtsi.
> > + stdout-path = "uart0:115200";
> > + };
> > +
> > + cpus {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
>
> Missing blank line.
OK.
> > + cpu@0 {
> > + compatible = "opencores,or1200-rtlsvn481";
> > + reg = <0>;
> > + clock-frequency = <50000000>;
> > + };
> > + };
> > +
> > + /*
> > + * OR1K PIC is built into CPU and accessed via special purpose
> > + * registers. It is not addressable and, hence, has no 'reg'
> > + * property.
> > + */
> > + pic: pic {
> > + compatible = "opencores,or1k-pic";
> > + #interrupt-cells = <1>;
> > + interrupt-controller;
> > + };
> > +
> > + serial0: serial@90000000 {
> > + compatible = "opencores,uart16550-rtlsvn105", "ns16550a";
> > + reg = <0x90000000 0x100>;
> > + interrupts = <2>;
> > + clock-frequency = <50000000>;
> > + };
> > +};
-Stafford
next prev parent reply other threads:[~2026-01-03 6:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 8:08 [PATCH v2 0/5] OpenRISC de0 nano single and multicore boards Stafford Horne
2025-12-17 8:08 ` [PATCH v2 1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio Stafford Horne
2025-12-18 0:55 ` Conor Dooley
2026-01-03 5:55 ` Stafford Horne
2026-01-07 14:17 ` Linus Walleij
2026-01-07 14:35 ` Geert Uytterhoeven
2026-01-08 8:20 ` Stafford Horne
2026-01-08 8:41 ` Geert Uytterhoeven
2026-01-09 10:07 ` Linus Walleij
2026-01-09 10:19 ` Geert Uytterhoeven
2026-01-09 12:51 ` Stafford Horne
2026-01-12 9:25 ` Bartosz Golaszewski
2026-01-13 16:17 ` Stafford Horne
2025-12-17 8:08 ` [PATCH v2 2/5] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2025-12-18 18:36 ` Geert Uytterhoeven
2026-01-03 6:16 ` Stafford Horne [this message]
2026-01-05 11:02 ` Geert Uytterhoeven
2026-01-06 9:54 ` Stafford Horne
2026-01-06 10:18 ` Geert Uytterhoeven
2026-01-08 7:50 ` Stafford Horne
2025-12-17 8:08 ` [PATCH v2 3/5] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2025-12-17 8:08 ` [PATCH v2 4/5] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2025-12-18 18:37 ` Geert Uytterhoeven
2026-01-03 6:13 ` Stafford Horne
2025-12-17 8:08 ` [PATCH v2 5/5] openrisc: dts: Add de0 nano multicore config and devicetree Stafford Horne
2025-12-18 13:46 ` (subset) [PATCH v2 0/5] OpenRISC de0 nano single and multicore boards Bartosz Golaszewski
2026-01-11 16:39 ` 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=aVi0W6syzK6buL_v@antec \
--to=shorne@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jonas@southpole.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stefan.kristiansson@saunalahti.fi \
/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