From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kumar Anurag <kumar.singh@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: Abel Vesa <abelvesa@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_mohanull@quicinc.com,
quic_hbandi@quicinc.com
Subject: Re: [PATCH v1] arm64: dts: qcom: Add dmic45 support to rb3gen2 vision mezzanine overlay
Date: Mon, 2 Nov 2026 15:20:02 +0100 [thread overview]
Message-ID: <bde94c6c-1119-4bb7-be7c-a4772c6d0a6d@oss.qualcomm.com> (raw)
In-Reply-To: <20261027115115.1822423-1-kumar.singh@oss.qualcomm.com>
On 10/27/26 12:51 PM, Kumar Anurag wrote:
> Add pinctrl states and VA macro routing for two additional digital
> microphones (DMIC4/DMIC5) that are present on the vision mezzanine
> add-on board, mirroring the dmic01/dmic23 pattern already used for
> the on-board microphones.
>
> Signed-off-by: Kumar Anurag <kumar.singh@oss.qualcomm.com>
> ---
> .../qcs6490-rb3gen2-vision-mezzanine.dtso | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-vision-mezzanine.dtso b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-vision-mezzanine.dtso
> index aceafea45343..0a4e6080a2b2 100644
> --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-vision-mezzanine.dtso
> +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2-vision-mezzanine.dtso
> @@ -80,3 +80,42 @@ cam_mclk3_suspend: cam-mclk3-suspend-state {
> bias-pull-down;
> };
> };
> +
> +&lpass_tlmm {
> + lpass_dmic45_clk: dmic45-clk-state {
> + pins = "gpio12";
> + function = "dmic3_clk";
> + };
> +
> + lpass_dmic45_data: dmic45-data-state {
> + pins = "gpio13";
> + function = "dmic3_data";
> + };
> +};
This should go to kodiak.dtsi
Konrad
prev parent reply other threads:[~2026-11-02 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 11:51 Kumar Anurag
2026-11-02 14:20 ` Konrad Dybcio [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=bde94c6c-1119-4bb7-be7c-a4772c6d0a6d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kumar.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohanull@quicinc.com \
--cc=robh@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
all inboxes | Powered by JetHome®