From: Bjorn Andersson <andersson@kernel.org>
To: konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
konrad.dybcio@oss.qualcomm.com,
Dmitry Baryshkov <lumag@kernel.org>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Cc: mukesh.savaliya@oss.qualcomm.com
Subject: Re: (subset) [PATCH 1/1] arm64: dts: qcom: talos: Drop opp-shared from QUP OPP table
Date: Tue, 20 Jan 2026 20:35:55 -0600 [thread overview]
Message-ID: <176896294110.1060469.5525109788160217073.b4-ty@kernel.org> (raw)
In-Reply-To: <20251111170350.525832-1-viken.dadhaniya@oss.qualcomm.com>
On Tue, 11 Nov 2025 22:33:50 +0530, Viken Dadhaniya wrote:
> QUP devices are currently marked with opp-shared in their OPP table,
> causing the kernel to treat them as part of a shared OPP domain. This
> leads to the qcom_geni_serial driver failing to probe with error
> -EBUSY (-16).
>
> Remove the opp-shared property to ensure the OPP framework treats the
> QUP OPP table as device-specific, allowing the serial driver to probe
> successfully
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: talos: Drop opp-shared from QUP OPP table
commit: dda4bdd325326dd67ae4401f4f3d35b9cf781e3f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-01-21 2:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 17:03 Viken Dadhaniya
2025-11-11 19:55 ` Bjorn Andersson
2025-11-21 10:07 ` Viken Dadhaniya
2025-11-21 12:03 ` Dmitry Baryshkov
2025-11-24 9:40 ` Viken Dadhaniya
2025-12-17 15:50 ` Viken Dadhaniya
2026-01-07 4:52 ` Viken Dadhaniya
2026-01-09 19:40 ` Bjorn Andersson
2026-01-12 8:47 ` Viken Dadhaniya
2025-11-12 9:40 ` Konrad Dybcio
2026-01-21 2:35 ` Bjorn Andersson [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=176896294110.1060469.5525109788160217073.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=mukesh.savaliya@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=viken.dadhaniya@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
all inboxes | Powered by JetHome®