From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-16.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1449CC47080 for ; Mon, 24 May 2021 07:31:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D934E61241 for ; Mon, 24 May 2021 07:31:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232295AbhEXHcc (ORCPT ); Mon, 24 May 2021 03:32:32 -0400 Received: from mail.kernel.org ([198.145.29.99]:37906 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232254AbhEXHcb (ORCPT ); Mon, 24 May 2021 03:32:31 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4032160E0B; Mon, 24 May 2021 07:31:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1621841464; bh=cREJ80BL8BLuZgT+HaJzUef/mFV18kZDbQk7m7I+jPU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eJsdxDzaBy1arpXCQzikBLvfQrnAFDhoK+HcBFvtv3nagX2qfuPSnkbjdGF08OcO5 LxSa8cp+3d/TCLTvb+JZXBI3rDzi4/gYnY2M2X09TKGi3EyKitxSdi+jybFOSKXhU1 r4gxzWQwFu+KcVhrcT9a7e9culSTiL1jbHz4mJ/mDSIIpun9+9Xl7wfUAUO1vbu1vo RFCDb9AzDRCvPsJ++HcipaCTdMfWSXzM+OsuD8E1jYFNlNhIiRpO3pRUZA+cg3O3Vl eTNML0luuoMeL10sXJ53apRLzlM2Bs1y53gg0pd9ndu1bx+MLMP+f5FSmF2QT4ihQJ BH3AMOgbVEa7A== Date: Mon, 24 May 2021 13:00:59 +0530 From: Vinod Koul To: Bjorn Andersson Cc: Rob Clark , linux-arm-msm@vger.kernel.org, David Airlie , Daniel Vetter , Jonathan Marek , Dmitry Baryshkov , Abhinav Kumar , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, Rob Herring , devicetree@vger.kernel.org Subject: Re: [RFC PATCH 02/13] dt-bindings: msm/dsi: Document Display Stream Compression (DSC) parameters Message-ID: References: <20210521124946.3617862-1-vkoul@kernel.org> <20210521124946.3617862-3-vkoul@kernel.org> <20210521144237.GZ2484@yoga> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210521144237.GZ2484@yoga> Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 21-05-21, 09:42, Bjorn Andersson wrote: > On Fri 21 May 07:49 CDT 2021, Vinod Koul wrote: > > > DSC enables streams to be compressed before we send to panel. This > > requires DSC enabled encoder and a panel to be present. So we add this > > information in board DTS and find if DSC can be enabled and the > > parameters required to configure DSC are added to binding document along > > with example > > > > Signed-off-by: Vinod Koul > > --- > > .../devicetree/bindings/display/msm/dsi.txt | 15 +++++++++++++++ > > 1 file changed, 15 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/display/msm/dsi.txt b/Documentation/devicetree/bindings/display/msm/dsi.txt > > index b9a64d3ff184..83d2fb92267e 100644 > > --- a/Documentation/devicetree/bindings/display/msm/dsi.txt > > +++ b/Documentation/devicetree/bindings/display/msm/dsi.txt > > @@ -48,6 +48,13 @@ Optional properties: > > - pinctrl-n: the "sleep" pinctrl state > > - ports: contains DSI controller input and output ports as children, each > > containing one endpoint subnode. > > +- qcom,mdss-dsc-enabled: Display Stream Compression (DSC) is enabled > > +- qcom,mdss-slice-height: DSC slice height in pixels > > +- qcom,mdss-slice-width: DSC slice width in pixels > > +- qcom,mdss-slice-per-pkt: DSC slices per packet > > +- qcom,mdss-bit-per-component: DSC bits per component > > +- qcom,mdss-bit-per-pixel: DSC bits per pixel > > +- qcom,mdss-block-prediction-enable: Block prediction mode of DSC enabled > > > > DSI Endpoint properties: > > - remote-endpoint: For port@0, set to phandle of the connected panel/bridge's > > @@ -188,6 +195,14 @@ Example: > > qcom,master-dsi; > > qcom,sync-dual-dsi; > > > > + qcom,mdss-dsc-enabled; > > To me the activation of DSC seems to be a property of the panel. I think there are three parts to the problem 1. Panel needs to support it 2. Host needs to support it 3. Someone needs to decide to use when both the above conditions are met. There are cases where above 1, 2 will be satisfied, but we might be okay without DSC too.. so how to decide when to do DSC :) I feel it is more of a system property. And I also think that these parameters here are host configuration and not really for panel... > > > + qcom,mdss-slice-height = <16>; > > + qcom,mdss-slice-width = <540>; > > + qcom,mdss-slice-per-pkt = <1>; > > + qcom,mdss-bit-per-component = <8>; > > + qcom,mdss-bit-per-pixel = <8>; > > + qcom,mdss-block-prediction-enable; > > Which of these properties relates to the DSC encoder and what needs to > be agreed with the sink? Can't we derive e.g. bpp from the information > we have from the attached panel already? Let me go back and check on this a bit more Thanks -- ~Vinod