From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>,
robdclark@gmail.com, sean@poorly.run, swboyd@chromium.org,
dianders@chromium.org, vkoul@kernel.org, daniel@ffwll.ch,
agross@kernel.org
Cc: quic_abhinavk@quicinc.com, quic_sbillaka@quicinc.com,
freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/5] Add data-lanes and link-frequencies to dp_out endpoint
Date: Fri, 2 Dec 2022 08:18:22 +0200 [thread overview]
Message-ID: <8aa37c6f-e545-8d7a-1c34-b9dd7a46c5ad@linaro.org> (raw)
In-Reply-To: <1669933049-13106-1-git-send-email-quic_khsieh@quicinc.com>
On 02/12/2022 00:17, Kuogee Hsieh wrote:
> Add DP both data-lanes and link-frequencies property to dp_out endpoint and support
> functions to DP driver.
>
> Kuogee Hsieh (5):
> arm64: dts: qcom: add data-lanes and link-freuencies into dp_out
> endpoint
> dt-bindings: msm/dp: add data-lanes and link-frequencies property
> drm/msm/dp: parser data-lanes as property of dp_out endpoint
> drm/msm/dp: parser link-frequencies as property of dp_out endpoint
> drm/msm/dp: add support of max dp link rate
Also, please fix the email address list you are using.
>
> .../bindings/display/msm/dp-controller.yaml | 22 +++++++++----
> arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 6 +++-
> arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi | 6 +++-
> drivers/gpu/drm/msm/dp/dp_display.c | 4 +++
> drivers/gpu/drm/msm/dp/dp_panel.c | 7 ++--
> drivers/gpu/drm/msm/dp/dp_panel.h | 1 +
> drivers/gpu/drm/msm/dp/dp_parser.c | 38 ++++++++++++++++++----
> drivers/gpu/drm/msm/dp/dp_parser.h | 2 ++
> 8 files changed, 68 insertions(+), 18 deletions(-)
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-12-02 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 22:17 Kuogee Hsieh
2022-12-02 6:15 ` Dmitry Baryshkov
2022-12-02 6:18 ` Dmitry Baryshkov [this message]
2022-12-05 17:45 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=8aa37c6f-e545-8d7a-1c34-b9dd7a46c5ad@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.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
all inboxes | Powered by JetHome®