From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yunhong Jiang <yunhong.jiang@linux.intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, rafael@kernel.org, lenb@kernel.org,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 2/9] dt-bindings: x86: Add a binding for x86 wakeup mailbox
Date: Fri, 20 Sep 2024 13:19:26 +0200 [thread overview]
Message-ID: <dce6b8b3-2171-47a9-b110-89ad02021fc7@kernel.org> (raw)
In-Reply-To: <20240919221431.GA14771@yjiang5-mobl.amr.corp.intel.com>
On 20/09/2024 00:15, Yunhong Jiang wrote:
>>>
>>>>
>>>> For your "validated by the tools", can you please share the tools you used to
>>>> validate the schema? I used "make dt_binding_check" per the
>>>> submitting-patches.rst but I think your comments is about another tool.
>>>
>>> See writing-schema document.
>> Yes, I figured out in the end that the validate tools means the dt-schema tools.
>>
>> Thank you
>> --jyh
>
> One thing just come to my mind. The
> Documentation/devicetree/bindings/x86/wakeup.yaml only adds one property,
> wakeup-mailbox-addr, to the cpus node, and it does not specify any new object.
> Per my understanding, the json schema file normally specifies a new object.
> Is my change a supported scenario in current Documentation/devicetree?
I think that's not related. You can add properties per specific devices,
but (as I said) you do not have a compatible. Compatible represents a
specific device. You do not have it. Look at the cpus.yaml schema.
>
> I checked similar scenario like arm/cpu-enable-method/nuvoton and
> npcm750-smp/cpu-enable-method/al,alpine-smp, they don't present as a json
> schema file. Wonder if it's because the same reason.
Rather no one cares about that hardware.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-20 11:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 23:23 [PATCH v2 0/9] x86/hyperv: Support wakeup mailbox for VTL2 TDX guest Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 1/9] x86/acpi: Move ACPI MADT wakeup to generic code Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 2/9] dt-bindings: x86: Add a binding for x86 wakeup mailbox Yunhong Jiang
2024-08-25 7:10 ` Krzysztof Kozlowski
2024-08-27 20:45 ` Yunhong Jiang
2024-09-10 6:13 ` Yunhong Jiang
2024-09-16 8:56 ` Krzysztof Kozlowski
2024-09-19 19:19 ` Yunhong Jiang
2024-09-19 22:15 ` Yunhong Jiang
2024-09-20 11:19 ` Krzysztof Kozlowski [this message]
2024-09-20 11:15 ` Krzysztof Kozlowski
2025-03-03 22:21 ` Ricardo Neri
2025-03-11 10:01 ` Krzysztof Kozlowski
2025-03-12 5:51 ` Ricardo Neri
2025-03-19 7:52 ` Krzysztof Kozlowski
2025-03-20 20:34 ` Ricardo Neri
2024-08-23 23:23 ` [PATCH v2 3/9] x86/dt: Support the ACPI multiprocessor wakeup for device tree Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-03 18:35 ` Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 4/9] x86/hyperv: Parse the ACPI wakeup mailbox Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-03 20:19 ` Yunhong Jiang
2024-09-04 14:56 ` Michael Kelley
2024-09-04 17:31 ` Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 5/9] x86/hyperv: Mark ACPI wakeup mailbox page as private Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-09-02 18:38 ` Saurabh Singh Sengar
2024-09-02 20:24 ` Michael Kelley
2024-08-23 23:23 ` [PATCH v2 6/9] x86/realmode: Add memory range support to reserve_real_mode Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 7/9] x86/hyperv: Move setting the real_mode_header to hv_vtl_init_platform Yunhong Jiang
2024-08-23 23:23 ` [PATCH v2 8/9] x86/hyperv: Set realmode_limit to 4G for VTL2 TDX guest Yunhong Jiang
2024-09-02 3:35 ` Michael Kelley
2024-08-23 23:23 ` [PATCH v2 9/9] x86/hyperv: Use wakeup mailbox for VTL2 guests if available Yunhong Jiang
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=dce6b8b3-2171-47a9-b110-89ad02021fc7@kernel.org \
--to=krzk@kernel.org \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=yunhong.jiang@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).