public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
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 2/2] mailbox: qcom-cpucp: Add support for Nord CPUCP mailbox controller
Date: Tue, 21 Apr 2026 15:39:26 +0800	[thread overview]
Message-ID: <aecprtAMplWlaiBI@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <43db2263-0dab-4652-ae1e-f827d1dc5c28@oss.qualcomm.com>

On Mon, Apr 20, 2026 at 10:22:59AM +0200, Konrad Dybcio wrote:
> On 4/20/26 5:49 AM, Shawn Guo wrote:
> > From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> > 
> > The Nord SoC CPUCP mailbox supports 16 IPC channels, compared to 3 on
> > x1e80100. The existing driver hardcodes the channel count via a
> > compile-time constant (APSS_CPUCP_IPC_CHAN_SUPPORTED), making it
> > impossible to support hardware with a different number of channels.
> > 
> > Introduce a qcom_cpucp_mbox_data per-hardware configuration struct that
> > carries the channel count, and retrieve it via of_device_get_match_data()
> > at probe time. Switch the channel array from a fixed-size member to a
> > dynamically allocated buffer sized from the hardware data. Update the
> > x1e80100 entry to supply its own data struct, and add a new Nord entry
> > with num_chans = 16.
> > 
> > Signed-off-by: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> > Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> > ---
> 
> [...]
> 
> >  /**
> >   * struct qcom_cpucp_mbox - Holder for the mailbox driver
> > - * @chans:			The mailbox channel
> > + * @chans:			The mailbox channels (dynamically allocated)
> 
> I don't think this line is a valuable change

Indeed!  I will drop the change.  Thanks!

Shawn

  reply	other threads:[~2026-04-21  7:39 UTC|newest]

Thread overview: 8+ 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-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 [this message]
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=aecprtAMplWlaiBI@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=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@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