From: Michal Simek <michal.simek@amd.com>
To: Conor Dooley <conor@kernel.org>
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 12:09:58 +0100 [thread overview]
Message-ID: <4223470c-5596-4168-9c89-e701559fbbed@amd.com> (raw)
In-Reply-To: <20231106-hangnail-prankster-a04e713bed35@spud>
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/
>
>> 1 file changed, 26 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/soc/amd/amd.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/soc/amd/amd.yaml b/Documentation/devicetree/bindings/soc/amd/amd.yaml
>> new file mode 100644
>> index 000000000000..21adf28756fa
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/amd/amd.yaml
>> @@ -0,0 +1,26 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/soc/amd/amd.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: AMD Platforms
>> +
>> +maintainers:
>> + - Michal Simek <michal.simek@amd.com>
>> +
>> +description: |
>> + AMD boards with MicroBlaze V SOC
>> +
>> +properties:
>> + $nodename:
>> + const: '/'
>> + compatible:
>> + oneOf:
>> + - description: AMD MicroBlaze V
>> + items:
>> + - const: amd,mbv
>
> You don't actually list any boards here, but instead permit having only
> the SoC compatible and no board one. The SoC compatible is also
> incredibly generic. Personally I don't think this binding makes any
> sense as it appears to exist as a catch all for anything using your
> new cores in any combination.
I think I need to define any string for compatibility because it is standard
property. Because this is soft core it can be added to any board with AMD/Xilinx
chip. I don't have really an option to list all boards.
I am happy to change it to something else but not sure to what.
Thanks,
Michal
next prev parent reply other threads:[~2023-11-07 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:53 Michal Simek
2023-11-06 17:07 ` Conor Dooley
2023-11-07 11:09 ` Michal Simek [this message]
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
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=4223470c-5596-4168-9c89-e701559fbbed@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=conor@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@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
all inboxes | Powered by JetHome®