intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Quanxian Wang <quanxian.wang@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Defined NM doesn't work on KBL and uses automatic N/M.
Date: Fri, 26 May 2017 11:31:00 +0300	[thread overview]
Message-ID: <87zie0m33v.fsf@intel.com> (raw)
In-Reply-To: <1495778837-6722-1-git-send-email-quanxian.wang@intel.com>

On Fri, 26 May 2017, Quanxian Wang <quanxian.wang@intel.com> wrote:
> According to the bspec, when set N/M, should disable
> and enable transcoder which attaching DP audio. However
> with that implementation will affect performance more.
>
> But with current implementation, KBL could not work with defined N/M.
> By default, KBL will use automatic N/M.
>
> Signed-off-by: Quanxian Wang <quanxian.wang@intel.com>
> Reviewed-by: Libin Yang <libin.yang@intel.com>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

I have *NOT* reviewed this patch. Even if it's based on my suggestion in
[1], it does not automatically signify review.

The patch subject should start with "drm/i915/audio:".

The DP spec always expresses the values as M/N, more specifically
Maud/Naud, so it's confusing to see them expressed as N/M.

I still have trouble understanding the commit message. I am wondering if
something was fixed in Kabylake and beyond, since according to
6014ac122ed0 ("drm/i915/audio: set proper N/M in modeset") we need this
for certain modes. In particular, should the condition check for KBL ||
gen >= 10?

BR,
Jani.


[1] http://mid.mail-archive.com/87pogs1lz7.fsf@intel.com



> ---
>  drivers/gpu/drm/i915/intel_audio.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_audio.c b/drivers/gpu/drm/i915/intel_audio.c
> index d805b6e..ba4994e 100644
> --- a/drivers/gpu/drm/i915/intel_audio.c
> +++ b/drivers/gpu/drm/i915/intel_audio.c
> @@ -289,6 +289,10 @@ hsw_dp_audio_config_update(struct intel_crtc *intel_crtc, enum port port,
>  	enum pipe pipe = intel_crtc->pipe;
>  	u32 tmp;
>  
> +	/* It doesn't work on KBL and uses automatic N/M. */
> +	if (IS_KABYLAKE(dev_priv))
> +		nm = NULL;
> +
>  	if (nm)
>  		DRM_DEBUG_KMS("using Maud %u, Naud %u\n", nm->m, nm->n);
>  	else

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-05-26  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  6:07 [PATCH] Defined NM doesn't work on KBL and uses automatic N/M Quanxian Wang
2017-05-26  6:27 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-26  8:31 ` Jani Nikula [this message]
2017-05-26  9:52   ` [PATCH] " Wang, Quanxian
2017-05-26 11:00     ` Jani Nikula
2017-05-26 21:36       ` Wang, Quanxian
2017-05-29  8:29         ` Jani Nikula
2017-05-31  3:20           ` Wang, Quanxian
2017-12-08  0:41             ` Wang, Quanxian

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=87zie0m33v.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=quanxian.wang@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;
as well as URLs for NNTP newsgroup(s).