From: Bjorn Andersson <andersson@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>, johan+linaro@kernel.org
Cc: Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, konrad.dybcio@somainline.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
agross@kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: sc8280xp: disallow regulator mode switches
Date: Mon, 29 Aug 2022 18:45:51 -0500 [thread overview]
Message-ID: <166181675980.322065.3918715363441736917.b4-ty@kernel.org> (raw)
In-Reply-To: <20220803121942.30236-1-johan+linaro@kernel.org>
On Wed, 3 Aug 2022 14:19:39 +0200, Johan Hovold wrote:
> A recent change in a USB/DP PHY driver that started specifying regulator
> loads caused the regulators that were also shared with the PCIe and USB
> PHYs to be put in low-power mode, something which broke PCIe and USB on
> sa8295p-adp.
>
> As was discussed in the following thread:
>
> [...]
Applied, thanks!
[1/3] arm64: dts: qcom: sc8280xp-crd: disallow regulator mode switches
commit: 412737a60c846a6adb7f7571905c200da036815e
[2/3] arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: disallow regulator mode switches
commit: 648ec2f2ddc05346287e308fbc31a6b8117a1edd
[3/3] arm64: dts: qcom: sa8295p-adp: disallow regulator mode switches
commit: 2a6164cef63cae77edbd9deef844b1774886fcb7
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-08-29 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 12:19 [PATCH 0/3] arm64: dts: qcom: sc8280xp: disallow regulator mode switches Johan Hovold
2022-08-03 12:19 ` [PATCH 1/3] arm64: dts: qcom: sc8280xp-crd: " Johan Hovold
2022-08-03 12:19 ` [PATCH 2/3] arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: " Johan Hovold
2022-08-03 12:19 ` [PATCH 3/3] arm64: dts: qcom: sa8295p-adp: " Johan Hovold
2022-08-08 8:10 ` [PATCH 0/3] arm64: dts: qcom: sc8280xp: " Manivannan Sadhasivam
2022-08-29 23:45 ` 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=166181675980.322065.3918715363441736917.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=robh+dt@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 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.