dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Manasi Navare <manasi.d.navare@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 10/23] drm/dsc: Add helpers for DSC picture parameter set infoframes
Date: Fri, 3 Aug 2018 12:55:14 -0700	[thread overview]
Message-ID: <20180803195513.GB1830@intel.com> (raw)
In-Reply-To: <153332543109.15394.5754498060825727180@skylake-alporthouse-com>

On Fri, Aug 03, 2018 at 08:43:51PM +0100, Chris Wilson wrote:
> Quoting Manasi Navare (2018-08-03 20:18:42)
> > On Tue, Jul 31, 2018 at 10:16:45PM +0100, Chris Wilson wrote:
> > > Quoting Manasi Navare (2018-07-31 22:07:06)
> > > > +       /* PPS 4 */
> > > > +       pps_sdp->pps_payload.pps_4 = (u8)((dsc_cfg->bits_per_pixel &
> > > > +                                          DSC_PPS_BPP_HIGH_MASK) >>
> > > > +                                         DSC_PPS_MSB_SHIFT) |
> > > 
> > > To avoid overhanging cliffs, insert the newline after the sequence
> > > point. Quite a few examples throughout the series that would benefit
> > > from more judicial placement of line breaks.
> > 
> > What exactly are you refering to by sequence point here?
> 
> Which ever makes sense visually, here '='.
> 
> pps_sdp->pps_payload.pps_4 =
> 	dsc_cfg->bits_per_pixel >> X << DSC_PPS_MSB_SHIFT |
> 	dsc_cfg->vbr_enable << DSC_PPS_VBR_EN_SHIFT |
> 	dsc_cfg->enable422 << DSC_PPS_SIMPLE422_SHIFT |
> 	dsc_cfg->convert_rgb << DSC_PPS_CONVERT_RGB_SHIFT |
> 	dsc_cfg->block_pred_enable << DSC_PPS_BLOCK_PRED_EN_SHIFT;

Ok understood about the sequence point

> 
> If you want to mask with 0xff do it without having to refer to C type promotion
> rules.

This point is still not clear. is this not correct:
(dsc_cfg->bits_per_pixel & DSC_PPS_BPP_HIGH_MASK) >> DSC_PPS_MSB_SHIFT

> 
> > > Furthermore, you only need the SPDX shorthand rather than full licence
> > > text.
> > 
> > Here the header is what all the other .c files in drm have. They all tend to use
> > complete text.
> 
> And they all need updating, eventually. There's no reason for new file
> to use the old style.
> 
> > Are you suggesting just adding SPDX-License-Identifier: GPL-2.0+ at the begining of the file?
> > Should I remove the entire paragraph about the Copyright?
> 
> No, the code is MIT. You replace the licence with just a SPDX link.

Could you give an example here for the correct way of adding SPDX info in the header and what part
of the existing header needs to stay?
That would be helpful.

Manasi
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-08-03 19:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 21:06 [PATCH v2 00/23] Display Stream Compression enabling on eDP/DP Manasi Navare
2018-07-31 21:06 ` [PATCH v2 01/23] drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT Manasi Navare
2018-07-31 22:17   ` Srivatsa, Anusha
2018-07-31 21:06 ` [PATCH v2 03/23] drm/dp: DRM DP helper/macros to get DP sink DSC parameters Manasi Navare
2018-07-31 23:33   ` Srivatsa, Anusha
2018-07-31 21:07 ` [PATCH v2 06/23] drm/dp: Define payload size for DP SDP PPS packet Manasi Navare
2018-07-31 21:07 ` [PATCH v2 07/23] drm/dsc: Define Display Stream Compression PPS infoframe Manasi Navare
2018-08-17 19:31   ` Srivatsa, Anusha
2018-08-23 20:08     ` Manasi Navare
2018-08-23 19:40   ` Harry Wentland
2018-08-23 20:12     ` Manasi Navare
2018-07-31 21:07 ` [PATCH v2 08/23] drm/dsc: Define VESA Display Stream Compression Capabilities Manasi Navare
2018-08-23 20:01   ` Harry Wentland
2018-08-28 21:12     ` Srivatsa, Anusha
2018-07-31 21:07 ` [PATCH v2 09/23] drm/dsc: Define Rate Control values that do not change over configurations Manasi Navare
2018-09-10 19:41   ` Manasi Navare
2018-07-31 21:07 ` [PATCH v2 10/23] drm/dsc: Add helpers for DSC picture parameter set infoframes Manasi Navare
2018-07-31 21:16   ` Chris Wilson
2018-08-03 19:18     ` Manasi Navare
2018-08-03 19:43       ` Chris Wilson
2018-08-03 19:55         ` Manasi Navare [this message]
2018-08-23 19:58   ` Harry Wentland
2018-07-31 21:07 ` [PATCH v2 14/23] drm/dsc: Define the DSC 1.1 and 1.2 Line Buffer depth constants Manasi Navare

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=20180803195513.GB1830@intel.com \
    --to=manasi.d.navare@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).