From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Johan Hovold <johan@kernel.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Stephen Boyd <swboyd@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Andy Gross <agross@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
"Abhinav Kumar (QUIC)" <quic_abhinavk@quicinc.com>,
"Aravind Venkateswaran (QUIC)" <quic_aravindh@quicinc.com>,
Sankeerth Billakanti <quic_sbillaka@quicinc.com>,
freedreno <freedreno@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <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 17:15:35 +0100 [thread overview]
Message-ID: <Ytl7p1UHidn2yHfv@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=WuyKAwLwJ80uv15jBPO=W9F7FGZ4dAci+CncwF0WPfOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Thu, Jul 21, 2022 at 07:52:01AM -0700, Doug Anderson wrote:
> On Thu, Jul 21, 2022 at 7:39 AM Doug Anderson <dianders@chromium.org> wrote:
> > vdda-phy-supply = <&vdda_mipi_dsi0_1p2>;
> > vdda-phy-supply-base-load = <21800>;
> Ah, sorry to respond to my own thread so quickly, but I just thought
> of a reason for the "matching properties" solution instead of the two
> cells. It would allow the SoC "dtsi" file to specify a base load while
> the board "dts" file can then specify the supply. That feels like it
> could be a nice solution.
For a per device thing it probably shouldn't be called a "base load",
it's just the load. I would question how useful this would be, aside
from the concerns vendors will likely have with disclosing actual power
consumptions if the number never changes then it is immaterial which
device contributes which milliamp of load, you just want to configure a
fixed mode on the regulator and have done with it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-21 16:17 UTC|newest]
Thread overview: 22+ 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 ` [PATCH v16 1/3] phy: qcom-edp: add regulator_set_load to edp phy 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 ` [PATCH v16 3/3] drm/msm/dp: delete vdda regulator related functions from eDP/DP controller Kuogee Hsieh
2022-07-06 16:54 ` [PATCH v16 0/3] eDP/DP Phy vdda realted function Vinod Koul
2022-07-21 10:31 ` Johan Hovold
2022-07-21 11:20 ` Mark Brown
2022-07-21 11:56 ` Mark Brown
2022-07-21 12:12 ` Johan Hovold
2022-07-21 14:39 ` Doug Anderson
2022-07-21 14:52 ` Doug Anderson
2022-07-21 16:15 ` Mark Brown [this message]
2022-07-22 1:28 ` Doug Anderson
2022-07-21 13:25 ` Dmitry Baryshkov
2022-07-21 14:49 ` Doug Anderson
2022-07-21 15:05 ` Mark Brown
2022-07-21 15:43 ` Doug Anderson
2022-07-21 16:06 ` Mark Brown
2022-07-21 18:41 ` Dmitry Baryshkov
2022-07-29 13:35 ` Johan Hovold
2022-07-29 14:07 ` Mark Brown
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=Ytl7p1UHidn2yHfv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox