From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>,
dri-devel@lists.freedesktop.org, robdclark@gmail.com,
sean@poorly.run, swboyd@chromium.org, dianders@chromium.org,
vkoul@kernel.org, daniel@ffwll.ch, airlied@linux.ie,
agross@kernel.org, bjorn.andersson@linaro.org
Cc: quic_abhinavk@quicinc.com, quic_sbillaka@quicinc.com,
freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/4] arm64: dts: qcom: add data-lanes and link-freuencies into dp_out endpoint
Date: Thu, 1 Dec 2022 02:07:02 +0200 [thread overview]
Message-ID: <7bf73466-e476-4a1d-5dc0-1b63ea742226@linaro.org> (raw)
In-Reply-To: <1669852310-22360-2-git-send-email-quic_khsieh@quicinc.com>
On 01/12/2022 01:51, Kuogee Hsieh wrote:
> Move data-lanes property from mdss_dp node to dp_out endpoint. Also
> add link-frequencies property into dp_out endpoint as well. The last
> frequency specified at link-frequencies will be the max link rate
> supported by DP.
>
> Changes in v5:
> -- revert changes at sc7180.dtsi and sc7280.dtsi
> -- add &dp_out to sc7180-trogdor.dtsi and sc7280-herobrine.dtsi
>
> Changes in v6:
> -- add data-lanes and link-frequencies to yaml
>
> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
> ---
> .../devicetree/bindings/display/msm/dp-controller.yaml | 17 +++++++++++++++++
Separate patch. Also you didn't check the get_maintainers output, so
required parties were not included into the distribution.
Also as you'd check the get_maintainers output, please fix other email
addresses too.
> arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 6 +++++-
> arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi | 6 +++++-
> 3 files changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/dp-controller.yaml b/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> index 94bc6e1..af70343 100644
> --- a/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/dp-controller.yaml
> @@ -90,6 +90,20 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description: Output endpoint of the controller
>
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> +
> + properties:
> + link-frequencies: true
> + data-lanes: true
No. Use $ref for both of them.
> +
> + required:
> + - link-frequencies
> + - data-lanes
No, they are not required.
> +
> + additionalProperties: false
> +
deprecation of old data-lanes property?
> required:
> - compatible
> - reg
> @@ -158,6 +172,9 @@ examples:
> reg = <1>;
> endpoint {
> remote-endpoint = <&typec>;
> + data-lanes = <1 2>;
> + link-frequencies = /bits/ 64 <160000000 270000000
> + 540000000 810000000>;
I guess the number of zeroes is wrong here. This is 160 MHz ... 810 Mhz,
rather than 1.6 GHz ... 8.1 GHz
> };
> };
> };
> diff --git a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> index 754d2d6..39f0844 100644
> --- a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> @@ -812,7 +812,11 @@ hp_i2c: &i2c9 {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&dp_hot_plug_det>;
> - data-lanes = <0 1>;
> +};
> +
> +&dp_out {
> + data-lanes = <0 1>;
> + link-frequencies = /bits/ 64 <160000000 270000000 540000000>;
Same comment here.
> };
>
> &pm6150_adc {
> diff --git a/arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi b/arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi
> index 93e39fc..b7c343d 100644
> --- a/arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi
> @@ -440,7 +440,11 @@ ap_i2c_tpm: &i2c14 {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&dp_hot_plug_det>;
> - data-lanes = <0 1>;
> +};
> +
> +&dp_out {
> + data-lanes = <0 1>;
> + link-frequencies = /bits/ 64 <160000000 270000000 540000000 810000000>;
And here.
> };
>
> &mdss_mdp {
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-12-01 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 23:51 [PATCH v6 0/4] Add data-lanes and link-frequencies to dp_out endpoint Kuogee Hsieh
2022-11-30 23:51 ` [PATCH v6 1/4] arm64: dts: qcom: add data-lanes and link-freuencies into " Kuogee Hsieh
2022-12-01 0:07 ` Dmitry Baryshkov [this message]
2022-12-01 0:21 ` Dmitry Baryshkov
2022-12-01 17:32 ` Kuogee Hsieh
2022-12-01 17:49 ` Dmitry Baryshkov
2022-12-01 20:59 ` Kuogee Hsieh
2022-12-01 17:34 ` Kuogee Hsieh
2022-12-01 17:36 ` Dmitry Baryshkov
2022-11-30 23:51 ` [PATCH v6 2/4] drm/msm/dp: parser data-lanes as property of " Kuogee Hsieh
2022-11-30 23:58 ` Dmitry Baryshkov
2022-11-30 23:51 ` [PATCH v6 3/4] drm/msm/dp: parser link-frequencies " Kuogee Hsieh
2022-12-01 0:26 ` Dmitry Baryshkov
2022-11-30 23:51 ` [PATCH v6 4/4] drm/msm/dp: add support of max dp link rate Kuogee Hsieh
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=7bf73466-e476-4a1d-5dc0-1b63ea742226@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.org \
/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