From: sashiko-bot@kernel.org
To: "Sneh Mankad" <sneh.mankad@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 4/4] mailbox: qcom-apcs-ipc: Add Shikra APCS IPC support
Date: Fri, 08 May 2026 19:02:48 +0000 [thread overview]
Message-ID: <20260508190249.56F54C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508-shikra_mailbox_and_rpm_changes-v2-4-ab76fd9e71de@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch adds a new compatible string `qcom,shikra-apss-shared` that reuses existing driver data (`apps_shared_apcs_data`), directly violating an explicit maintainer directive in the code.
--
commit 6670ebc79f6a6772d5ca45315526be52e226e375
Author: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
mailbox: qcom-apcs-ipc: Add Shikra APCS IPC support
This commit enables Shikra APCS IPC support by adding the compatible string.
It reuses the existing apps_shared_apcs_data.
> diff --git a/drivers/mailbox/qcom-apcs-ipc-mailbox.c b/drivers/mailbox/qcom-apcs-ipc-mailbox.c
> index d3a8f6b4a03b3..25f76965921ba 100644
> --- a/drivers/mailbox/qcom-apcs-ipc-mailbox.c
> +++ b/drivers/mailbox/qcom-apcs-ipc-mailbox.c
> @@ -168,6 +168,7 @@ static const struct of_device_id qcom_apcs_ipc_of_match[] = {
> { .compatible = "qcom,ipq8074-apcs-apps-global", .data = &ipq6018_apcs_data },
> { .compatible = "qcom,sc7180-apss-shared", .data = &apps_shared_apcs_data },
> { .compatible = "qcom,sc8180x-apss-shared", .data = &apps_shared_apcs_data },
> + { .compatible = "qcom,shikra-apss-shared", .data = &apps_shared_apcs_data },
This isn't a bug, but does this addition conflict with the maintainer comment
located earlier in the qcom_apcs_ipc_of_match array?
The array contains an explicit directive:
/* Do not add any more entries using existing driver data */
Should this new device instead use a fallback compatible string in the
devicetree, such as "qcom,shikra-apss-shared", "qcom,sdm845-apss-shared",
rather than expanding the driver's match table?
> { .compatible = "qcom,sm8150-apss-shared", .data = &apps_shared_apcs_data },
> {}
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260508-shikra_mailbox_and_rpm_changes-v2-0-ab76fd9e71de@oss.qualcomm.com?part=4
prev parent reply other threads:[~2026-05-08 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 7:19 [PATCH v2 0/4] Add compatible strings for RPM and mailbox devices for Shikra Sneh Mankad
2026-05-08 7:19 ` [PATCH v2 1/4] dt-bindings: soc: qcom: smd-rpm: Add Shikra rpm-smd compatible Sneh Mankad
2026-05-08 7:19 ` [PATCH v2 2/4] dt-bindings: remoteproc: Add Shikra RPM processor compatible Sneh Mankad
2026-05-08 7:19 ` [PATCH v2 3/4] dt-bindings: mailbox: qcom: Add Shikra APCS compatible Sneh Mankad
2026-05-08 7:19 ` [PATCH v2 4/4] mailbox: qcom-apcs-ipc: Add Shikra APCS IPC support Sneh Mankad
2026-05-08 9:57 ` Dmitry Baryshkov
2026-05-11 5:35 ` Sneh Mankad
2026-05-08 19:02 ` sashiko-bot [this message]
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=20260508190249.56F54C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko@lists.linux.dev \
--cc=sneh.mankad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.