From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, aiqun.yu@oss.qualcomm.com,
tingwei.zhang@oss.qualcomm.com, trilok.soni@oss.qualcomm.com,
yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH] dt-bindings: mailbox: qcom: Add CPUCP mailbox controller bindings for Kaanapali
Date: Thu, 9 Oct 2025 19:53:53 +0900 [thread overview]
Message-ID: <b2f06313-124f-41ef-bd53-2484140ca0b1@kernel.org> (raw)
In-Reply-To: <20250924-knp-cpufreq-v1-1-1bda16702bb1@oss.qualcomm.com>
On 25/09/2025 08:23, Jingyi Wang wrote:
> Document CPUSS Control Processor (CPUCP) mailbox controller for Qualcomm
> Kaanapali, which is compatible with X1E80100, use fallback to indicate
> this.
>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml b/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml
> index f7342d04beec..6f72f78e4b72 100644
> --- a/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml
> +++ b/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml
> @@ -15,8 +15,13 @@ description:
>
> properties:
> compatible:
> - items:
> - - const: qcom,x1e80100-cpucp-mbox
> + oneOf:
No, you send conflicting work with Glymur. Just send ONE PATCH.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-09 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:23 [PATCH] dt-bindings: mailbox: qcom: Add CPUCP mailbox controller bindings for Kaanapali Jingyi Wang
2025-10-09 10:53 ` Krzysztof Kozlowski [this message]
2025-10-09 10:57 ` 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=b2f06313-124f-41ef-bd53-2484140ca0b1@kernel.org \
--to=krzk@kernel.org \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.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