From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
kernel@oss.qualcomm.com, prasad.kumpatla@oss.qualcomm.com,
ajay.nandam@oss.qualcomm.com
Subject: Re: [PATCH v1] arm64: dts: qcom: monaco-evk: Use correct sound card compatible to match SoC
Date: Wed, 10 Sep 2025 09:24:56 +0200 [thread overview]
Message-ID: <9a4e50f3-cb4e-40cc-a722-b17d136a7062@kernel.org> (raw)
In-Reply-To: <20250910044512.1369640-1-mohammad.rafi.shaik@oss.qualcomm.com>
On 10/09/2025 06:45, Mohammad Rafi Shaik wrote:
> The Monaco-EVK board is based on Qualcomm's QCS8300 SoC. The DTS
> previously reused the sound card compatible as "qcom,qcs8275-sndcard",
So who is going to use qcom,qcs8275-sndcard compatible? I don't see any
DTS using it.
> which is based on existing coverage. To maintain clarity and consistency,
> the naming conventions for the compatible should reflect actual SoC
> rather than the board. Therefore, update the sound card compatible as
> "qcom,qcs8300-sndcard" to avoid potential confusion.
>
> Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-10 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 4:45 [PATCH v1] arm64: dts: qcom: monaco-evk: Use correct sound card compatible to match SoC Mohammad Rafi Shaik
2025-09-10 4:47 ` kernel test robot
2025-09-10 7:24 ` Krzysztof Kozlowski [this message]
2025-09-10 9:45 ` 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=9a4e50f3-cb4e-40cc-a722-b17d136a7062@kernel.org \
--to=krzk@kernel.org \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@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=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=prasad.kumpatla@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
/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