From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <simon.ser@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] lib/igt_edid: fix detailed pixel timing analog/digital
Date: Tue, 30 Apr 2019 20:21:36 +0300 [thread overview]
Message-ID: <20190430172136.GH24299@intel.com> (raw)
In-Reply-To: <20190426080018.17686-1-simon.ser@intel.com>
On Fri, Apr 26, 2019 at 11:00:18AM +0300, Simon Ser wrote:
> The generated EDIDs were wrongly indicating that they support analog sync.
> Fixup the detailed timings flags to advertise digital sync instead.
>
> Currently the Linux kernel seems to ignore this completely. However I'd prefer
> to fix this anyway to make sure we don't run into issues if an EDID consumer
> actually cares about it.
>
> The header definitions for EDID_PT_* values has been re-organized to make it
> clearer in which situations the flags are relevant.
>
> Signed-off-by: Simon Ser <simon.ser@intel.com>
> Fixes: a2fd0489c87a4d647c339f98057e6a1550e0e2f5
I think the custom is to use the kernel style for these. The kernel docs
have the magic git config incantation listed somewhere.
> ---
>
> Changes from v1 to v2:
> - Fix misleading commit message
> - Revert the "misc" → "features" rename
> - Re-organize EDID_PT_* definitions to make them clearer
And this should be included in the commit message proper.
>
> lib/igt_edid.c | 2 +-
> lib/igt_edid.h | 14 ++++++++++----
> 2 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/lib/igt_edid.c b/lib/igt_edid.c
> index 52e66ab2..9d604b13 100644
> --- a/lib/igt_edid.c
> +++ b/lib/igt_edid.c
> @@ -110,7 +110,7 @@ void detailed_timing_set_mode(struct detailed_timing *dt, drmModeModeInfo *mode,
> pt->width_height_mm_hi = (width_mm & 0xF00) >> 4
> | (height_mm & 0xF00) >> 8;
>
> - pt->misc = 0;
> + pt->misc = EDID_PT_SYNC_DIGITAL_SEPARATE;
> if (mode->flags & DRM_MODE_FLAG_PHSYNC)
> pt->misc |= EDID_PT_HSYNC_POSITIVE;
> if (mode->flags & DRM_MODE_FLAG_PVSYNC)
> diff --git a/lib/igt_edid.h b/lib/igt_edid.h
> index bbcb939a..d0963033 100644
> --- a/lib/igt_edid.h
> +++ b/lib/igt_edid.h
> @@ -52,11 +52,17 @@ struct std_timing {
>
> #define DETAILED_TIMINGS_LEN 4
>
> +#define EDID_PT_STEREO (1 << 5)
> +#define EDID_PT_INTERLACED (1 << 7)
The 5,7,3,1,2 order is making my ocd tingle. Would be nice
to stick to a consistent order.
Anyways, apart from the style issues the meat of the patch
looks good to me:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> +
> +/* Sync type */
> +#define EDID_PT_SYNC_ANALOG 0
> +#define EDID_PT_SYNC_DIGITAL_COMPOSITE (0b10 << 3)
> +#define EDID_PT_SYNC_DIGITAL_SEPARATE (0b11 << 3)
> +
> +/* Applies to EDID_PT_SYNC_DIGITAL_SEPARATE only */
> #define EDID_PT_HSYNC_POSITIVE (1 << 1)
> #define EDID_PT_VSYNC_POSITIVE (1 << 2)
> -#define EDID_PT_SEPARATE_SYNC (3 << 3)
> -#define EDID_PT_STEREO (1 << 5)
> -#define EDID_PT_INTERLACED (1 << 7)
>
> struct detailed_pixel_timing {
> uint8_t hactive_lo;
> @@ -74,7 +80,7 @@ struct detailed_pixel_timing {
> uint8_t width_height_mm_hi;
> uint8_t hborder;
> uint8_t vborder;
> - uint8_t misc;
> + uint8_t misc; /* EDID_PT_* */
> } __attribute__((packed));
>
> struct detailed_data_string {
> --
> 2.21.0
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-30 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 8:00 [igt-dev] [PATCH i-g-t v2] lib/igt_edid: fix detailed pixel timing analog/digital Simon Ser
2019-04-26 8:41 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib/igt_edid: fix detailed pixel timing analog/digital (rev2) Patchwork
2019-05-03 4:48 ` Arkadiusz Hiler
2019-04-30 17:21 ` Ville Syrjälä [this message]
2019-05-06 10:51 ` [igt-dev] [PATCH i-g-t v2] lib/igt_edid: fix detailed pixel timing analog/digital Ser, Simon
2019-05-06 12:33 ` Ville Syrjälä
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=20190430172136.GH24299@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=simon.ser@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: 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