From: Jani Nikula <jani.nikula@linux.intel.com>
To: clinton.a.taylor@intel.com, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values
Date: Mon, 15 Oct 2018 14:24:34 +0300 [thread overview]
Message-ID: <87bm7vmozx.fsf@intel.com> (raw)
In-Reply-To: <1538778405-29103-1-git-send-email-clinton.a.taylor@intel.com>
On Fri, 05 Oct 2018, clinton.a.taylor@intel.com wrote:
> From: Clint Taylor <clinton.a.taylor@intel.com>
>
> HDMI 2.0 594Mhz modes were incorrectly selecting 25.200Mhz Automatic N
> value mode instead of HDMI specification values.
>
> Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
> ---
> drivers/gpu/drm/i915/intel_audio.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
> index 769f3f5..4b8f6f6 100644
> --- a/drivers/gpu/drm/i915/intel_audio.c
> +++ b/drivers/gpu/drm/i915/intel_audio.c
> @@ -144,6 +144,8 @@ struct dp_aud_n_m {
> /* HDMI N/CTS table */
> #define TMDS_297M 297000
> #define TMDS_296M 296703
> +#define TMDS_594M 594000
> +#define TMDS_593M 593407
> static const struct {
> int sample_rate;
> int clock;
> @@ -164,6 +166,20 @@ struct dp_aud_n_m {
> { 176400, TMDS_297M, 18816, 247500 },
> { 192000, TMDS_296M, 23296, 281250 },
> { 192000, TMDS_297M, 20480, 247500 },
> + { 44100, TMDS_593M, 8918, 937500 },
> + { 44100, TMDS_594M, 9408, 990000 },
> + { 48000, TMDS_593M, 5824, 562500 },
> + { 48000, TMDS_594M, 6144, 594000 },
> + { 32000, TMDS_593M, 5824, 843750 },
> + { 32000, TMDS_594M, 3072, 445500 },
> + { 88200, TMDS_593M, 17836, 937500 },
> + { 88200, TMDS_594M, 9408, 990000 },
The N here should be 18816. The rest looks good.
BR,
Jani.
> + { 96000, TMDS_593M, 11648, 562500 },
> + { 96000, TMDS_594M, 12288, 594000 },
> + { 176400, TMDS_593M, 35672, 937500 },
> + { 176400, TMDS_594M, 37632, 990000 },
> + { 192000, TMDS_593M, 23296, 562500 },
> + { 192000, TMDS_594M, 24576, 594000 },
> };
>
> /* get AUD_CONFIG_PIXEL_CLOCK_HDMI_* value for mode */
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-15 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 22:26 [PATCH] drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values clinton.a.taylor
2018-10-06 0:17 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-10-06 8:11 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-15 11:24 ` Jani Nikula [this message]
2018-10-15 11:31 ` [PATCH] " Jani Nikula
2018-10-25 18:56 ` Clint Taylor
2018-10-25 18:51 ` [PATCH 0/2] HDMI 2.0 clock recovery values clinton.a.taylor
2018-10-25 18:52 ` [PATCH v2 1/2] drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values clinton.a.taylor
2018-10-26 7:04 ` Jani Nikula
2018-10-25 18:52 ` [PATCH v2 2/2] drm/i915/hdmi: Reorder structure to match specification clinton.a.taylor
2018-10-26 10:23 ` Jani Nikula
2018-10-25 19:27 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values (rev2) Patchwork
2018-10-25 19:50 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-26 2:07 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-31 20:54 ` [PATCH v3] drm/i915/hdmi: Reorder structure to match specification clinton.a.taylor
2018-11-15 14:04 ` Jani Nikula
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=87bm7vmozx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=clinton.a.taylor@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