Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Georgi Djakov <djakov@kernel.org>,
	Yassine Oudjana <y.oudjana@protonmail.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	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, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] interconnect: qcom: msm8996: add missing link to SLAVE_USB_HS
Date: Mon, 6 Oct 2025 11:25:21 +0200	[thread overview]
Message-ID: <fde00935-6475-470d-bfde-4341d15c8441@oss.qualcomm.com> (raw)
In-Reply-To: <20251002-fix-msm8996-icc-v1-1-a36a05d1f869@oss.qualcomm.com>

On 10/2/25 10:53 AM, Dmitry Baryshkov wrote:
> From the initial submission the interconnect driver missed the link from
> SNOC_PNOC to the USB 2 configuration space. Add missing link in order to
> let the platform configure and utilize this path.
> 
> Fixes: 7add937f5222 ("interconnect: qcom: Add MSM8996 interconnect provider driver")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad


  reply	other threads:[~2025-10-06  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  8:52 [PATCH 0/2] arm64: dts: qcom: msm8996: fix issues with probing of USB hosts Dmitry Baryshkov
2025-10-02  8:53 ` [PATCH 1/2] interconnect: qcom: msm8996: add missing link to SLAVE_USB_HS Dmitry Baryshkov
2025-10-06  9:25   ` Konrad Dybcio [this message]
2025-10-02  8:53 ` [PATCH 2/2] arm64: dts: qcom: msm8996: add interconnect paths to USB2 controller Dmitry Baryshkov
2025-10-06  9:27   ` Konrad Dybcio
2025-10-06  9:30   ` Konrad Dybcio
2025-10-06 10:06     ` Dmitry Baryshkov
2025-10-30 18:24     ` Dmitry Baryshkov
2025-10-30 18:52       ` Bjorn Andersson

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=fde00935-6475-470d-bfde-4341d15c8441@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=dmitry.baryshkov@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=linux-pm@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=robh@kernel.org \
    --cc=y.oudjana@protonmail.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