From: Danny Milosavljevic <dannym-bxPqe3T81XXwRsdMLXbzog@public.gmane.org>
To: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
Jaroslav Kysela <perex-/Fr2/VpizcU@public.gmane.org>,
Takashi Iwai <tiwai-IBi9RG/b67k@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: [PATCH v8 0/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs
Date: Mon, 21 Dec 2015 12:31:48 +0100 [thread overview]
Message-ID: <20151221123148.1ab6480b@dayas> (raw)
Hi,
this is the eighth version of the patch set that adds inputs to sun4i-codec.
Changes compared to v7 are:
- fix the routes for line and mic capturing.
The patches are on top of the branch "sunxi-next" in
<git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git>.
Regards,
Danny
---
Danny Milosavljevic (2):
sun4i-codec: Add FM, Line and Mic inputs
sun4i-codec: make it possible to use different codec_widgets for A10 and A20.
b/sound/soc/sunxi/sun4i-codec.c | 230 +++++++++++++++++++++++++++++++++++++---
1 file changed, 215 insertions(+), 15 deletions(-)
next reply other threads:[~2015-12-21 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 11:31 Danny Milosavljevic [this message]
2015-12-21 11:33 ` [PATCH v8 1/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs Danny Milosavljevic
2015-12-27 17:34 ` Maxime Ripard
2015-12-21 11:34 ` [PATCH v8 2/2] " Danny Milosavljevic
2015-12-27 18:21 ` Maxime Ripard
2015-12-28 3:06 ` Danny Milosavljevic
2015-12-31 22:19 ` Mark Brown
2016-01-06 22:09 ` Maxime Ripard
2016-01-09 15:48 ` Danny Milosavljevic
2016-03-12 7:52 ` Danny Milosavljevic
[not found] ` <20160312085222.226d89bf-bxPqe3T81XXwRsdMLXbzog@public.gmane.org>
2016-03-12 8:31 ` Code Kipper
2016-03-14 10:49 ` Maxime Ripard
2016-03-15 10:58 ` Mark Brown
[not found] ` <20160315105802.GN2566-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-19 16:13 ` Danny Milosavljevic
[not found] ` <20160319171336.6e16eb5a-bxPqe3T81XXwRsdMLXbzog@public.gmane.org>
2016-03-21 14:24 ` Mark Brown
2016-03-21 17:54 ` Maxime Ripard
2016-04-21 8:55 ` Danny Milosavljevic
2016-03-19 16:51 ` Danny Milosavljevic
[not found] ` <20160319175124.6bfe3617-bxPqe3T81XXwRsdMLXbzog@public.gmane.org>
2016-03-21 18:06 ` Maxime Ripard
2016-03-21 18:19 ` [linux-sunxi] " Mark Brown
2016-03-22 12:20 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2015-12-21 11:30 [PATCH v8 0/2] " Danny Milosavljevic
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=20151221123148.1ab6480b@dayas \
--to=dannym-bxpqe3t81xxwrsdmlxbzog@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=perex-/Fr2/VpizcU@public.gmane.org \
--cc=tiwai-IBi9RG/b67k@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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).