[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220804143854.1544395-1-dianders@chromium.org>
Date: Thu, 4 Aug 2022 07:38:47 -0700
From: Douglas Anderson <dianders@...omium.org>
To: Rob Clark <robdclark@...il.com>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Mark Brown <broonie@...nel.org>, linux-arm-msm@...r.kernel.org,
freedreno@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
Douglas Anderson <dianders@...omium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...ainline.org>,
Archit Taneja <architt@...eaurora.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
Jonathan Marek <jonathan@...ek.ca>,
José Expósito <jose.exposito89@...il.com>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Loic Poulain <loic.poulain@...aro.org>,
Marijn Suijten <marijn.suijten@...ainline.org>,
Rajeev Nandan <quic_rajeevny@...cinc.com>,
Sean Paul <sean@...rly.run>,
Stephen Boyd <swboyd@...omium.org>,
Vinod Koul <vkoul@...nel.org>,
Vladimir Lypak <vladimir.lypak@...il.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH v4 0/6] drm/msm/dsi regulator improvements
The main goal of this series is to make a small dent in cleaning up
the way we deal with regulator loads for DSI drivers.
As of v3 of this series, the regulator API improvements needed for the
later patches in the series are merged into mainline. Thus this series
only contains the DSI changes now.
I'd expect:
* The first two patches are bugfixes found while converting the DSI
driver over. Those could land any time.
* The third patch ("drm/msm/dsi: Don't set a load before disabling a
regulator") is a patch a sent the other day verbatim, included in
this series because it's highly related. It could land any
time.
* The next two patches use the new APIs. Since those APIs are now in
mainline those could also land any time.
* The last patch is just cleanup I noticed as I was touching the
function. It's not really related to regulators but it applies atop
these. In theory it could be rebased to land separately.
Changes in v4:
- Correct the commit that this Fixes.
- Mention error code change in commit message.
- Use more gooder English in the commit description.
Changes in v3:
- ("Improve dsi_phy_driver_probe() probe error handling") new for v3.
- Do all the PHYs too.
- Fix typo in commit message.
- Get rid of error print after devm_regulator_bulk_get_const().
- Just directly call the bulk commands; get rid of the wrapper.
- Update commit message to point at the git hash of the regulator change.
Changes in v2:
- ("Fix number of regulators for SDM660") new for v2.
- ("Fix number of regulators for msm8996_dsi_cfg") new for v2.
- ("Take advantage of devm_regulator_bulk_get_const") new for v2.
- ("Use the new regulator bulk feature to specify the load") new for v2.
Douglas Anderson (6):
drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
drm/msm/dsi: Fix number of regulators for SDM660
drm/msm/dsi: Don't set a load before disabling a regulator
drm/msm/dsi: Use the new regulator bulk feature to specify the load
drm/msm/dsi: Take advantage of devm_regulator_bulk_get_const()
drm/msm/dsi: Improve dsi_phy_driver_probe() probe error handling
drivers/gpu/drm/msm/dsi/dsi.h | 13 --
drivers/gpu/drm/msm/dsi/dsi_cfg.c | 172 +++++++++---------
drivers/gpu/drm/msm/dsi/dsi_cfg.h | 3 +-
drivers/gpu/drm/msm/dsi/dsi_host.c | 96 ++--------
drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 160 ++++------------
drivers/gpu/drm/msm/dsi/phy/dsi_phy.h | 5 +-
drivers/gpu/drm/msm/dsi/phy/dsi_phy_10nm.c | 20 +-
drivers/gpu/drm/msm/dsi/phy/dsi_phy_14nm.c | 32 ++--
drivers/gpu/drm/msm/dsi/phy/dsi_phy_20nm.c | 14 +-
drivers/gpu/drm/msm/dsi/phy/dsi_phy_28nm.c | 28 +--
.../gpu/drm/msm/dsi/phy/dsi_phy_28nm_8960.c | 12 +-
drivers/gpu/drm/msm/dsi/phy/dsi_phy_7nm.c | 32 ++--
12 files changed, 197 insertions(+), 390 deletions(-)
--
2.37.1.455.g008518b4e5-goog
Powered by blists - more mailing lists