From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: dri-devel@lists.freedesktop.org, robdclark@gmail.com,
sean@poorly.run, swboyd@chromium.org, dianders@chromium.org,
vkoul@kernel.org, daniel@ffwll.ch, airlied@linux.ie,
agross@kernel.org, bjorn.andersson@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
Subject: Re: [PATCH v2 0/2] eDP/DP Phy vdda realted function
Date: Wed, 18 May 2022 20:31:00 +0300 [thread overview]
Message-ID: <38e1f139-6814-db63-1f4b-5a76a1ab0eda@linaro.org> (raw)
In-Reply-To: <98295144-2e05-674b-4983-5f1738480c86@quicinc.com>
On 18/05/2022 20:29, Kuogee Hsieh wrote:
>
> On 5/18/2022 10:16 AM, Dmitry Baryshkov wrote:
>> On Wed, 18 May 2022 at 19:43, Kuogee Hsieh <quic_khsieh@quicinc.com>
>> wrote:
>>> 1) add regulator_set_load() to eDP/DP phy
>>> 2) remove vdda related function out of eDP/DP controller
>> These patches touch two subsystems and have a dependency between them.
>> How do we merge them?
>
> currently, both phy and controller are vote for regulator. The last vote
> will just increase count.
>
> Therefore the dependency should be very loose.
So, do you propose to merge dp change a cycle after the phy changes go in?
>
>
>>> Kuogee Hsieh (2):
>>> phy/qcom: add regulator_set_load to edp/dp phy
>>> drm/msm/dp: delete vdda regulator related functions from eDP/DP
>>> controller
>>>
>>> drivers/gpu/drm/msm/dp/dp_parser.c | 14 ------
>>> drivers/gpu/drm/msm/dp/dp_parser.h | 6 ---
>>> drivers/gpu/drm/msm/dp/dp_power.c | 95
>>> +------------------------------------
>>> drivers/phy/qualcomm/phy-qcom-edp.c | 25 ++++++++--
>>> drivers/phy/qualcomm/phy-qcom-qmp.c | 13 +++++
>>> 5 files changed, 36 insertions(+), 117 deletions(-)
>>>
>>> --
>>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>>> Forum,
>>> a Linux Foundation Collaborative Project
>>>
>>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-05-18 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:43 [PATCH v2 0/2] eDP/DP Phy vdda realted function Kuogee Hsieh
2022-05-18 16:43 ` [PATCH v2 1/2] phy/qcom: add regulator_set_load to edp/dp phy Kuogee Hsieh
2022-05-18 17:12 ` Dmitry Baryshkov
2022-05-18 17:36 ` Kuogee Hsieh
2022-05-18 17:52 ` Dmitry Baryshkov
2022-05-18 18:27 ` Kuogee Hsieh
2022-05-18 16:43 ` [PATCH v2 2/2] drm/msm/dp: delete vdda regulator related functions from eDP/DP controller Kuogee Hsieh
2022-05-18 17:13 ` Dmitry Baryshkov
2022-05-18 17:16 ` [PATCH v2 0/2] eDP/DP Phy vdda realted function Dmitry Baryshkov
2022-05-18 17:29 ` Kuogee Hsieh
2022-05-18 17:31 ` Dmitry Baryshkov [this message]
2022-05-18 20:19 ` Kuogee Hsieh
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=38e1f139-6814-db63-1f4b-5a76a1ab0eda@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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=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;
as well as URLs for NNTP newsgroup(s).