[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fe7a404-be2c-4ac8-8980-2b3d07a74bca@kernel.org>
Date: Mon, 10 Feb 2025 20:27:34 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Mike Rapoport <rppt@...nel.org>, linux-kernel@...r.kernel.org,
Alexander Graf <graf@...zon.com>, Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>, Anthony Yznaga
<anthony.yznaga@...cle.com>, Arnd Bergmann <arnd@...db.de>,
Ashish Kalra <ashish.kalra@....com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Borislav Petkov <bp@...en8.de>, Catalin Marinas <catalin.marinas@....com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
David Woodhouse <dwmw2@...radead.org>, Eric Biederman
<ebiederm@...ssion.com>, Ingo Molnar <mingo@...hat.com>,
James Gowans <jgowans@...zon.com>, Jonathan Corbet <corbet@....net>,
Mark Rutland <mark.rutland@....com>, Paolo Bonzini <pbonzini@...hat.com>,
Pasha Tatashin <pasha.tatashin@...een.com>, "H. Peter Anvin"
<hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
Pratyush Yadav <ptyadav@...zon.de>, Rob Herring <robh+dt@...nel.org>,
Rob Herring <robh@...nel.org>, Saravana Kannan <saravanak@...gle.com>,
Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>,
Steven Rostedt <rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>,
Tom Lendacky <thomas.lendacky@....com>, Usama Arif
<usama.arif@...edance.com>, Will Deacon <will@...nel.org>,
devicetree@...r.kernel.org, kexec@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-mm@...ck.org, x86@...nel.org
Subject: Re: [PATCH v4 14/14] Documentation: KHO: Add memblock bindings
On 10/02/2025 20:15, Jason Gunthorpe wrote:
> On Sun, Feb 09, 2025 at 09:50:37PM +0100, Krzysztof Kozlowski wrote:
>>> Ah, neat, that would almost solve the problem but you wrote:
>>>
>>> +$id: http://devicetree.org/schemas/memblock/reserve_mem.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>
>>> so no, this does not work like that. You use devicetree here namespace
>>> and ignore its rules.
>>
>> ... and that obviously is barely parseable, so maybe one more try:
>> "You use here devicetree namespace but ignore its rules."
>
> It makes sense to me, there should be zero cross-over of the two
> specs, KHO should be completely self defined and stand alone.
>
> There is some documentation missing, I think. This yaml describes one
> node type, but the entire overall structure of the fdt does not seem
> to have documentation?
A lot of ABI is missing there and undocumented like: node name (which
for every standard DT would be a NAK), few properties. This binding
describes only subset while skipping all the rest and effectively
introducing implied/undocumented ABI.
Best regards,
Krzysztof
Powered by blists - more mailing lists