mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: Michal Simek <michal.simek@amd.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: Tue, 15 Sep 2026 02:10:16 +0200	[thread overview]
Message-ID: <76db8193-6144-4460-acaa-f3d11fddba44@nabladev.com> (raw)
In-Reply-To: <656ae6e2-608a-4839-bcfe-941dfffdca11@amd.com>

On 9/14/26 8:29 AM, Michal Simek wrote:

[...]
>>>>> 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.
>>
>> I do not think there is, but no public documentation is the case with 
>> many boards/DTs that are upstream, and it does not diminish their 
>> usefulness to their users.
>>
>> What do you need to know ?
> 
> All these SOC based boards are created not because of hard block (PS 
> part) but because of programmable logic which is not described in any 
> upstream project DT. It means no matter what manufacturer has to 
> maintain PL description separately.
> 
> I don't really mind if other maintainers are fine with dealing with 
> these kind of boards without any public documentation. There is no way 
> to check if even your description is correct.
> I am not going to take any responsibility for maintaining them.
I can help with maintaining this board, it's a non-issue.

  reply	other threads:[~2026-09-15  3:26 UTC|newest]

Thread overview: 19+ 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 14:50     ` Marek Vasut
2026-09-11  9:38   ` Peter Korsgaard
2026-09-11 14:49     ` Marek Vasut
2026-09-13 14:27       ` Peter Korsgaard
2026-09-14  1:55         ` Marek Vasut
2026-09-14  5:32           ` Peter Korsgaard
2026-09-14 13:50             ` Marek Vasut
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
2026-09-11 15:54           ` Marek Vasut
2026-09-14  6:29             ` Michal Simek
2026-09-15  0:10               ` Marek Vasut [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=76db8193-6144-4460-acaa-f3d11fddba44@nabladev.com \
    --to=marex@nabladev.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=michal.simek@amd.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®