From: "Ville Syrjälä" <ville.syrjala@linux.intel.com> To: Jani Nikula <jani.nikula@intel.com> Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Subject: Re: [PATCH v2 02/11] drm/edid: fix reduced blanking support check Date: Mon, 28 Mar 2022 19:31:41 +0300 [thread overview] Message-ID: <YkHi7QmemzCXP6QR@intel.com> (raw) In-Reply-To: <8bb6a4997680685e1a6b8978ac34befd955578f4.1648458971.git.jani.nikula@intel.com> On Mon, Mar 28, 2022 at 12:17:16PM +0300, Jani Nikula wrote: > The reduced blanking bit is valid only for CVT, indicated by display > range limits flags 0x04. > > Signed-off-by: Jani Nikula <jani.nikula@intel.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> > --- > drivers/gpu/drm/drm_edid.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c > index 1b552fe54f38..13d05062d68c 100644 > --- a/drivers/gpu/drm/drm_edid.c > +++ b/drivers/gpu/drm/drm_edid.c > @@ -2408,7 +2408,7 @@ is_rb(struct detailed_timing *t, void *data) > if (!is_display_descriptor(r, EDID_DETAIL_MONITOR_RANGE)) > return; > > - if (r[15] & 0x10) > + if (r[10] == DRM_EDID_CVT_SUPPORT_FLAG && r[15] & 0x10) > *(bool *)data = true; > } > > -- > 2.30.2 -- Ville Syrjälä Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com> To: Jani Nikula <jani.nikula@intel.com> Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Subject: Re: [Intel-gfx] [PATCH v2 02/11] drm/edid: fix reduced blanking support check Date: Mon, 28 Mar 2022 19:31:41 +0300 [thread overview] Message-ID: <YkHi7QmemzCXP6QR@intel.com> (raw) In-Reply-To: <8bb6a4997680685e1a6b8978ac34befd955578f4.1648458971.git.jani.nikula@intel.com> On Mon, Mar 28, 2022 at 12:17:16PM +0300, Jani Nikula wrote: > The reduced blanking bit is valid only for CVT, indicated by display > range limits flags 0x04. > > Signed-off-by: Jani Nikula <jani.nikula@intel.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> > --- > drivers/gpu/drm/drm_edid.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c > index 1b552fe54f38..13d05062d68c 100644 > --- a/drivers/gpu/drm/drm_edid.c > +++ b/drivers/gpu/drm/drm_edid.c > @@ -2408,7 +2408,7 @@ is_rb(struct detailed_timing *t, void *data) > if (!is_display_descriptor(r, EDID_DETAIL_MONITOR_RANGE)) > return; > > - if (r[15] & 0x10) > + if (r[10] == DRM_EDID_CVT_SUPPORT_FLAG && r[15] & 0x10) > *(bool *)data = true; > } > > -- > 2.30.2 -- Ville Syrjälä Intel
next prev parent reply other threads:[~2022-03-28 16:31 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 9:17 [PATCH v2 00/11] drm/edid: constify EDID parsing, with some fixes Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 01/11] drm/edid: don't modify EDID while parsing Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 02/11] drm/edid: fix reduced blanking support check Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 16:31 ` Ville Syrjälä [this message] 2022-03-28 16:31 ` Ville Syrjälä 2022-03-28 9:17 ` [PATCH v2 03/11] drm/edid: slightly restructure timing and non-timing descriptor structs Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:44 ` Jani Nikula 2022-03-28 9:44 ` Jani Nikula 2022-03-28 9:44 ` [Intel-gfx] " Jani Nikula 2022-03-28 11:45 ` kernel test robot 2022-03-28 13:20 ` Jani Nikula 2022-03-28 13:20 ` Jani Nikula 2022-03-28 13:20 ` Jani Nikula 2022-03-28 12:26 ` kernel test robot 2022-03-28 12:26 ` kernel test robot 2022-03-28 12:46 ` kernel test robot 2022-03-28 9:17 ` [PATCH v2 04/11] drm/edid: pass a timing pointer to is_display_descriptor() Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 05/11] drm/edid: use struct detailed_timing member access in is_rb() Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 06/11] drm/edid: use struct detailed_data_monitor_range member access in gtf2 functions Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 07/11] drm/edid: constify struct detailed_timing in lower level parsing Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 08/11] drm/edid: constify struct detailed_timing in parsing callbacks Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 09/11] drm/edid: constify struct edid passed to detailed blocks Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 10/11] drm/edid: constify struct edid passed around in callbacks and closure Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 9:17 ` [PATCH v2 11/11] drm/edid: add more general struct edid constness in the interfaces Jani Nikula 2022-03-28 9:17 ` [Intel-gfx] " Jani Nikula 2022-03-28 13:26 ` [PATCH v2 00/11] drm/edid: constify EDID parsing, with some fixes Jani Nikula 2022-03-28 13:26 ` [Intel-gfx] " Jani Nikula 2022-03-28 14:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2022-03-28 14:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork 2022-03-28 15:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2022-03-28 17:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=YkHi7QmemzCXP6QR@intel.com \ --to=ville.syrjala@linux.intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jani.nikula@intel.com \ /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: linkBe 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.