From: Mark Brown <broonie@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Kuogee Hsieh <quic_khsieh@quicinc.com>,
Douglas Anderson <dianders@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
dri-devel@lists.freedesktop.org, robdclark@gmail.com,
sean@poorly.run, swboyd@chromium.org, daniel@ffwll.ch,
airlied@linux.ie, agross@kernel.org, dmitry.baryshkov@linaro.org,
quic_abhinavk@quicinc.com, quic_aravindh@quicinc.com,
quic_sbillaka@quicinc.com, freedreno@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v16 0/3] eDP/DP Phy vdda realted function
Date: Thu, 21 Jul 2022 12:20:23 +0100 [thread overview]
Message-ID: <Ytk2dxEC2n/ffNpD@sirena.org.uk> (raw)
In-Reply-To: <YtkrDcjTGhpaU1e0@hovoldconsulting.com>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Thu, Jul 21, 2022 at 12:31:41PM +0200, Johan Hovold wrote:
If you're copying someone into a thread that's not obviously relevant
for them it's good practice to put a note about it at the top of the
mail to reduce the chances that it just gets deleted unread - people get
copies of all sorts of random stuff for not great reasons (like getting
pulled in by checkpatch due to once having done a cleanup) and are often
quicky to delete things.
> This series breaks USB and PCIe for some SC8280XP and SA540P machines
> where the DP PHY regulators are shared with other PHYs whose drivers do
> not request a load.
> Specifically, the hard-coded vdda-phy load of 21.8 mA added by this
> series, causes several RPMh regulators to now be put in low-power mode.
> I found Doug's suggestion to handle situations like this in regulator
> core:
>
> https://lore.kernel.org/all/20180814170617.100087-1-dianders@chromium.org/
> but since that was rejected, how do we deal with this generally?
> In the above thread Doug mentioned adding support for load requests to
> further drivers and Bjorn mentioned working around it by adding
> regulator-system-load properties to DT.
> It seems quite likely that changes like this one affects other systems
> too, and the effects may be hard to debug. So a more general solution
> than playing whack-a-mole using DT would be good to have.
You could add a way to specify constant base loads in DT on either a per
regulator or per consumer basis.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: quic_sbillaka@quicinc.com, airlied@linux.ie,
dri-devel@lists.freedesktop.org,
Liam Girdwood <lgirdwood@gmail.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
quic_aravindh@quicinc.com,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
agross@kernel.org, linux-arm-msm@vger.kernel.org,
quic_abhinavk@quicinc.com, swboyd@chromium.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
sean@poorly.run, Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
dmitry.baryshkov@linaro.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH v16 0/3] eDP/DP Phy vdda realted function
Date: Thu, 21 Jul 2022 12:20:23 +0100 [thread overview]
Message-ID: <Ytk2dxEC2n/ffNpD@sirena.org.uk> (raw)
In-Reply-To: <YtkrDcjTGhpaU1e0@hovoldconsulting.com>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Thu, Jul 21, 2022 at 12:31:41PM +0200, Johan Hovold wrote:
If you're copying someone into a thread that's not obviously relevant
for them it's good practice to put a note about it at the top of the
mail to reduce the chances that it just gets deleted unread - people get
copies of all sorts of random stuff for not great reasons (like getting
pulled in by checkpatch due to once having done a cleanup) and are often
quicky to delete things.
> This series breaks USB and PCIe for some SC8280XP and SA540P machines
> where the DP PHY regulators are shared with other PHYs whose drivers do
> not request a load.
> Specifically, the hard-coded vdda-phy load of 21.8 mA added by this
> series, causes several RPMh regulators to now be put in low-power mode.
> I found Doug's suggestion to handle situations like this in regulator
> core:
>
> https://lore.kernel.org/all/20180814170617.100087-1-dianders@chromium.org/
> but since that was rejected, how do we deal with this generally?
> In the above thread Doug mentioned adding support for load requests to
> further drivers and Bjorn mentioned working around it by adding
> regulator-system-load properties to DT.
> It seems quite likely that changes like this one affects other systems
> too, and the effects may be hard to debug. So a more general solution
> than playing whack-a-mole using DT would be good to have.
You could add a way to specify constant base loads in DT on either a per
regulator or per consumer basis.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-21 11:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 16:29 [PATCH v16 0/3] eDP/DP Phy vdda realted function Kuogee Hsieh
2022-07-05 16:29 ` Kuogee Hsieh
2022-07-05 16:29 ` [PATCH v16 1/3] phy: qcom-edp: add regulator_set_load to edp phy Kuogee Hsieh
2022-07-05 16:29 ` Kuogee Hsieh
2022-07-05 16:29 ` [PATCH v16 2/3] phy: qcom-qmp: add regulator_set_load to dp phy Kuogee Hsieh
2022-07-05 16:29 ` Kuogee Hsieh
2022-07-05 16:29 ` [PATCH v16 3/3] drm/msm/dp: delete vdda regulator related functions from eDP/DP controller Kuogee Hsieh
2022-07-05 16:29 ` Kuogee Hsieh
2022-07-06 16:54 ` [PATCH v16 0/3] eDP/DP Phy vdda realted function Vinod Koul
2022-07-06 16:54 ` Vinod Koul
2022-07-21 10:31 ` Johan Hovold
2022-07-21 10:31 ` Johan Hovold
2022-07-21 11:20 ` Mark Brown [this message]
2022-07-21 11:20 ` Mark Brown
2022-07-21 11:56 ` Mark Brown
2022-07-21 11:56 ` Mark Brown
2022-07-21 12:12 ` Johan Hovold
2022-07-21 12:12 ` Johan Hovold
2022-07-21 14:39 ` Doug Anderson
2022-07-21 14:39 ` Doug Anderson
2022-07-21 14:52 ` Doug Anderson
2022-07-21 14:52 ` Doug Anderson
2022-07-21 16:15 ` Mark Brown
2022-07-21 16:15 ` Mark Brown
2022-07-22 1:28 ` Doug Anderson
2022-07-22 1:28 ` Doug Anderson
2022-07-21 13:25 ` Dmitry Baryshkov
2022-07-21 13:25 ` Dmitry Baryshkov
2022-07-21 14:49 ` Doug Anderson
2022-07-21 14:49 ` Doug Anderson
2022-07-21 15:05 ` Mark Brown
2022-07-21 15:05 ` Mark Brown
2022-07-21 15:43 ` Doug Anderson
2022-07-21 15:43 ` Doug Anderson
2022-07-21 16:06 ` Mark Brown
2022-07-21 16:06 ` Mark Brown
2022-07-21 18:41 ` Dmitry Baryshkov
2022-07-21 18:41 ` Dmitry Baryshkov
2022-07-29 13:35 ` Johan Hovold
2022-07-29 13:35 ` Johan Hovold
2022-07-29 14:07 ` Mark Brown
2022-07-29 14:07 ` Mark Brown
2022-08-03 8:50 ` Johan Hovold
2022-08-03 8:50 ` Johan Hovold
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=Ytk2dxEC2n/ffNpD@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_aravindh@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@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.