Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 29 May 2023 19:22:15 +0100
From:   Conor Dooley <conor@kernel.org>
To:     Luca Weiss <luca@z3ntu.xyz>
Cc:     ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org,
        Rob Clark <robdclark@gmail.com>,
        Abhinav Kumar <quic_abhinavk@quicinc.com>,
        Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
        Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
        Daniel Vetter <daniel@ffwll.ch>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Krishna Manikandan <quic_mkrishn@quicinc.com>,
        Andy Gross <agross@kernel.org>,
        Bjorn Andersson <andersson@kernel.org>,
        Konrad Dybcio <konrad.dybcio@linaro.org>,
        linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
        freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: msm: dsi-phy-28nm: Document msm8226
 compatible
Message-ID: <20230529-encircle-cherub-374102ca43d4@spud>
References: <20230308-msm8226-mdp-v1-0-679f335d3d5b@z3ntu.xyz>
 <20230308-msm8226-mdp-v1-1-679f335d3d5b@z3ntu.xyz>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="UyjEm4CeDHfnthCw"
Content-Disposition: inline
In-Reply-To: <20230308-msm8226-mdp-v1-1-679f335d3d5b@z3ntu.xyz>
Precedence: bulk


--UyjEm4CeDHfnthCw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 29, 2023 at 11:43:58AM +0200, Luca Weiss wrote:
> The MSM8226 SoC uses a slightly different 28nm dsi phy. Add a new
> compatible for it.
>=20
> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> ---
>  Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml | 1 +
>  Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml    | 1 +
>  2 files changed, 2 insertions(+)
>=20
> diff --git a/Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.y=
aml b/Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml
> index cf4a338c4661..bd70c3873ca9 100644
> --- a/Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml
> @@ -18,6 +18,7 @@ properties:
>        - qcom,dsi-phy-28nm-hpm
>        - qcom,dsi-phy-28nm-hpm-fam-b
>        - qcom,dsi-phy-28nm-lp
> +      - qcom,dsi-phy-28nm-8226

How come the order is different in both places?

Acked-by: Conor Dooley <conor.dooley@microchip.com>

Thanks,
Conor.

>        - qcom,dsi-phy-28nm-8960
> =20
>    reg:
> diff --git a/Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml=
 b/Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml
> index b0100105e428..db9f07c6142d 100644
> --- a/Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/qcom,mdss.yaml
> @@ -125,6 +125,7 @@ patternProperties:
>            - qcom,dsi-phy-14nm-660
>            - qcom,dsi-phy-14nm-8953
>            - qcom,dsi-phy-20nm
> +          - qcom,dsi-phy-28nm-8226
>            - qcom,dsi-phy-28nm-hpm
>            - qcom,dsi-phy-28nm-lp
>            - qcom,hdmi-phy-8084
>=20
> --=20
> 2.40.1
>=20

--UyjEm4CeDHfnthCw
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZHTtVwAKCRB4tDGHoIJi
0nvKAQDbhG5jqoLQjbATFU8ogWNuoWFeY5pQPfj1a1MKxd++VAD/fQ/wznbK/2Ma
4WV5Mn40WKJywRLn/w7MU15yVh9TGgk=
=M/da
-----END PGP SIGNATURE-----

--UyjEm4CeDHfnthCw--