From: sashiko-bot@kernel.org
To: "Ajay Kumar Nandam" <ajay.nandam@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: sound: qcom,q6apm-dai: add optional qcom,vmid
Date: Tue, 09 Jun 2026 06:52:52 +0000 [thread overview]
Message-ID: <20260609065252.B1BC51F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260609064038.492641-2-ajay.nandam@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree binding arbitrarily restricts `qcom,vmid` array elements to a maximum of 31, encoding an OS driver bug as a hardware constraint.
--
commit adf539322d2d402e55788f41c212034d7e0a62e8
Author: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
dt-bindings: sound: qcom,q6apm-dai: add optional qcom,vmid
This commit adds an optional qcom,vmid property to the q6apm-dais node to
describe additional VMIDs that should be granted access to PCM DMA buffers.
It introduces a maximum value of 31 for the VMIDs to match the current SCM
source-permission mask handling.
> diff --git a/Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml b/Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml
> index 9e5b30d9c6e62..b767625985a74 100644
> --- a/Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml
> +++ b/Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml
> @@ -20,6 +20,16 @@ properties:
> minItems: 1
> maxItems: 2
>
> + qcom,vmid:
> + description: Optional list of destination VMIDs to share PCM DMA buffers with.
> + HLOS retains RW access as source owner and must not be listed.
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + items:
> + minimum: 1
> + maximum: 31
[Severity: Medium]
Does this artificially limit the hardware description based on a driver
implementation issue?
The commit message notes this matches current SCM source-permission mask
handling, but include/dt-bindings/firmware/qcom,scm.h defines valid VMIDs
that exceed 31 (e.g., QCOM_SCM_VMID_ADSP_HEAP = 37,
QCOM_SCM_VMID_CP_ADSP_SHARED = 51).
The limit of 31 seems to stem from the Linux qcom_scm_assign_mem() function
where it uses a 32-bit mask to track the source VMID mask. Should the device
tree binding allow higher VMIDs since bindings are meant to describe the
hardware capabilities rather than software limitations?
> + minItems: 1
> + maxItems: 8
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609064038.492641-1-ajay.nandam@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-06-09 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 6:40 [PATCH v1 0/3] ASoC: qcom: add q6apm VMID support and qdsp6 GPR destination-domain routing Ajay Kumar Nandam
2026-06-09 6:40 ` [PATCH v1 1/3] dt-bindings: sound: qcom,q6apm-dai: add optional qcom,vmid Ajay Kumar Nandam
2026-06-09 6:52 ` sashiko-bot [this message]
2026-06-09 6:40 ` [PATCH v1 2/3] ASoC: qcom: q6apm-dai: add VMID-based SCM assignment Ajay Kumar Nandam
2026-06-09 6:56 ` sashiko-bot
2026-06-09 6:40 ` [PATCH v1 3/3] ASoC: qcom: qdsp6: generalize GPR service domain Ajay Kumar Nandam
2026-06-09 8:59 ` sashiko-bot
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=20260609065252.B1BC51F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.