From: abhinavk@codeaurora.org
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Jonathan Marek <jonathan@marek.ca>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
freedreno@lists.freedesktop.org
Subject: Re: [Freedreno] [PATCH 0/8] dsi: rework clock parents and timing handling
Date: Thu, 10 Jun 2021 09:34:33 -0700 [thread overview]
Message-ID: <acc08fd48c98af3007ad3d8d810ff335@codeaurora.org> (raw)
In-Reply-To: <71839b49-554c-fcc4-d110-0c8a49905413@linaro.org>
Hi Dmitry
I will take a look at this next week for sure.
Thanks
Abhinav
On 2021-06-10 06:48, Dmitry Baryshkov wrote:
> On 15/05/2021 16:12, Dmitry Baryshkov wrote:
>> This patch series brings back several patches targeting assigning
>> dispcc
>> clock parents, that were removed from the massive dsi rework patchset
>> earlier.
>
> Gracious ping for this series. I'd ask to skip patch 8 for now (as we
> might bring that back for moving PHY to drivers/phy), but patches 1-7
> are still valid and pending review/acceptance.
>
>>
>> Few notes:
>> - assign-clock-parents is a mandatory proprety according to the
>> current
>> dsi.txt description.
>> - There is little point in duplicating this functionality with the
>> ad-hoc
>> implementation in the dsi code.
>>
>> On top of that come few minor cleanups for the DSI PHY drivers.
>>
>> I'd kindly ask to bring all dts changes also through the drm tree, so
>> that there won't be any breakage of the functionality.
>>
>>
>> The following changes since commit
>> f2f46b878777e0d3f885c7ddad48f477b4dea247:
>>
>> drm/msm/dp: initialize audio_comp when audio starts (2021-05-06
>> 16:26:57 -0700)
>>
>> are available in the Git repository at:
>>
>> https://git.linaro.org/people/dmitry.baryshkov/kernel.git
>> dsi-phy-update
>>
>> for you to fetch changes up to
>> f1fd3b113cbb98febad682fc11ea1c6e717434c2:
>>
>> drm/msm/dsi: remove msm_dsi_dphy_timing from msm_dsi_phy
>> (2021-05-14 22:55:11 +0300)
>>
>> ----------------------------------------------------------------
>> Dmitry Baryshkov (8):
>> arm64: dts: qcom: sc7180: assign DSI clock source parents
>> arm64: dts: qcom: sdm845: assign DSI clock source parents
>> arm64: dts: qcom: sdm845-mtp: assign DSI clock source parents
>> arm64: dts: qcom: sm8250: assign DSI clock source parents
>> drm/msm/dsi: stop setting clock parents manually
>> drm/msm/dsi: phy: use of_device_get_match_data
>> drm/msm/dsi: drop msm_dsi_phy_get_shared_timings
>> drm/msm/dsi: remove msm_dsi_dphy_timing from msm_dsi_phy
>>
>> arch/arm64/boot/dts/qcom/sc7180.dtsi | 3 ++
>> arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 3 ++
>> arch/arm64/boot/dts/qcom/sdm845.dtsi | 6 +++
>> arch/arm64/boot/dts/qcom/sm8250.dtsi | 6 +++
>> drivers/gpu/drm/msm/dsi/dsi.h | 7 +---
>> drivers/gpu/drm/msm/dsi/dsi_host.c | 51
>> -------------------------
>> drivers/gpu/drm/msm/dsi/dsi_manager.c | 8 +---
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 46
>> ++++++++++------------
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy.h | 10 ++++-
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_10nm.c | 11 ++----
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_14nm.c | 11 ++----
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_20nm.c | 10 +----
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_28nm.c | 12 ++----
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_28nm_8960.c | 10 +----
>> drivers/gpu/drm/msm/dsi/phy/dsi_phy_7nm.c | 13 ++-----
>> 15 files changed, 67 insertions(+), 140 deletions(-)
>>
>>
next prev parent reply other threads:[~2021-06-10 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 13:12 [PATCH 0/8] dsi: rework clock parents and timing handling Dmitry Baryshkov
2021-05-15 13:12 ` [PATCH 1/8] arm64: dts: qcom: sc7180: assign DSI clock source parents Dmitry Baryshkov
2021-06-21 22:08 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 2/8] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2021-06-21 22:08 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 3/8] arm64: dts: qcom: sdm845-mtp: " Dmitry Baryshkov
2021-06-21 22:08 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 4/8] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2021-06-21 22:09 ` abhinavk
2021-05-15 13:12 ` [PATCH 5/8] drm/msm/dsi: stop setting clock parents manually Dmitry Baryshkov
2021-06-21 22:10 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 6/8] drm/msm/dsi: phy: use of_device_get_match_data Dmitry Baryshkov
2021-06-21 22:11 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 7/8] drm/msm/dsi: drop msm_dsi_phy_get_shared_timings Dmitry Baryshkov
2021-06-21 22:41 ` [Freedreno] " abhinavk
2021-05-15 13:12 ` [PATCH 8/8] drm/msm/dsi: remove msm_dsi_dphy_timing from msm_dsi_phy Dmitry Baryshkov
2021-06-21 22:43 ` [Freedreno] " abhinavk
2021-06-21 22:57 ` Dmitry Baryshkov
2021-06-10 13:48 ` [PATCH 0/8] dsi: rework clock parents and timing handling Dmitry Baryshkov
2021-06-10 16:34 ` abhinavk [this message]
2021-06-21 22:01 ` [Freedreno] " abhinavk
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=acc08fd48c98af3007ad3d8d810ff335@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@kernel.org \
--cc=sean@poorly.run \
/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