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 v5 2/6] drm/vc4: hdmi: Move clock calculation into its own function
Date: Thu, 3 Feb 2022 21:59:15 +0200 [thread overview]
Message-ID: <Yfw0EwaI9OqS6keP@intel.com> (raw)
In-Reply-To: <20220127141021.302482-3-maxime@cerno.tech>
On Thu, Jan 27, 2022 at 03:10:17PM +0100, Maxime Ripard wrote:
> The code to compute our clock rate for a given setup will be called in
> multiple places in the next patches, so let's create a separate function
> for it.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
> drivers/gpu/drm/vc4/vc4_hdmi.c | 49 +++++++++++++++++++++++-----------
> 1 file changed, 34 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/vc4/vc4_hdmi.c b/drivers/gpu/drm/vc4/vc4_hdmi.c
> index 105911644b02..a1fa37ad350d 100644
> --- a/drivers/gpu/drm/vc4/vc4_hdmi.c
> +++ b/drivers/gpu/drm/vc4/vc4_hdmi.c
> @@ -1274,6 +1274,35 @@ vc4_hdmi_encoder_clock_valid(const struct vc4_hdmi *vc4_hdmi,
> return MODE_OK;
> }
>
> +static unsigned long long
> +vc4_hdmi_encoder_compute_mode_clock(const struct drm_display_mode *mode,
> + unsigned int bpc)
> +{
> + unsigned long long clock = mode->clock * 1000;
> +
> + if (mode->flags & DRM_MODE_FLAG_DBLCLK)
> + clock = clock * 2;
> +
> + return clock * bpc / 8;
div_u64()/etc.?
> +}
> +
> +static int
> +vc4_hdmi_encoder_compute_clock(const struct vc4_hdmi *vc4_hdmi,
> + struct vc4_hdmi_connector_state *vc4_state,
> + const struct drm_display_mode *mode,
> + unsigned int bpc)
> +{
> + unsigned long long clock;
> +
> + clock = vc4_hdmi_encoder_compute_mode_clock(mode, bpc);
> + if (vc4_hdmi_encoder_clock_valid(vc4_hdmi, clock) != MODE_OK)
> + return -EINVAL;
> +
> + vc4_state->pixel_rate = clock;
This thing seems a bit confused between pixels vs. TMDS characters.
Either that or some/all of the pixel_clock/rate things are just
misnamed?
> +
> + return 0;
> +}
> +
> #define WIFI_2_4GHz_CH1_MIN_FREQ 2400000000ULL
> #define WIFI_2_4GHz_CH1_MAX_FREQ 2422000000ULL
>
> @@ -1286,6 +1315,7 @@ static int vc4_hdmi_encoder_atomic_check(struct drm_encoder *encoder,
> struct vc4_hdmi *vc4_hdmi = encoder_to_vc4_hdmi(encoder);
> unsigned long long pixel_rate = mode->clock * 1000;
> unsigned long long tmds_rate;
> + int ret;
>
> if (vc4_hdmi->variant->unsupported_odd_h_timings &&
> ((mode->hdisplay % 2) || (mode->hsync_start % 2) ||
> @@ -1306,21 +1336,10 @@ static int vc4_hdmi_encoder_atomic_check(struct drm_encoder *encoder,
> pixel_rate = mode->clock * 1000;
> }
>
> - if (conn_state->max_bpc == 12) {
> - pixel_rate = pixel_rate * 150;
> - do_div(pixel_rate, 100);
> - } else if (conn_state->max_bpc == 10) {
> - pixel_rate = pixel_rate * 125;
> - do_div(pixel_rate, 100);
> - }
> -
> - if (mode->flags & DRM_MODE_FLAG_DBLCLK)
> - pixel_rate = pixel_rate * 2;
> -
> - if (vc4_hdmi_encoder_clock_valid(vc4_hdmi, pixel_rate) != MODE_OK)
> - return -EINVAL;
> -
> - vc4_state->pixel_rate = pixel_rate;
> + ret = vc4_hdmi_encoder_compute_clock(vc4_hdmi, vc4_state, mode,
> + conn_state->max_bpc);
> + if (ret)
> + return ret;
>
> return 0;
> }
> --
> 2.34.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-02-03 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 14:10 [PATCH v5 0/6] drm/vc4: hdmi: Yet Another Approach to HDMI YUV output Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 1/6] drm/vc4: hdmi: Move clock validation to its own function Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 2/6] drm/vc4: hdmi: Move clock calculation into " Maxime Ripard
2022-02-03 19:59 ` Ville Syrjälä [this message]
2022-02-10 9:00 ` Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 3/6] drm/vc4: hdmi: Take the sink maximum TMDS clock into account Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 4/6] drm/vc4: hdmi: Take bpp into account for the scrambler Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 5/6] drm/vc4: hdmi: Always try to have the highest bpc Maxime Ripard
2022-01-27 14:10 ` [PATCH v5 6/6] drm/vc4: hdmi: Support HDMI YUV output Maxime Ripard
2022-02-03 20:07 ` Ville Syrjälä
2022-02-10 10:03 ` Maxime Ripard
2022-02-10 10:17 ` 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=Yfw0EwaI9OqS6keP@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox