All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: u-boot@lists.denx.de, git@xilinx.com,
	Conor Dooley <conor.dooley@microchip.com>,
	Leo <ycliang@andestech.com>, Randolph <randolph@andestech.com>,
	Rick Chen <rick@andestech.com>, Wei Fu <wefu@redhat.com>,
	Yanhong Wang <yanhong.wang@starfivetech.com>,
	Yixun Lan <dlan@gentoo.org>
Subject: Re: [PATCH] riscv: Add support for AMD/Xilinx MicroBlaze V
Date: Fri, 3 Nov 2023 16:25:47 +0000	[thread overview]
Message-ID: <20231103-shell-those-d0776d5c2e41@spud> (raw)
In-Reply-To: <41c2fda5d6f96e44188d912811a63b8a40625e6e.1699027398.git.michal.simek@amd.com>

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Yo,

Since you sent it to me, I may as well comment...

On Fri, Nov 03, 2023 at 05:03:25PM +0100, Michal Simek wrote:
> MicroBlaze V is new AMD/Xilinx soft-core 32bit RISC-V processor IP.
> It is hardware compatible with classic MicroBlaze processor.
> 
> The patch contains initial wiring and configuration for initial HW design
> with memory, cpu, interrupt controller, timers and uartlite console.
> 
> Provided DT is just describing one configuration and should be taken only
> as example.


> @@ -0,0 +1,86 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * dts file for Xilinx MicroBlaze V
> + *
> + * (C) Copyright 2023, Advanced Micro Devices, Inc.
> + *
> + * Michal Simek <michal.simek@amd.com>
> + */
> +
> +/dts-v1/;
> +/ {
> +	#address-cells = <1>;
> +	#size-cells = <1>;
> +	model = "Xilinx MicroBlaze V 32bit";
> +	compatible = "xlnx,mbv32";
> +
> +	cpus: cpus {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +		timebase-frequency = <102000000>;
> +		cpu_0: cpu@0 {
> +			device_type = "cpu";
> +			compatible = "riscv";

You're missing a cpu specific compatible here.
"riscv" in isolation is only for {emu,simu}lators.

> +			reg = <0>;
> +			status = "okay";
> +			riscv,isa = "rv32imafdc";
> +			clock-frequency = <100000000>;
> +			i-cache-size = <32768>;
> +			d-cache-size = <32768>;

Missing an interrupt-controller child node for the cpu-intc, no?

> +		};
> +	};
> +
> +	aliases {
> +		serial0 = &uart0;
> +	};
> +
> +	chosen {
> +		bootargs = "earlycon";
> +		stdout-path = "serial0:115200n8";
> +	};
> +
> +	memory@20000000 {
> +		device_type = "memory";
> +		reg = <0x20000000 0x20000000>;
> +	};
> +
> +	axi: axi {
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		compatible = "simple-bus";
> +		ranges;
> +		bootph-all;
> +
> +		axi_intc: interrupt-controller@41200000 {
> +			compatible = "xlnx.xps-intc";

This is some non-standard interrupt controller, rather than a plic,
right?

Also, should you not also have a riscv,timer node?

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-03 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 16:03 [PATCH] riscv: Add support for AMD/Xilinx MicroBlaze V Michal Simek
2023-11-03 16:25 ` Conor Dooley [this message]
2023-11-06 11:53   ` Michal Simek

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=20231103-shell-those-d0776d5c2e41@spud \
    --to=conor@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=dlan@gentoo.org \
    --cc=git@xilinx.com \
    --cc=michal.simek@amd.com \
    --cc=randolph@andestech.com \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=wefu@redhat.com \
    --cc=yanhong.wang@starfivetech.com \
    --cc=ycliang@andestech.com \
    /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.