From: Michal Simek <michal.simek@amd.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] dt-bindings: soc: xilinx: Add support for K26 rev2 SOMs
Date: Wed, 31 Jan 2024 10:09:14 +0100 [thread overview]
Message-ID: <537eb07a-07e8-4af2-ad83-058e010f892c@amd.com> (raw)
In-Reply-To: <90e1a393154c3d87e8ee7dc9eef07fc937c1eaf7.1706019397.git.michal.simek@amd.com>
On 1/23/24 15:16, Michal Simek wrote:
> Revision 2 is SW compatible with revision 1 but it is necessary to reflect
> it in model and compatible properties which are parsed by user space.
> Rev 2 has improved a power on boot reset and MIO34 shutdown glich
> improvement done via an additional filter in the GreenPak chip.
>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
> Changes in v3:
> - use allOf contains structure to avoid random chars caused by
> additionalItems: true
>
> Changes in v2:
> - Support older combinations
>
> I want to support all versions we created:
> All of them:
> -rev2, -rev1, -revB, -revA, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
>
> rev1:
> -rev1, -revB, -revA, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
>
> revB:
> -revB, -revA, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
>
> revA:
> -revA, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
>
> And also single one are permitted:
> -revB, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
> -rev1, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
> -rev2, "xlnx,zynqmp-smk-k26", "xlnx,zynqmp"
>
> I didn't find a way to pretty much all the time force that there must be
> both "xlnx,zynqmp-smk-k26", "xlnx,zynqmp" that's why there is only
> requested to have xlnx,zynqmp. If you find a way how to encode it please
> let me know.
>
> ---
> .../bindings/soc/xilinx/xilinx.yaml | 36 +++++++++++++------
> 1 file changed, 26 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml b/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> index d4c0fe1fe435..7c75dbb4f307 100644
> --- a/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> +++ b/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> @@ -117,20 +117,36 @@ properties:
> - const: xlnx,zynqmp
>
> - description: Xilinx Kria SOMs
> + minItems: 3
> items:
> - - const: xlnx,zynqmp-sm-k26-rev1
> - - const: xlnx,zynqmp-sm-k26-revB
> - - const: xlnx,zynqmp-sm-k26-revA
> - - const: xlnx,zynqmp-sm-k26
> - - const: xlnx,zynqmp
> + enum:
> + - xlnx,zynqmp-sm-k26-rev2
> + - xlnx,zynqmp-sm-k26-rev1
> + - xlnx,zynqmp-sm-k26-revB
> + - xlnx,zynqmp-sm-k26-revA
> + - xlnx,zynqmp-sm-k26
> + - xlnx,zynqmp
> + allOf:
> + - contains:
> + const: xlnx,zynqmp
> + - contains:
> + const: xlnx,zynqmp-sm-k26
>
> - description: Xilinx Kria SOMs (starter)
> + minItems: 3
> items:
> - - const: xlnx,zynqmp-smk-k26-rev1
> - - const: xlnx,zynqmp-smk-k26-revB
> - - const: xlnx,zynqmp-smk-k26-revA
> - - const: xlnx,zynqmp-smk-k26
> - - const: xlnx,zynqmp
> + enum:
> + - xlnx,zynqmp-smk-k26-rev2
> + - xlnx,zynqmp-smk-k26-rev1
> + - xlnx,zynqmp-smk-k26-revB
> + - xlnx,zynqmp-smk-k26-revA
> + - xlnx,zynqmp-smk-k26
> + - xlnx,zynqmp
> + allOf:
> + - contains:
> + const: xlnx,zynqmp
> + - contains:
> + const: xlnx,zynqmp-smk-k26
>
> - description: AMD MicroBlaze V (QEMU)
> items:
Applied.
M
prev parent reply other threads:[~2024-01-31 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 14:16 [PATCH v3] dt-bindings: soc: xilinx: Add support for K26 rev2 SOMs Michal Simek
2024-01-30 20:50 ` Rob Herring
2024-01-31 9:09 ` Michal Simek [this message]
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=537eb07a-07e8-4af2-ad83-058e010f892c@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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