During the email discussion Aiqun Yu (Maria) pointed out that the file
names for some of the MSM display schema files might not be obvious.
Indeed they do not fully follow the established practice of matching the
file name and one of compat strings.
Move DSI PHY schemas to the PHY subdir (renaming
While the DSI PHY schema files describe the display-related hardware,
they still describe a PHY. Move all DSI PHY schema files to the phy/
subdir.
Signed-off-by: Dmitry Baryshkov
---
.../msm/dsi-phy-10nm.yaml => phy/qcom,dsi-phy-10nm.yaml} | 4 ++--
.../msm/dsi-phy-14nm.yaml => phy/qcom,dsi
Rename the Qualcomm MSM Display schemas to follow the main compatible
string instead of just using the block type. This follows the
established practice for YAML file names.
Cc: Aiqun Yu (Maria)
Signed-off-by: Dmitry Baryshkov
---
.../bindings/display/msm/{gmu.yaml => qcom,adreno-gmu.yaml}
Hi,
On 14/12/23 17:50, Helen Koike wrote:
On 14/12/2023 05:00, Dmitry Baryshkov wrote:
On Tue, 12 Dec 2023 at 18:04, Vignesh Raman
wrote:
build-kdl.sh was doing a `clone --depth 1` of the default branch,
then checking out a commit that might not be the latest of that
branch, resulting in c
On Thu, 21 Dec 2023 12:25:05 +0200, Dmitry Baryshkov wrote:
> While the DSI PHY schema files describe the display-related hardware,
> they still describe a PHY. Move all DSI PHY schema files to the phy/
> subdir.
>
> Signed-off-by: Dmitry Baryshkov
> ---
> .../msm/dsi-phy-10nm.yaml => phy/qcom
On Thu, 21 Dec 2023 12:25:06 +0200, Dmitry Baryshkov wrote:
> Rename the Qualcomm MSM Display schemas to follow the main compatible
> string instead of just using the block type. This follows the
> established practice for YAML file names.
>
> Cc: Aiqun Yu (Maria)
> Signed-off-by: Dmitry Barysh
Title typo: SC8108X -> SC8180X :)
On 2023-12-03 03:32:01, Dmitry Baryshkov wrote:
> Enable WB2 hardware block, enabling writeback support on this platform.
>
> Signed-off-by: Dmitry Baryshkov
> ---
> .../msm/disp/dpu1/catalog/dpu_5_1_sc8180x.h| 18 ++
> 1 file changed, 18 in
build-kdl.sh was doing a `clone --depth 1` of the default branch,
then checking out a commit that might not be the latest of that
branch, resulting in container build error.
https://gitlab.freedesktop.org/mesa/mesa/-/commit/5efa4d56 fixes
kdl commit fetch issue. Uprev mesa in drm-ci to fix this.