From: Chen-Yu Tsai <wens@csie.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Chen-Yu Tsai <wens@csie.org>,
alsa-devel@alsa-project.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] sun4i-codec: add inputs
Date: Fri, 11 Dec 2015 10:45:37 +0800 [thread overview]
Message-ID: <CAGb2v643+bbOM-zgPeQrypyJg13r4m6h=1qAP-Zd5_CVB07BWg@mail.gmail.com> (raw)
In-Reply-To: <20151210215227.6453acc8@dayas>
On Fri, Dec 11, 2015 at 4:52 AM, Danny Milosavljevic
<dannym@scratchpost.org> wrote:
> Hi Maxime,
>
> On Thu, 10 Dec 2015 18:54:20 +0100
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>> > + SOC_DAPM_SINGLE("Mic1-In Playback Switch", SUN4I_CODEC_DAC_ACTL,
>> > + SUN4I_CODEC_DAC_ACTL_MIC1RS, 1, 0),
>> > + SOC_DAPM_SINGLE("Mic2-In Playback Switch", SUN4I_CODEC_DAC_ACTL,
>> > + SUN4I_CODEC_DAC_ACTL_MIC2RS, 1, 0),
>> > };
>>
>> Do we need the -In part of FM, Mic1 and Mic2?
>
> For consistency to what's in linux-sunxi.git, I will remove the "-In" from
> the Mic names in v7.
>
> For FM, do we? I don't know. Are there ALSA devices which output to FM?
>
>> Mic1 is already defined a few lines above.
>> And you have the Mixers routes a bit above too.
>
> Aha, Mic1 is there in <https://github.com/linux-sunxi/linux-sunxi.git>
> branch "sunxi-next".
> In <git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git>
> branch "sunxi/for-next", it's not there.
> This patch is for the latter.
linux-sunxi/sunxi-next is a branch we maintain that has "most" new features
and patches aimed at the next release. It is not an official kernel branch,
nor is it always up to date (though we try to merge new things in).
mripard/linux sunxi/for-next is Maxime's sunxi branches, which is mostly
clock and dts patches.
You should always base your patches on the "next" branch of the maintainer
that will take your patches. In this case, ASoC:
https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/log/?h=for-next
There's also a sunxi topic branch:
https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/log/?h=topic/sunxi
Or you can just base them off linux-next.
Regards
ChenYu
>
> I'm currently rebasing on the former, but it will take some time.
> The differences between these driver versions are:
> - Mic1 Preamplifier is registered as PGA instead of switch in the former.
> - Mic1 is already an input in the former.
> - VMIC is handled in the former.
> - ADC Capturing support exists in the former.
> That's it.
>
> I'll retest a patch based on the former...
>
>> [global mutation]
>> We'll need to fix that, see the other discussion.
>
> Yeah, I think I found a nicer way to do it in v6.
>
> Thanks,
> Danny
prev parent reply other threads:[~2015-12-11 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 3:20 [PATCH v5] sun4i-codec: add inputs Danny Milosavljevic
2015-12-10 17:54 ` Maxime Ripard
2015-12-10 20:52 ` Danny Milosavljevic
2015-12-11 2:45 ` Chen-Yu Tsai [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='CAGb2v643+bbOM-zgPeQrypyJg13r4m6h=1qAP-Zd5_CVB07BWg@mail.gmail.com' \
--to=wens@csie.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dannym@scratchpost.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).