From: Konrad Dybcio <konrad.dybcio@somainline.org> To: ~postmarketos/upstreaming@lists.sr.ht Cc: martin.botka@somainline.org, angelogioacchino.delregno@somainline.org, marijn.suijten@somainline.org, jamipkettunen@somainline.org, Konrad Dybcio <konrad.dybcio@somainline.org>, Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>, Abhinav Kumar <quic_abhinavk@quicinc.com>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Stephen Boyd <swboyd@chromium.org>, Bjorn Andersson <bjorn.andersson@linaro.org>, Kalyan Thota <quic_kalyant@quicinc.com>, Krishna Manikandan <quic_mkrishn@quicinc.com>, Yangtao Li <tiny.windzz@gmail.com>, linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH] drm/msm/dpu1: Add a common DPU1 compatible Date: Tue, 22 Feb 2022 02:26:37 +0100 [thread overview] Message-ID: <20220222012638.6650-1-konrad.dybcio@somainline.org> (raw) There is *almost no reason* to keep separate compatibles for different SoCs utilizing the DPU1 driver, as it checks the HW version at runtime. Introduce a common compatible, while not removing the old ones to keep old DT compatibility. Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org> --- Bar some very very very unlikely edge cases (such as need for some random quick being applied to one SoC from a family that shares DPU hw rev, but not the others, there is little to no reason to keep adding compatibles that don't mean anything. If this change is cool, then the question about what to do with dt-bindings arises... drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c index 47fe11a84a77..335018542a3a 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c @@ -1348,6 +1348,9 @@ static const struct dev_pm_ops dpu_pm_ops = { }; const struct of_device_id dpu_dt_match[] = { + { .compatible = "qcom,dpu1" }, + + /* Legacy compatibles for old DTs */ { .compatible = "qcom,sdm845-dpu", }, { .compatible = "qcom,sc7180-dpu", }, { .compatible = "qcom,sc7280-dpu", }, -- 2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Dybcio <konrad.dybcio@somainline.org> To: ~postmarketos/upstreaming@lists.sr.ht Cc: Kalyan Thota <quic_kalyant@quicinc.com>, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>, linux-arm-msm@vger.kernel.org, Konrad Dybcio <konrad.dybcio@somainline.org>, Abhinav Kumar <quic_abhinavk@quicinc.com>, jamipkettunen@somainline.org, Stephen Boyd <swboyd@chromium.org>, Yangtao Li <tiny.windzz@gmail.com>, martin.botka@somainline.org, dri-devel@lists.freedesktop.org, angelogioacchino.delregno@somainline.org, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, marijn.suijten@somainline.org, Bjorn Andersson <bjorn.andersson@linaro.org>, Sean Paul <sean@poorly.run>, Krishna Manikandan <quic_mkrishn@quicinc.com> Subject: [RFC PATCH] drm/msm/dpu1: Add a common DPU1 compatible Date: Tue, 22 Feb 2022 02:26:37 +0100 [thread overview] Message-ID: <20220222012638.6650-1-konrad.dybcio@somainline.org> (raw) There is *almost no reason* to keep separate compatibles for different SoCs utilizing the DPU1 driver, as it checks the HW version at runtime. Introduce a common compatible, while not removing the old ones to keep old DT compatibility. Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org> --- Bar some very very very unlikely edge cases (such as need for some random quick being applied to one SoC from a family that shares DPU hw rev, but not the others, there is little to no reason to keep adding compatibles that don't mean anything. If this change is cool, then the question about what to do with dt-bindings arises... drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c index 47fe11a84a77..335018542a3a 100644 --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c @@ -1348,6 +1348,9 @@ static const struct dev_pm_ops dpu_pm_ops = { }; const struct of_device_id dpu_dt_match[] = { + { .compatible = "qcom,dpu1" }, + + /* Legacy compatibles for old DTs */ { .compatible = "qcom,sdm845-dpu", }, { .compatible = "qcom,sc7180-dpu", }, { .compatible = "qcom,sc7280-dpu", }, -- 2.35.1
next reply other threads:[~2022-02-22 1:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-22 1:26 Konrad Dybcio [this message] 2022-02-22 1:26 ` [RFC PATCH] drm/msm/dpu1: Add a common DPU1 compatible Konrad Dybcio 2022-02-22 2:26 ` Dmitry Baryshkov 2022-02-22 2:26 ` Dmitry Baryshkov
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=20220222012638.6650-1-konrad.dybcio@somainline.org \ --to=konrad.dybcio@somainline.org \ --cc=airlied@linux.ie \ --cc=angelogioacchino.delregno@somainline.org \ --cc=bjorn.andersson@linaro.org \ --cc=daniel@ffwll.ch \ --cc=dmitry.baryshkov@linaro.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=freedreno@lists.freedesktop.org \ --cc=jamipkettunen@somainline.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=marijn.suijten@somainline.org \ --cc=martin.botka@somainline.org \ --cc=quic_abhinavk@quicinc.com \ --cc=quic_kalyant@quicinc.com \ --cc=quic_mkrishn@quicinc.com \ --cc=robdclark@gmail.com \ --cc=sean@poorly.run \ --cc=swboyd@chromium.org \ --cc=tiny.windzz@gmail.com \ --cc=~postmarketos/upstreaming@lists.sr.ht \ /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: linkBe 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.