linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dannym@scratchpost.org (Danny Milosavljevic)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v9 2/2] Add mixer controls: Line-In, FM-In, Mic 2, Capture Source, Differential Line-In.
Date: Wed, 31 Aug 2016 09:49:59 +0200	[thread overview]
Message-ID: <20160831094959.2e5e6ae7@scratchpost.org> (raw)
In-Reply-To: <CAGb2v67YGiZEzBezub5HcEBZ5689uF1yQYj2xJkbVdHyEpOm5Q@mail.gmail.com>

Hi Chen-Yu,
 
> My apologies. I didn't notice that VMIC was already in the driver.
> In that your original patch did everything right.

Don't worry about it :)

But I have a question:

If I replace DAPM_INPUT by DAPM_MIC it wants a callback that is supposed to
fiddle with the bias. 
Do I provide one?
If so, will it conflict with the supply?

Or do I leave it as DAPM_INPUT ?

  reply	other threads:[~2016-08-31  7:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  5:44 [PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In Danny Milosavljevic
2016-08-30  5:44 ` [PATCH v9 1/2] ASoC: sun4i-codec: Distinguish sun4i from sun7i Danny Milosavljevic
2016-08-31  3:22   ` Chen-Yu Tsai
2016-08-31 17:46   ` Maxime Ripard
2016-08-31 20:14     ` [linux-sunxi] " Danny Milosavljevic
2016-09-01 16:45       ` Maxime Ripard
2016-08-30  5:44 ` [PATCH v9 2/2] Add mixer controls: Line-In, FM-In, Mic 2, Capture Source, Differential Line-In Danny Milosavljevic
2016-08-31  6:24   ` Chen-Yu Tsai
2016-08-31  7:17     ` Danny Milosavljevic
2016-08-31  7:46       ` Chen-Yu Tsai
2016-08-31  7:40     ` [linux-sunxi] " Danny Milosavljevic
2016-08-31  7:43       ` Chen-Yu Tsai
2016-08-31  7:49         ` Danny Milosavljevic [this message]
2016-08-31  7:55           ` Chen-Yu Tsai
2016-09-01 10:56     ` Danny Milosavljevic
2016-09-01 13:25       ` [linux-sunxi] " Chen-Yu Tsai

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=20160831094959.2e5e6ae7@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=linux-arm-kernel@lists.infradead.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).