From: Vinod Koul <vkoul@kernel.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Jonathan Marek <jonathan@marek.ca>,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-kernel@vger.kernel.org,
Abhinav Kumar <abhinavk@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
freedreno@lists.freedesktop.org,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [Freedreno] [PATCH v3 12/13] drm/msm/dsi: Add support for DSC configuration
Date: Wed, 23 Mar 2022 16:27:59 +0530 [thread overview]
Message-ID: <Yjr9N4DPdOyi7CO5@matsya> (raw)
In-Reply-To: <20220322185925.nszstmi5silgefd5@SoMainline.org>
On 22-03-22, 19:59, Marijn Suijten wrote:
> On 2022-03-22 22:46:50, Vinod Koul wrote:
> > On 17-02-22, 16:11, Marijn Suijten wrote:
> > > Hi Vinod,
> > >
> > > Thanks for taking time to go through this review, please find some
> > > clarifications below.
> > >
> > > On 2022-02-17 16:44:04, Vinod Koul wrote:
> > > > Hi Marijn,
> > > >
> > > > On 11-12-21, 01:03, Marijn Suijten wrote:
> > > >
> > > > > > +static int dsi_dsc_update_pic_dim(struct msm_display_dsc_config *dsc,
> > > > > > + int pic_width, int pic_height)
> > > > >
> > > > > This function - adopted from downstream - does not seem to perform a
> > > > > whole lot, especially without the modulo checks against the slice size.
> > > > > Perhaps it can be inlined?
> > > >
> > > > Most of the code here is :)
> > > >
> > > > This was split from downstream code to check and update dimension. We
> > > > can inline this, or should we leave that to compiler. I am not a very
> > > > big fan of inlining...
> > >
> > > It doesn't seem beneficial to code readability to have this function,
> > > which is only called just once and also has the same struct members read
> > > in a `DBG()` directly, abstracted away to a function. Not really
> > > concerned about generated code/performance FWIW.
> > >
> > > Also note that the caller isn't checking the `-EINVAL` result...
> >
> > I have made this void inline.
>
> Perhaps there is a misunderstanding here: with inlining I am referring
> to the process of transplanting the _function body_ to the only
> call-site, not adding the `inline` keyword nor changing this to `void`.
>
> The checks that make this function return `-EINVAL` seem valid, so the
> caller should check it instead of removing the return?
Okay somehow I misunderstood then, let me see how the code looks in this
case then
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Jonathan Marek <jonathan@marek.ca>,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-kernel@vger.kernel.org,
Abhinav Kumar <abhinavk@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
dri-devel@lists.freedesktop.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
freedreno@lists.freedesktop.org,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [Freedreno] [PATCH v3 12/13] drm/msm/dsi: Add support for DSC configuration
Date: Wed, 23 Mar 2022 16:27:59 +0530 [thread overview]
Message-ID: <Yjr9N4DPdOyi7CO5@matsya> (raw)
In-Reply-To: <20220322185925.nszstmi5silgefd5@SoMainline.org>
On 22-03-22, 19:59, Marijn Suijten wrote:
> On 2022-03-22 22:46:50, Vinod Koul wrote:
> > On 17-02-22, 16:11, Marijn Suijten wrote:
> > > Hi Vinod,
> > >
> > > Thanks for taking time to go through this review, please find some
> > > clarifications below.
> > >
> > > On 2022-02-17 16:44:04, Vinod Koul wrote:
> > > > Hi Marijn,
> > > >
> > > > On 11-12-21, 01:03, Marijn Suijten wrote:
> > > >
> > > > > > +static int dsi_dsc_update_pic_dim(struct msm_display_dsc_config *dsc,
> > > > > > + int pic_width, int pic_height)
> > > > >
> > > > > This function - adopted from downstream - does not seem to perform a
> > > > > whole lot, especially without the modulo checks against the slice size.
> > > > > Perhaps it can be inlined?
> > > >
> > > > Most of the code here is :)
> > > >
> > > > This was split from downstream code to check and update dimension. We
> > > > can inline this, or should we leave that to compiler. I am not a very
> > > > big fan of inlining...
> > >
> > > It doesn't seem beneficial to code readability to have this function,
> > > which is only called just once and also has the same struct members read
> > > in a `DBG()` directly, abstracted away to a function. Not really
> > > concerned about generated code/performance FWIW.
> > >
> > > Also note that the caller isn't checking the `-EINVAL` result...
> >
> > I have made this void inline.
>
> Perhaps there is a misunderstanding here: with inlining I am referring
> to the process of transplanting the _function body_ to the only
> call-site, not adding the `inline` keyword nor changing this to `void`.
>
> The checks that make this function return `-EINVAL` seem valid, so the
> caller should check it instead of removing the return?
Okay somehow I misunderstood then, let me see how the code looks in this
case then
--
~Vinod
next prev parent reply other threads:[~2022-03-23 10:58 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 6:22 [PATCH v3 00/13] drm/msm: Add Display Stream Compression Support Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-16 6:22 ` [PATCH v3 01/13] drm/msm/dsi: add support for dsc data Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:53 ` Dmitry Baryshkov
2021-11-24 15:53 ` Dmitry Baryshkov
2021-11-30 1:14 ` [Freedreno] " Abhinav Kumar
2021-11-30 1:14 ` Abhinav Kumar
2021-11-16 6:22 ` [PATCH v3 02/13] drm/msm/disp/dpu1: Add support for DSC Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:35 ` Dmitry Baryshkov
2021-11-24 15:35 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 03/13] drm/msm/disp/dpu1: Add support for DSC in pingpong block Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2022-02-17 21:54 ` Marijn Suijten
2022-02-17 21:54 ` Marijn Suijten
2022-02-17 22:06 ` Marijn Suijten
2022-02-17 22:06 ` Marijn Suijten
2022-02-17 22:12 ` Dmitry Baryshkov
2022-02-17 22:12 ` Dmitry Baryshkov
2022-02-17 22:39 ` Marijn Suijten
2022-02-17 22:39 ` Marijn Suijten
2021-11-16 6:22 ` [PATCH v3 04/13] drm/msm/disp/dpu1: Add DSC for SDM845 to hw_catalog Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-16 6:22 ` [PATCH v3 05/13] drm/msm/disp/dpu1: Don't use DSC with mode_3d Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:39 ` Dmitry Baryshkov
2021-11-24 15:39 ` Dmitry Baryshkov
2021-11-24 15:40 ` Dmitry Baryshkov
2021-11-24 15:40 ` Dmitry Baryshkov
2021-11-24 15:57 ` Dmitry Baryshkov
2021-11-24 15:57 ` Dmitry Baryshkov
2021-11-24 15:43 ` Dmitry Baryshkov
2021-11-24 15:43 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 06/13] drm/msm/disp/dpu1: Add DSC support in hw_ctl Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:40 ` Dmitry Baryshkov
2021-11-24 15:40 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 07/13] drm/msm/disp/dpu1: Add support for DSC in encoder Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:58 ` Dmitry Baryshkov
2021-11-24 15:58 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 08/13] drm/msm: Add missing structure documentation Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-16 6:22 ` [PATCH v3 09/13] drm/msm/disp/dpu1: Add support for DSC in topology Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 15:59 ` Dmitry Baryshkov
2021-11-24 15:59 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 10/13] drm/msm/disp/dpu1: Add DSC support in RM Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 16:01 ` Dmitry Baryshkov
2021-11-24 16:01 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 11/13] drm/msm/dsi: add mode valid callback for dsi_mgr Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 20:33 ` Dmitry Baryshkov
2021-11-24 20:33 ` Dmitry Baryshkov
2021-11-16 6:22 ` [PATCH v3 12/13] drm/msm/dsi: Add support for DSC configuration Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-18 21:47 ` kernel test robot
2021-11-18 21:47 ` kernel test robot
2021-11-18 21:47 ` kernel test robot
2021-11-24 16:21 ` Dmitry Baryshkov
2021-11-24 16:21 ` Dmitry Baryshkov
2021-11-24 16:27 ` Dmitry Baryshkov
2021-11-24 16:27 ` Dmitry Baryshkov
2021-12-11 0:03 ` Marijn Suijten
2021-12-11 0:03 ` Marijn Suijten
2022-02-17 11:14 ` [Freedreno] " Vinod Koul
2022-02-17 11:14 ` Vinod Koul
2022-02-17 15:11 ` Marijn Suijten
2022-02-17 15:11 ` Marijn Suijten
2022-03-22 17:16 ` Vinod Koul
2022-03-22 17:16 ` Vinod Koul
2022-03-22 18:59 ` Marijn Suijten
2022-03-22 18:59 ` Marijn Suijten
2022-03-23 10:57 ` Vinod Koul [this message]
2022-03-23 10:57 ` Vinod Koul
2021-11-16 6:22 ` [PATCH v3 13/13] drm/msm/dsi: Pass DSC params to drm_panel Vinod Koul
2021-11-16 6:22 ` Vinod Koul
2021-11-24 16:28 ` Dmitry Baryshkov
2021-11-24 16:28 ` Dmitry Baryshkov
2021-11-24 16:51 ` Dmitry Baryshkov
2021-11-24 16:51 ` 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=Yjr9N4DPdOyi7CO5@matsya \
--to=vkoul@kernel.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--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=jeffrey.l.hugo@gmail.com \
--cc=jonathan@marek.ca \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.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 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.