From: John Stultz <john.stultz@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
lkml <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Rob Herring <robh+dt@kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id
Date: Mon, 26 Jun 2017 09:31:34 -0700 [thread overview]
Message-ID: <CALAqxLUqt-pyRimWjJL6QYnvX17wSjbkdy_Vsynbhrf8bfgfnQ@mail.gmail.com> (raw)
In-Reply-To: <20170614000543.l636aslxdt5xd32f@sirena.org.uk>
On Tue, Jun 13, 2017 at 5:05 PM, Mark Brown <broonie@kernel.org> wrote:
> On Tue, Jun 13, 2017 at 02:59:49PM -0700, John Stultz wrote:
>> ALSA SoC needs to know connected DAI ID for probing. Using
>> the new audio-card-graph approach, ports/endpoints are used
>> to describe how the links are connected. Unfortunately, since
>
> Unless someone objects in the next week or so I intend to apply this.
Hey Mark,
Just wanted to check on this to make sure it didn't slip by. I've
not seen it show up in -next yet.
thanks
-john
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-26 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 21:59 [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id John Stultz
2017-06-13 22:01 ` John Stultz
2017-06-14 0:05 ` Mark Brown
2017-06-26 16:31 ` John Stultz [this message]
2017-06-28 18:50 ` Mark Brown
2017-06-30 11:59 ` Applied "drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id" to the asoc tree Mark Brown
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=CALAqxLUqt-pyRimWjJL6QYnvX17wSjbkdy_Vsynbhrf8bfgfnQ@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).