mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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] dt-bindings: soc: xilinx: Add support for KV260 CC
Date: Wed, 31 Jan 2024 10:09:24 +0100	[thread overview]
Message-ID: <c0742517-868d-4dbc-b6e1-a5fddeceb6d9@amd.com> (raw)
In-Reply-To: <14c184225cc4f0a61da5f8c98bc0767f8deba0df.1706019781.git.michal.simek@amd.com>



On 1/23/24 15:23, Michal Simek wrote:
> When DT overlay is applied at run time compatible string or model AFAIK is
> not updated. But when fdtoverlay tool is used it actually creates full
> description for used SOM and carrier card(CC). That's why there is no
> reason to use generic SOM name and its compatible strings because they are
> not properly reflected in newly created DT.
> Composing dt overlays together was introduced by commit 7a4c31ee877a
> ("arm64: zynqmp: Add support for Xilinx Kria SOM board") and later renamed
> by commit 45fe0dc4ea2e ("arm64: xilinx: Use zynqmp prefix for SOM dt
> overlays").
> DTB selection is done prior booting OS that's why there is no need to do
> run time composition for SOM and CC combination. And user space can use
> compatible string and all listed revisions to figured it out which SOM and
> CC combinations OS is running at.
> 
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
> 
> We are using U-Boot DTB reselection feature to identify SOM + CC
> combination.
> 
> This patch depends on
> https://lore.kernel.org/r/90e1a393154c3d87e8ee7dc9eef07fc937c1eaf7.1706019397.git.michal.simek@amd.com
> 
> ---
>   .../bindings/soc/xilinx/xilinx.yaml           | 34 +++++++++++++++++++
>   1 file changed, 34 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml b/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> index 7c75dbb4f307..131aba5ed9f4 100644
> --- a/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> +++ b/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
> @@ -148,6 +148,40 @@ properties:
>             - contains:
>                 const: xlnx,zynqmp-smk-k26
>   
> +      - description: Xilinx Kria SOM KV260 revA/Y/Z
> +        minItems: 3
> +        items:
> +          enum:
> +            - xlnx,zynqmp-sk-kv260-revA
> +            - xlnx,zynqmp-sk-kv260-revY
> +            - xlnx,zynqmp-sk-kv260-revZ
> +            - xlnx,zynqmp-sk-kv260
> +            - xlnx,zynqmp
> +        allOf:
> +          - contains:
> +              const: xlnx,zynqmp-sk-kv260-revA
> +          - contains:
> +              const: xlnx,zynqmp-sk-kv260
> +          - contains:
> +              const: xlnx,zynqmp
> +
> +      - description: Xilinx Kria SOM KV260 rev2/1/B
> +        minItems: 3
> +        items:
> +          enum:
> +            - xlnx,zynqmp-sk-kv260-rev2
> +            - xlnx,zynqmp-sk-kv260-rev1
> +            - xlnx,zynqmp-sk-kv260-revB
> +            - xlnx,zynqmp-sk-kv260
> +            - xlnx,zynqmp
> +        allOf:
> +          - contains:
> +              const: xlnx,zynqmp-sk-kv260-revB
> +          - contains:
> +              const: xlnx,zynqmp-sk-kv260
> +          - contains:
> +              const: xlnx,zynqmp
> +
>         - description: AMD MicroBlaze V (QEMU)
>           items:
>             - const: qemu,mbv

Applied.
M

      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:23 Michal Simek
2024-01-30 20:51 ` 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=c0742517-868d-4dbc-b6e1-a5fddeceb6d9@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

all inboxes | Powered by JetHome®