Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: intel-gfx@lists.freedesktop.org, alsa-devel@alsa-project.org,
	libin.yang@linux.intel.com
Subject: Re: DP audio API changes for identifying displays connected to a port
Date: Wed, 03 Aug 2016 15:47:32 +0200	[thread overview]
Message-ID: <s5h4m72t157.wl-tiwai@suse.de> (raw)
In-Reply-To: <1470190470-32326-1-git-send-email-dhinakaran.pandiyan@intel.com>

On Wed, 03 Aug 2016 04:14:29 +0200,
Dhinakaran Pandiyan wrote:
> 
> 
> An additional parameter has been added to the API's between i915 and audio
> drivers to identify display devices that can be connected to the same port.
> Currently only the port identity is being shared, but this is not
> sufficient as multiple displays can be driven from the same port
> (E.g. DP MST). This patch makes the API changes with dummy changes in the
> audio driver (Thanks Libin). Implementation to fully enable DP MST audio
> will follow later.

You should put this rather in the patch description, as it's a single
patch.


thanks,

Takashi


> 
> Dhinakaran Pandiyan(1):
> drm/i915/dp: DP audio API changes for MST
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-08-03 13:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  2:14 DP audio API changes for identifying displays connected to a port Dhinakaran Pandiyan
2016-08-03  2:14 ` [PATCH] drm/i915/dp: DP audio API changes for MST Dhinakaran Pandiyan
2016-08-03 13:53   ` Takashi Iwai
2016-08-03 18:52     ` Pandiyan, Dhinakaran
2016-08-03 19:08   ` Ville Syrjälä
2016-08-03 19:43     ` Pandiyan, Dhinakaran
2016-08-03 20:28       ` Ville Syrjälä
2016-08-03 21:42         ` Pandiyan, Dhinakaran
2016-08-04 12:49           ` Ville Syrjälä
2016-08-04 16:44             ` Pandiyan, Dhinakaran
2016-08-04 17:18     ` Jim Bride
2016-08-04 17:35       ` Ville Syrjälä
2016-08-04 17:55         ` Takashi Iwai
2016-08-04 20:48           ` Ville Syrjälä
2016-08-05  2:31             ` Yang, Libin
2016-08-05  7:46               ` Pandiyan, Dhinakaran
2016-08-05  8:51                 ` Ville Syrjälä
2016-08-05  2:35   ` Yang, Libin
2016-08-05  5:57     ` Pandiyan, Dhinakaran
2016-08-05  6:21       ` Yang, Libin
2016-08-05  6:41         ` Pandiyan, Dhinakaran
2016-08-05  6:43           ` Yang, Libin
2016-08-03  6:25 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-03 13:47 ` Takashi Iwai [this message]

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=s5h4m72t157.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=libin.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox