[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3af48ac4-c9c2-5636-c18e-6e8c2ec2472d@quicinc.com>
Date: Mon, 20 Jun 2022 13:22:09 -0700
From: Kuogee Hsieh <quic_khsieh@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
<dri-devel@...ts.freedesktop.org>, <robdclark@...il.com>,
<sean@...rly.run>, <swboyd@...omium.org>, <dianders@...omium.org>,
<vkoul@...nel.org>, <daniel@...ll.ch>, <airlied@...ux.ie>,
<agross@...nel.org>, <bjorn.andersson@...aro.org>
CC: <quic_abhinavk@...cinc.com>, <quic_aravindh@...cinc.com>,
<quic_sbillaka@...cinc.com>, <freedreno@...ts.freedesktop.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v14 2/3] phy: qcom-qmp: add regulator_set_load to dp phy
On 6/20/2022 1:15 PM, Dmitry Baryshkov wrote:
> On 20/06/2022 23:12, Kuogee Hsieh wrote:
>> This patch add regulator_set_load() before enable regulator at
>> DP phy driver.
>>
>> Signed-off-by: Kuogee Hsieh <quic_khsieh@...cinc.com>
>> Reviewed-by: Stephen Boyd <swboyd@...omium.org>
>> Reviewed-by: Douglas Anderson <dianders@...omium.org>
>> ---
>> drivers/phy/qualcomm/phy-qcom-qmp.c | 40
>> ++++++++++++++++++++++++++++---------
>
> This was not rebased. There is no phy-qcom-qmp.c in phy-next.
is https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
phy-next tree?
What exactly procedures I have to do base on Vinod's comment?
Thanks,
Powered by blists - more mailing lists