From: Johan Hovold <johan@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Robert Foss <rfoss@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Abel Vesa <abel.vesa@linaro.org>,
Richard Acayan <mailingradian@gmail.com>,
Rob Clark <robdclark@chromium.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/8] drm/msm/dpu: link DSPP_2/_3 blocks on X1E80100
Date: Tue, 17 Dec 2024 09:41:44 +0100 [thread overview]
Message-ID: <Z2E5SGIfAaKugNTP@hovoldconsulting.com> (raw)
In-Reply-To: <20241216-dpu-fix-catalog-v1-7-15bf0807dba1@linaro.org>
On Mon, Dec 16, 2024 at 10:27:28AM +0200, Dmitry Baryshkov wrote:
> Link DSPP_2 to the LM_2 and DSPP_3 to the LM_3 mixer blocks.
Please say something about why you're doing this and what the expected
outcome of doing so is.
There is currently no way for a third party (e.g. stable or distro
maintainer) to determine what this patch does, if it needs to be
backported or if it's essentially just a clean up like Abhinav indicated
in one of his replies.
> Fixes: e3b1f369db5a ("drm/msm/dpu: Add X1E80100 support")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Johan
next prev parent reply other threads:[~2024-12-17 8:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 8:27 [PATCH 0/8] drm/msm/dpu: catalog corrections Dmitry Baryshkov
2024-12-16 8:27 ` [PATCH 1/8] drm/msm/dpu: link DSPP_2/_3 blocks on SM8150 Dmitry Baryshkov
2024-12-16 21:11 ` Abhinav Kumar
2024-12-16 22:21 ` Dmitry Baryshkov
2024-12-16 22:46 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 2/8] drm/msm/dpu: link DSPP_2/_3 blocks on SC8180X Dmitry Baryshkov
2024-12-16 21:15 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 3/8] drm/msm/dpu: link DSPP_2/_3 blocks on SM8250 Dmitry Baryshkov
2024-12-16 22:04 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 4/8] drm/msm/dpu: link DSPP_2/_3 blocks on SM8350 Dmitry Baryshkov
2024-12-16 22:05 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 5/8] drm/msm/dpu: link DSPP_2/_3 blocks on SM8550 Dmitry Baryshkov
2024-12-16 22:13 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 6/8] drm/msm/dpu: link DSPP_2/_3 blocks on SM8650 Dmitry Baryshkov
2024-12-16 22:14 ` Abhinav Kumar
2024-12-16 8:27 ` [PATCH 7/8] drm/msm/dpu: link DSPP_2/_3 blocks on X1E80100 Dmitry Baryshkov
2024-12-16 22:42 ` Abhinav Kumar
2024-12-17 8:41 ` Johan Hovold [this message]
2024-12-17 10:38 ` Dmitry Baryshkov
2024-12-19 10:14 ` Johan Hovold
2024-12-16 8:27 ` [PATCH 8/8] drm/msm/dpu: provide DSPP and correct LM config for SDM670 Dmitry Baryshkov
2024-12-16 23:35 ` Abhinav Kumar
2024-12-16 23:36 ` [PATCH 0/8] drm/msm/dpu: catalog corrections Abhinav Kumar
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=Z2E5SGIfAaKugNTP@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.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=mailingradian@gmail.com \
--cc=marijn.suijten@somainline.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.