From: Neil Armstrong <neil.armstrong@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
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>, Daniel Vetter <daniel@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 5/5] drm/msm: dpu1: sm8550: move split clock controls to sspp entries
Date: Tue, 10 Oct 2023 10:00:29 +0200 [thread overview]
Message-ID: <cd6c14ad-dd86-4fe3-8264-5ec70cffdd1e@linaro.org> (raw)
In-Reply-To: <7eecc9af-3d4f-43ba-8262-e58858bbe417@linaro.org>
On 09/10/2023 19:10, Dmitry Baryshkov wrote:
> On 09/10/2023 19:36, Neil Armstrong wrote:
>> The SM8550 has the SSPP clk_ctrl in the SSPP registers, move them
>> out of the MDP top.
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> .../gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h | 35 ++++++++++------------
>> 1 file changed, 15 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h
>> index 7bed819dfc39..527ec020fba4 100644
>> --- a/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_9_0_sm8550.h
>> @@ -24,16 +24,6 @@ static const struct dpu_mdp_cfg sm8550_mdp = {
>> .base = 0, .len = 0x494,
>> .features = BIT(DPU_MDP_PERIPH_0_REMOVED),
>> .clk_ctrls = {
>> - [DPU_CLK_CTRL_VIG0] = { .reg_off = 0x4330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_VIG1] = { .reg_off = 0x6330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_VIG2] = { .reg_off = 0x8330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_VIG3] = { .reg_off = 0xa330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA0] = { .reg_off = 0x24330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA1] = { .reg_off = 0x26330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA2] = { .reg_off = 0x28330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA3] = { .reg_off = 0x2a330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA4] = { .reg_off = 0x2c330, .bit_off = 0 },
>> - [DPU_CLK_CTRL_DMA5] = { .reg_off = 0x2e330, .bit_off = 0 },
>> [DPU_CLK_CTRL_REG_DMA] = { .reg_off = 0x2bc, .bit_off = 20 },
>
> Hmm, interesting. I even double-checked this. SSPP and WB have their own clock registers now. But the REG_DMA uses the main area (0x2bc).
yeah
>
>> },
>> };
>> @@ -73,6 +63,11 @@ static const struct dpu_ctl_cfg sm8550_ctl[] = {
>> },
>> };
>> +static const struct dpu_clk_ctrl_reg sm8550_sspp_clk_ctrl = {
>> + .reg_off = 0x330,
>> + .bit_off = 0
>> +};
>
> I don't think we even need this outside of dpu_hw_sspp. You can use core_major_rev to check whether the driver should use global clocks or per-SSPP / per-WB clocks register instead.
Ack
>
>> +
>> static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> {
>> .name = "sspp_0", .id = SSPP_VIG0,
>> @@ -81,7 +76,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_vig_sblk_0,
>> .xin_id = 0,
>> .type = SSPP_TYPE_VIG,
>> - .clk_ctrl = DPU_CLK_CTRL_VIG0,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_1", .id = SSPP_VIG1,
>> .base = 0x6000, .len = 0x344,
>> @@ -89,7 +84,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_vig_sblk_1,
>> .xin_id = 4,
>> .type = SSPP_TYPE_VIG,
>> - .clk_ctrl = DPU_CLK_CTRL_VIG1,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_2", .id = SSPP_VIG2,
>> .base = 0x8000, .len = 0x344,
>> @@ -97,7 +92,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_vig_sblk_2,
>> .xin_id = 8,
>> .type = SSPP_TYPE_VIG,
>> - .clk_ctrl = DPU_CLK_CTRL_VIG2,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_3", .id = SSPP_VIG3,
>> .base = 0xa000, .len = 0x344,
>> @@ -105,7 +100,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_vig_sblk_3,
>> .xin_id = 12,
>> .type = SSPP_TYPE_VIG,
>> - .clk_ctrl = DPU_CLK_CTRL_VIG3,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_8", .id = SSPP_DMA0,
>> .base = 0x24000, .len = 0x344,
>> @@ -113,7 +108,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sdm845_dma_sblk_0,
>> .xin_id = 1,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA0,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_9", .id = SSPP_DMA1,
>> .base = 0x26000, .len = 0x344,
>> @@ -121,7 +116,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sdm845_dma_sblk_1,
>> .xin_id = 5,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA1,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_10", .id = SSPP_DMA2,
>> .base = 0x28000, .len = 0x344,
>> @@ -129,7 +124,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sdm845_dma_sblk_2,
>> .xin_id = 9,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA2,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_11", .id = SSPP_DMA3,
>> .base = 0x2a000, .len = 0x344,
>> @@ -137,7 +132,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sdm845_dma_sblk_3,
>> .xin_id = 13,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA3,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_12", .id = SSPP_DMA4,
>> .base = 0x2c000, .len = 0x344,
>> @@ -145,7 +140,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_dma_sblk_4,
>> .xin_id = 14,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA4,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> }, {
>> .name = "sspp_13", .id = SSPP_DMA5,
>> .base = 0x2e000, .len = 0x344,
>> @@ -153,7 +148,7 @@ static const struct dpu_sspp_cfg sm8550_sspp[] = {
>> .sblk = &sm8550_dma_sblk_5,
>> .xin_id = 15,
>> .type = SSPP_TYPE_DMA,
>> - .clk_ctrl = DPU_CLK_CTRL_DMA5,
>> + .clk_ctrl_reg = &sm8550_sspp_clk_ctrl,
>> },
>> };
>>
>
next prev parent reply other threads:[~2023-10-10 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 16:36 [PATCH RFC 0/5] drm/msm: dpu1: correctly implement SSPP & WB Clock Control Split Neil Armstrong
2023-10-09 16:36 ` [PATCH RFC 1/5] drm/msm: dpu1: create a dpu_hw_clk_force_ctrl() helper Neil Armstrong
2023-10-09 16:57 ` Dmitry Baryshkov
2023-10-09 16:36 ` [PATCH RFC 2/5] drm/msm: dpu1: add setup_clk_force_ctrl() op to sspp & wb Neil Armstrong
2023-10-09 16:36 ` [PATCH RFC 3/5] drm/msm: dpu1: vbif: add dpu_vbif_setup_clk_force_ctrl() helper Neil Armstrong
2023-10-09 17:02 ` Dmitry Baryshkov
2023-10-09 16:36 ` [PATCH RFC 4/5] drm/msm: dpu1: call wb & sspp clk_force_ctrl op if split clock control Neil Armstrong
2023-10-09 17:07 ` Dmitry Baryshkov
2023-10-10 7:58 ` Neil Armstrong
2023-10-09 16:36 ` [PATCH RFC 5/5] drm/msm: dpu1: sm8550: move split clock controls to sspp entries Neil Armstrong
2023-10-09 17:10 ` Dmitry Baryshkov
2023-10-10 8:00 ` Neil Armstrong [this message]
2023-10-10 8:00 ` Neil Armstrong
2023-10-10 8:10 ` [PATCH RFC 0/5] drm/msm: dpu1: correctly implement SSPP & WB Clock Control Split Marijn Suijten
2023-10-10 8:12 ` Neil Armstrong
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=cd6c14ad-dd86-4fe3-8264-5ec70cffdd1e@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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