From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mailbox: qcom: Document Nord CPUCP mailbox controller
Date: Wed, 22 Apr 2026 18:43:18 +0800 [thread overview]
Message-ID: <aeimRgvAORJGer8d@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <20260421-free-meticulous-beetle-bb3fcd@quoll>
On Tue, Apr 21, 2026 at 12:30:11PM +0200, Krzysztof Kozlowski wrote:
> On Mon, Apr 20, 2026 at 11:49:31AM +0800, Shawn Guo wrote:
> > From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> >
> > Document CPUSS Control Processor (CPUCP) mailbox controller for Qualcomm
> > Nord SoC. It has 16 IPC channels, compared to 3 on X1E80100 CPUCP.
>
> And more channels does not make it incompatible (see writing bindings or
> DTS101 slides). Please provide explanation why devices are not
> compatible.
I will list it as compatible with X1E80100 CPUCP.
Thank you for the comment!
Shawn
next prev parent reply other threads:[~2026-04-22 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 3:49 [PATCH 0/2] Add CPUCP mailbox support for Qualcomm Nord SoC Shawn Guo
2026-04-20 3:49 ` [PATCH 1/2] dt-bindings: mailbox: qcom: Document Nord CPUCP mailbox controller Shawn Guo
2026-04-21 10:30 ` Krzysztof Kozlowski
2026-04-22 10:43 ` Shawn Guo [this message]
2026-04-20 3:49 ` [PATCH 2/2] mailbox: qcom-cpucp: Add support for " Shawn Guo
2026-04-20 8:22 ` Konrad Dybcio
2026-04-21 7:39 ` Shawn Guo
2026-04-20 8:23 ` [PATCH 0/2] Add CPUCP mailbox support for Qualcomm Nord SoC Konrad Dybcio
2026-04-21 7:38 ` Shawn Guo
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=aeimRgvAORJGer8d@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepti.jaggi@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@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