All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for YCBCR 4:2:0/4:4:4 output support for LSPCON (rev3)
Date: Tue, 27 Feb 2018 12:08:25 +0200	[thread overview]
Message-ID: <20180227100825.GZ5453@intel.com> (raw)
In-Reply-To: <20180207105759.6739.96217@emeril.freedesktop.org>

On Wed, Feb 07, 2018 at 10:57:59AM -0000, Patchwork wrote:
> == Series Details ==
> 
> Series: YCBCR 4:2:0/4:4:4 output support for LSPCON (rev3)
> URL   : https://patchwork.freedesktop.org/series/36068/
> State : warning
> 
> == Summary ==
> 
> Series 36068v3 YCBCR 4:2:0/4:4:4 output support for LSPCON
> https://patchwork.freedesktop.org/api/1.0/series/36068/revisions/3/mbox/
> 
> Test debugfs_test:
>         Subgroup read_all_entries:
>                 pass       -> DMESG-WARN (fi-elk-e7500) fdo#103989 +11
>                 pass       -> DMESG-WARN (fi-ilk-650)
>                 pass       -> DMESG-WARN (fi-snb-2600)
>                 pass       -> DMESG-WARN (fi-byt-j1900)
>                 pass       -> DMESG-WARN (fi-byt-n2820)
>                 pass       -> DMESG-WARN (fi-bsw-n3050)

Looks like all of these are due to missing readout in
i9xx/ilk_get_pipe_config().

>         Subgroup basic-s4-devices:
>                 pass       -> DMESG-WARN (fi-blb-e6850)
>                 pass       -> DMESG-WARN (fi-pnv-d510)
>                 pass       -> DMESG-WARN (fi-ilk-650)
>                 pass       -> DMESG-WARN (fi-snb-2520m)
>                 pass       -> DMESG-WARN (fi-snb-2600)
>                 pass       -> DMESG-WARN (fi-ivb-3520m)
>                 pass       -> DMESG-WARN (fi-ivb-3770)
>                 pass       -> DMESG-WARN (fi-byt-j1900)
>                 pass       -> DMESG-WARN (fi-byt-n2820)
>                 pass       -> DMESG-WARN (fi-hsw-4770)

The hsw case must be something a bit more subtle since you did add
something to hsw_get_pipe_config(). I can't immediately see what would
cause this. Probably best to fix the other platforms first and get
a new set of results with the extra noise removed, and then we can see
if you hit the same warn on the other platforms as you have on hsw.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-27 10:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 10:17 [PATCH v5 0/8] YCBCR 4:2:0/4:4:4 output support for LSPCON Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 1/8] drm/i915: Introduce CRTC output format Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 2/8] drm/i915: Add CRTC output format YCBCR 4:2:0 Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 3/8] drm/i915: Add CRTC output format YCBCR 4:4:4 Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 4/8] drm/i915: Check LSPCON vendor OUI Shashank Sharma
2018-02-07 11:19   ` Jani Nikula
2018-02-07 12:42     ` Sharma, Shashank
2018-02-07 10:17 ` [PATCH v5 5/8] drm/i915: Add AVI infoframe support for LSPCON Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 6/8] drm/i915: Write AVI infoframes for MCA LSPCON Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 7/8] drm/i915: Write AVI infoframes for Parade LSPCON Shashank Sharma
2018-02-07 10:17 ` [PATCH v5 8/8] drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON Shashank Sharma
2018-02-07 10:57 ` ✗ Fi.CI.BAT: warning for YCBCR 4:2:0/4:4:4 output support for LSPCON (rev3) Patchwork
2018-02-27 10:08   ` Ville Syrjälä [this message]
2018-03-20 15:31     ` 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=20180227100825.GZ5453@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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 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.