All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Dom Cobley <dom@raspberrypi.com>,
	Tim Gover <tim.gover@raspberrypi.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	David Airlie <airlied@linux.ie>,
	Werner Sembach <wse@tuxedocomputers.com>,
	dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Phil Elwell <phil@raspberrypi.com>
Subject: Re: [PATCH v6 0/7] drm/vc4: hdmi: Yet Another Approach to HDMI YUV output
Date: Thu, 24 Mar 2022 12:27:04 +0200	[thread overview]
Message-ID: <YjxHeDOeugXLETvS@intel.com> (raw)
In-Reply-To: <20220222164042.403112-1-maxime@cerno.tech>

On Tue, Feb 22, 2022 at 05:40:35PM +0100, Maxime Ripard wrote:
> Hi,
> 
> This is another attempt at supporting the HDMI YUV output in the vc4 HDMI
> driver.
> 
> This is a follow-up of
> https://lore.kernel.org/dri-devel/20210317154352.732095-1-maxime@cerno.tech/
> 
> And the discussions that occured recently on the mailing lists and IRC about
> this.
> 
> The series mentioned above had multiple issues, the main one being that it was
> a bit too much complicated for what we wanted to achieve. This series is taking
> a much simpler approach with an ad-hoc solution.
> 
> I think some parts of it could still be moved to KMS helpers (notably, the
> output format enum, and the helper to set the infoframe for it) and structures
> (the output format stored in drm_connector_state). This would also interact
> nicely with the work done here:
> 
> https://lore.kernel.org/dri-devel/20211118103814.524670-1-maxime@cerno.tech/
> 
> This can come as a second step though.
> 
> The other issues with the first attempt was that nothing was reported to
> userspace about the decision we made about the format, and that this decision
> was essentially policy, without any way for the userspace to influence it.
> 
> Those two points however are being worked on by Werner in a cross-driver
> effort:
> 
> https://lore.kernel.org/dri-devel/e452775c-5b95-bbfd-e818-f1480f556336@tuxedocomputers.com/
> 
> Since it's a KMS decision, I don't think we should hold off any driver as long
> as it's consistent with what the other drivers are doing.
> 
> Let me know what you think,

High level view looks fine to me. No clue about the low level hw bits.
Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> Maxime
> 
> ---
> 
> Changes from v5:
>   - Renamed pixel_rate to tmds_char_rate
>   - used do_div when necessary
>   - Used limited range YUV matrixes
>   - Rebased on current drm-misc-next
> 
> Changes from v4:
>   - Fix a clock calculation
>   - Rebased on latest drm-misc-next tag
> 
> Changes from v3:
>   - Rebased on latest next
>   - Fixed build error
> 
> Changes from v2:
>   - Rename the output format enum
>   - Split the edid_hdmi_dc_modes in two for RGB444 and YUV444
>   - Remove color_formats modifications from _parse_deep_color entirely
>   - Fixed comment formatting
>   - Fixed mode_valid that would always return true
>   - Fixed max_tmds_clock handling
> 
> Changes from v1:
>   - Fixed an EDID parsing error for YUV422
>   - Fixed the scrambling setup when using a bpc > 8
>   - Added some logging
>   - Fixed some build-bot warnings
>   - Fixed a number of HDMI specifications and EDID issues
>   - Try to max out the bpc every time
> 
> Maxime Ripard (7):
>   drm/vc4: hdmi: Rename pixel_rate variable
>   drm/vc4: hdmi: Move clock validation to its own function
>   drm/vc4: hdmi: Move clock calculation into its own function
>   drm/vc4: hdmi: Take the sink maximum TMDS clock into account
>   drm/vc4: hdmi: Take bpp into account for the scrambler
>   drm/vc4: hdmi: Always try to have the highest bpc
>   drm/vc4: hdmi: Support HDMI YUV output
> 
>  drivers/gpu/drm/vc4/vc4_hdmi.c      | 429 +++++++++++++++++++++++++---
>  drivers/gpu/drm/vc4/vc4_hdmi.h      |  23 +-
>  drivers/gpu/drm/vc4/vc4_hdmi_phy.c  |   2 +-
>  drivers/gpu/drm/vc4/vc4_hdmi_regs.h |   6 +
>  drivers/gpu/drm/vc4/vc4_regs.h      |  16 ++
>  5 files changed, 427 insertions(+), 49 deletions(-)
> 
> -- 
> 2.35.1
> 

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2022-03-24 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 16:40 [PATCH v6 0/7] drm/vc4: hdmi: Yet Another Approach to HDMI YUV output Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 1/7] drm/vc4: hdmi: Rename pixel_rate variable Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 2/7] drm/vc4: hdmi: Move clock validation to its own function Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 3/7] drm/vc4: hdmi: Move clock calculation into " Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 4/7] drm/vc4: hdmi: Take the sink maximum TMDS clock into account Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 5/7] drm/vc4: hdmi: Take bpp into account for the scrambler Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 6/7] drm/vc4: hdmi: Always try to have the highest bpc Maxime Ripard
2022-02-22 16:40 ` [PATCH v6 7/7] drm/vc4: hdmi: Support HDMI YUV output Maxime Ripard
2022-03-24 10:27 ` Ville Syrjälä [this message]
2022-03-24 12:48 ` [PATCH v6 0/7] drm/vc4: hdmi: Yet Another Approach to " Maxime Ripard

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=YjxHeDOeugXLETvS@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dom@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    --cc=phil@raspberrypi.com \
    --cc=tim.gover@raspberrypi.com \
    --cc=tzimmermann@suse.de \
    --cc=wse@tuxedocomputers.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 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.