From: Michal Simek <michal.simek@amd.com>
To: Marek Vasut <marex@nabladev.com>, linux-arm-kernel@lists.infradead.org
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: soc: xilinx: Document ifm ZynqMP VHIP6 EvalBoard
Date: Fri, 11 Sep 2026 10:38:08 +0200 [thread overview]
Message-ID: <a0d23fc9-6f7b-4c19-9f6f-9cc0c7cce3f5@amd.com> (raw)
In-Reply-To: <7b957072-df73-4fab-91ba-9835285ff8c5@nabladev.com>
On 9/11/26 01:39, Marek Vasut wrote:
> On 9/10/26 9:17 AM, Michal Simek wrote:
>
>>>>> +++ b/Documentation/devicetree/bindings/soc/xilinx/xilinx.yaml
>>>>> @@ -44,6 +44,11 @@ properties:
>>>>> - const: xlnx,zynq-zed
>>>>> - const: xlnx,zynq-7000
>>>>> + - items:
>>>>> + - const: ifm,zynqmp-vhip6-evalboard
>>>>> + - const: ifm,zynqmp-vhip6
>>>>> + - const: xlnx,zynqmp
>>>>> +
>>>>> - items:
>>>>> - enum:
>>>>> - xlnx,zynqmp-zc1751
>>>>
>>>> Can you please provide any link to public documentation about this board?
>>>> I wasn't able to find anything through google..
>>>
>>> I do not know whether there is any, it is an internal board from which other
>>> boards get derived.
>>>
>>> What would you like to know ?
>>
>> I would like to know value for me to maintain it. Why should I care about
>> board which don't have any public documentation and none can buy?
>
> I think because the users of this board actually do benefit from having the
> support upstream, instead of having to lug around random downstream patches in
> assorted state of decay.
>
>> There will be thousands of similar boards out there and I am definitely not
>> going to have all of them in the tree.
> Why not ? There are users who benefit from having their board support upstream.
> This is what other SoC vendors do as well, it does not seem to be a problem,
> rather it is a good indicator that the SoC has users who care about it and about
> upstream.
If there is public documentation about it I don't have any problem with it.
> If you do require a sample board, I could try to arrange that.
I definitely don't want that board.
Thanks,
Michal
next prev parent reply other threads:[~2026-09-11 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 18:26 Marek Vasut
2026-09-09 18:26 ` [PATCH v2 2/2] arm64: zynqmp: Add " Marek Vasut
2026-09-11 7:32 ` Krzysztof Kozlowski
2026-09-11 9:38 ` Peter Korsgaard
2026-09-10 6:22 ` [PATCH v2 1/2] dt-bindings: soc: xilinx: Document " Michal Simek
2026-09-10 7:01 ` Marek Vasut
2026-09-10 7:17 ` Michal Simek
2026-09-10 23:39 ` Marek Vasut
2026-09-11 8:38 ` Michal Simek [this message]
2026-09-11 7:32 ` Krzysztof Kozlowski
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=a0d23fc9-6f7b-4c19-9f6f-9cc0c7cce3f5@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=robh@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®