All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: daniel.vetter@ffwll.ch, alsa-devel@alsa-project.org,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: set proper N/CTS in modeset
Date: Wed, 23 Sep 2015 10:40:33 +0200	[thread overview]
Message-ID: <s5hlhbx8r5q.wl-tiwai@suse.de> (raw)
In-Reply-To: <87613av7n0.fsf@intel.com>

On Wed, 16 Sep 2015 15:03:15 +0200,
Jani Nikula wrote:
> 
> > diff --git a/include/drm/i915_component.h b/include/drm/i915_component.h
> > index e6d35d7..89dc7d6 100644
> > --- a/include/drm/i915_component.h
> > +++ b/include/drm/i915_component.h
> > @@ -24,8 +24,18 @@
> >  #ifndef _I915_COMPONENT_H_
> >  #define _I915_COMPONENT_H_
> >  
> > +/* MAX_PORT is the number of port
> > + * It must be sync with I915_MAX_PORTS defined i915_drv.h
> > + * 5 should be enough as only HSW, BDW, SKL need such fix.
> 
> You should probably add BUILD_BUG_ON(MAX_PORTS != I915_MAX_PORTS)
> somewhere near the loop above. Or at least change I915_MAX_PORTS to
> ARRAY_SIZE(acomp->aud_sample_rate) in the loop to not run over the array
> if MAX_PORTS gets out of sync.
> 
> With that addressed one way or another, this is
> 
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>

Libin, could you resubmit the patch with fixes Jani suggested?
Then I'm going to merge it to the existing topic/drm-sync-audio-rate
branch.


thanks,

Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-09-23  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  0:40 [PATCH] drm/i915: set proper N/CTS in modeset libin.yang
2015-09-16 13:03 ` Jani Nikula
2015-09-23  8:40   ` Takashi Iwai [this message]
2015-09-23 14:20     ` Yang, Libin
2015-09-24 13:18       ` Yang, Libin
  -- strict thread matches above, loose matches on Subject: below --
2015-09-10  7:29 libin.yang

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=s5hlhbx8r5q.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.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 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.