Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Marijn Suijten <marijn.suijten@somainline.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Krishna Manikandan <quic_mkrishn@quicinc.com>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Joerg Roedel <joro@8bytes.org>,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH v2 07/13] drm/msm/dpu: Add SM6350 support
Date: Fri, 28 Apr 2023 16:03:54 +0300	[thread overview]
Message-ID: <bfed3b0a-9672-fa59-5591-27ad17f5e96c@linaro.org> (raw)
In-Reply-To: <k25jg7cez2kimpxr4ztbdzjr2adq6a2vjknyvfe5frxujtogfg@vhfdyt45unv6>

On 27/04/2023 18:37, Marijn Suijten wrote:
> On 2023-04-21 00:31:16, Konrad Dybcio wrote:
>> Add SM6350 support to the DPU1 driver to enable display output.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> 
> After addressing the comments from Dmitry (CURSOR0->DMA1 and
> CURSOR1->DMA2), this is:
> 
> Reviewed-by: Marijn Suijten <marijn.suijten@somainline.org>
> 
> See below for some nits.
> 
>> ---
>>   .../gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h | 191 +++++++++++++++++++++
>>   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c     |   1 +
>>   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h     |   3 +
>>   drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c            |   1 +
>>   4 files changed, 196 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h
>> new file mode 100644
>> index 000000000000..687a508cbaa6
>> --- /dev/null
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h
>> @@ -0,0 +1,191 @@
>> +/* SPDX-License-Identifier: GPL-2.0-only */
>> +/*
>> + * Copyright (c) 2022. Qualcomm Innovation Center, Inc. All rights reserved.
>> + * Copyright (c) 2015-2018, 2020 The Linux Foundation. All rights reserved.
>> + * Copyright (c) 2023, Linaro Limited
>> + */
>> +
>> +#ifndef _DPU_6_4_SM6350_H
>> +#define _DPU_6_4_SM6350_H
>> +
>> +static const struct dpu_caps sm6350_dpu_caps = {
>> +	.max_mixer_width = DEFAULT_DPU_OUTPUT_LINE_WIDTH,
>> +	.max_mixer_blendstages = 0x7,
>> +	.qseed_type = DPU_SSPP_SCALER_QSEED4,
> 
> I thought it was QSEED3LITE, but doesn't really matter as both are
> handled similarly.  It'll anyway change when I resubmit:

If I understood correctly, we mixed two things: hw stuff and the 
userspace library. QSEEDv2 was a hardware scaler. "qseedv3/v3lite/v4" 
are software library names that are used with the scalers newer than 
QSEED2. From the driver point we can ignore that and use scaler's hw 
version (which mostly but not always corresponds to the 3/3lite/4).

> 
> https://lore.kernel.org/linux-arm-msm/20230215-sspp-scaler-version-v1-0-416b1500b85b@somainline.org/T/#u
> 
> which should hardcode the register value directly, making this field
> superfluous.
> 
>> +	.has_src_split = true,
>> +	.has_dim_layer = true,
>> +	.has_idle_pc = true,
>> +	.max_linewidth = DEFAULT_DPU_OUTPUT_LINE_WIDTH,
>> +	.pixel_ram_size = DEFAULT_PIXEL_RAM_SIZE,
>> +};

-- 
With best wishes
Dmitry


  parent reply	other threads:[~2023-04-28 13:04 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 22:31 [PATCH v2 00/13] SM63(50|75) DPU support Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 01/13] dt-bindings: display/msm: dsi-controller-main: Add SM6350 Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 02/13] dt-bindings: display/msm: dsi-controller-main: Add SM6375 Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 03/13] dt-bindings: display/msm: Add SM6350 DPU Konrad Dybcio
2023-04-25 16:53   ` Rob Herring
2023-04-25 17:03   ` Rob Herring
2023-05-05 12:38     ` Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 04/13] dt-bindings: display/msm: Add SM6350 MDSS Konrad Dybcio
2023-04-21 12:56   ` Rob Herring
2023-04-20 22:31 ` [PATCH v2 05/13] dt-bindings: display/msm: Add SM6375 DPU Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 06/13] dt-bindings: display/msm: Add SM6375 MDSS Konrad Dybcio
2023-04-21 12:56   ` Rob Herring
2023-04-20 22:31 ` [PATCH v2 07/13] drm/msm/dpu: Add SM6350 support Konrad Dybcio
2023-04-20 22:41   ` Dmitry Baryshkov
2023-04-20 23:05     ` Konrad Dybcio
2023-04-20 23:06       ` Dmitry Baryshkov
2023-05-18 21:21       ` Dmitry Baryshkov
2023-04-27 15:37   ` Marijn Suijten
2023-04-27 15:48     ` Marijn Suijten
2023-04-28 12:25       ` Konrad Dybcio
2023-04-28 12:24     ` Konrad Dybcio
2023-04-28 13:03     ` Dmitry Baryshkov [this message]
2023-05-08 22:03       ` Marijn Suijten
2023-05-05 12:11     ` Dmitry Baryshkov
2023-05-08 22:04       ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 08/13] drm/msm: mdss: " Konrad Dybcio
2023-04-20 22:43   ` Dmitry Baryshkov
2023-04-27 21:03   ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 09/13] drm/msm/dpu: Add SM6375 support Konrad Dybcio
2023-04-20 22:48   ` Dmitry Baryshkov
2023-04-27 15:46   ` Marijn Suijten
2023-04-28 12:32     ` Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 10/13] drm/msm: mdss: " Konrad Dybcio
2023-04-20 22:49   ` Dmitry Baryshkov
2023-04-20 22:50   ` Dmitry Baryshkov
2023-04-20 23:06     ` Konrad Dybcio
2023-04-27 21:04   ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 11/13] iommu/arm-smmu-qcom: Add SM6375 DPU compatible Konrad Dybcio
2023-04-20 22:52   ` Dmitry Baryshkov
2023-04-20 22:31 ` [PATCH v2 12/13] iommu/arm-smmu-qcom: Add SM6350 " Konrad Dybcio
2023-04-20 22:51   ` Dmitry Baryshkov
2023-04-20 22:31 ` [PATCH v2 13/13] iommu/arm-smmu-qcom: Sort the compatible list alphabetically Konrad Dybcio
2023-04-20 22:53   ` 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=bfed3b0a-9672-fa59-5591-27ad17f5e96c@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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=quic_mkrishn@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sean@poorly.run \
    --cc=will@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