From: Daniel Vetter <daniel@ffwll.ch>
To: Takashi Iwai <tiwai@suse.de>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] [PATCH v4 0/3] support DP MST audio
Date: Wed, 11 Jan 2017 08:39:13 +0100 [thread overview]
Message-ID: <CAKMK7uGpunR40JVavih0nqW9FWHZ+53fOu0vcEzJLHyKXgHo8Q@mail.gmail.com> (raw)
In-Reply-To: <s5hvatnl2od.wl-tiwai@suse.de>
On Tue, Jan 10, 2017 at 9:49 AM, Takashi Iwai <tiwai@suse.de> wrote:
> On Tue, 10 Jan 2017 09:45:31 +0100,
>> >-----Original Message-----
>> >From: Takashi Iwai [mailto:tiwai@suse.de]
>> >Sent: Tuesday, January 10, 2017 4:19 PM
>> >To: Yang, Libin <libin.yang@intel.com>
>> >Cc: Daniel Vetter <daniel@ffwll.ch>; intel-gfx <intel-gfx@lists.freedesktop.org>;
>> >Nikula, Jani <jani.nikula@linux.intel.com>; alsa-devel@alsa-project.org; Lin,
>> >Mengdong <mengdong.lin@intel.com>
>> >Subject: Re: [alsa-devel] [PATCH v4 0/3] support DP MST audio
>> >
>> >On Mon, 09 Jan 2017 07:22:55 +0100,
>> >Yang, Libin wrote:
>> >>
>> >> Hi Takashi,
>> >>
>> >> It seems the patches for DP MST in gfx is not merged into Linus branch.
>> >>
>> >> Do we have plan to merge gfx branch manually and review the patches for
>> >audio? Or we will wait the DP MST patches for i915 merged into Linus branch?
>> >
>> >Sorry, this was delayed due to the vacation.
>> >Now I applied these three patches to topic/hda-dp-mst branch based on 4.10-
>> >rc2, and it was merged to for-next branch.
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git topic/hda-dp-
>> >mst
>>
>> Thanks. These audio patches are based on the i915 dp mst patches. Without
>> I915 driver patches support, it will make errors.
>
> Ah yeah, I forgot it. So I removed it from for-next branch, but
> topic/hda-dp-mst branch is kept so that it can be merged to i915
> tree.
>
> Let me know if there is any i915 branch I can pull into sound tree.
Aw, I didn't know that the depency goes this way round, the dp mst
patches (I'm not even sure which ones they are) on the i915 are just
on the general pile. So not anywhere near a place where I can make a
topic branch.
I guess what needs to be done now is a cherry-picked list of just the
patches we need, on top of -rc3, that I can then pull into
drm-intel.git plus send a pull request for that to Takashi. That means
the patches are twice in drm-intel.git, but if we cherry-pick
reference them correctly then that should be all ok and can't really
be helped.
Or we just delay the audio side for 4.12, dp mst audio support is 4
years late anyway, so one more release won'thurt that much ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-11 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:48 [PATCH v4 0/3] support DP MST audio libin.yang
2016-12-06 2:48 ` [PATCH v4 1/3] ALSA: hda - add DP mst verb support libin.yang
2016-12-06 2:48 ` [PATCH v4 2/3] ALSA: hda - add DP MST audio support libin.yang
2016-12-06 2:48 ` [PATCH v4 3/3] ALSA: Documentation about HDA DP MST pin init and connection libin.yang
2016-12-06 2:58 ` [PATCH v4 0/3] support DP MST audio Yang, Libin
2016-12-06 7:20 ` Takashi Iwai
2016-12-06 7:51 ` [alsa-devel] " Daniel Vetter
2016-12-06 8:11 ` Takashi Iwai
2017-01-09 6:22 ` Yang, Libin
2017-01-10 8:19 ` Takashi Iwai
2017-01-10 8:45 ` Yang, Libin
2017-01-10 8:49 ` Takashi Iwai
2017-01-11 7:39 ` Daniel Vetter [this message]
2017-01-11 8:00 ` Takashi Iwai
2017-01-11 8:35 ` Daniel Vetter
2017-01-11 8:44 ` Yang, Libin
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=CAKMK7uGpunR40JVavih0nqW9FWHZ+53fOu0vcEzJLHyKXgHo8Q@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=alsa-devel@alsa-project.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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).