From: Conor Dooley <conor@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: Add new board description for MicroBlaze V
Date: Tue, 7 Nov 2023 21:18:16 +0000 [thread overview]
Message-ID: <20231107-expensive-jitters-92e454f77ea8@spud> (raw)
In-Reply-To: <4223470c-5596-4168-9c89-e701559fbbed@amd.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Tue, Nov 07, 2023 at 12:09:58PM +0100, Michal Simek wrote:
>
>
> On 11/6/23 18:07, Conor Dooley wrote:
> > On Mon, Nov 06, 2023 at 12:53:40PM +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. Processor can
> > > be used with standard AMD/Xilinx IPs including interrupt controller and
> > > timer.
> > >
> > > Signed-off-by: Michal Simek <michal.simek@amd.com>
> > > ---
> > >
> > > .../devicetree/bindings/soc/amd/amd.yaml | 26 +++++++++++++++++++
> >
> > Bindings for SoCs (and by extension boards with them) usually go to in
> > $arch/$vendor.yaml not into soc/$vendor/$vendor.yaml. Why is this any
> > different?
>
> I actually found it based on tracking renesas.yaml which describes one of
> risc-v board. No problem to move it under bindings/riscv/
That one is kinda a special case, as it contains arm/arm64/riscv.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-07 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:53 [PATCH] dt-bindings: soc: Add new board description for MicroBlaze V Michal Simek
2023-11-06 17:07 ` Conor Dooley
2023-11-07 11:09 ` Michal Simek
2023-11-07 11:27 ` Krzysztof Kozlowski
2023-11-07 12:09 ` Michal Simek
2023-11-07 12:38 ` Krzysztof Kozlowski
2023-11-07 21:36 ` Conor Dooley
2023-11-08 7:16 ` Michal Simek
2023-11-08 8:11 ` Krzysztof Kozlowski
2023-11-08 10:11 ` Michal Simek
2023-11-09 8:36 ` Krzysztof Kozlowski
2023-11-09 9:48 ` Michal Simek
2023-11-08 17:41 ` Rob Herring
2023-11-07 21:18 ` Conor Dooley [this message]
2023-11-08 10:06 ` Michal Simek
2023-11-08 10:12 ` Conor Dooley
2023-11-08 10:24 ` Michal Simek
2023-11-08 10:28 ` Conor Dooley
2023-11-08 11:05 ` 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=20231107-expensive-jitters-92e454f77ea8@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@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