From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Heiko Stübner" <heiko@sntech.de>,
zhengxing <zhengxing@rock-chips.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Takashi Iwai" <tiwai@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Xing Zheng" <acgzxing@gmail.com>,
"Douglas Anderson" <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
"Dylan Reid" <dgreid@chromium.org>,
"Sonny Rao" <sonnyrao@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] ASoC: rockchip: add rockchip machine driver
Date: Tue, 19 May 2015 12:16:02 +0100 [thread overview]
Message-ID: <20150519111602.GG2761@sirena.org.uk> (raw)
In-Reply-To: <555659DB.9010204@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 1305 bytes --]
On Fri, May 15, 2015 at 10:40:59PM +0200, Lars-Peter Clausen wrote:
> I think the proper way to support this is come up with the concept of jack
> detection providers and consumers. A component can register a jack detection
> provider just like it can register a DAI. And then in the board driver you'd
> just link the jack detection logic to the jack using the usual approach,
> which is also used for DAIs (e.g. of node or device name). The core would
> then take care of calling a enable callback or whatever is required to setup
> the jack detection logic in the driver.
Yes, nobody has really cared about it since we started pushing things
out of the card init into the device level. We would also need to add a
way to force microphone biases on for devices where that's not a part of
the jack detection IP.
> This would also nicely solve the issue with the GPIO jack detectors, where
> we currently can't really handle -EPROBE_DEFER. The GPIO would be requested
> by a jack detection provider which can request them before the card is
> registered rather than having to do the requesting in the card's init
> callback.
Cards should be able to do their requesting in their probe function
prior to registering with the core even without anything else, though
that needs a bit or refactoring too.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-19 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 9:26 [PATCH 0/4] ASoC: rockchip: add rockchip machine driver Xing Zheng
2015-05-12 9:26 ` [PATCH 1/4] " Xing Zheng
2015-05-12 19:22 ` Mark Brown
2015-05-13 13:23 ` zhengxing
2015-05-13 16:42 ` Mark Brown
2015-05-13 17:21 ` Dylan Reid
2015-05-13 23:11 ` Dylan Reid
2015-05-14 2:22 ` zhengxing
2015-05-15 20:40 ` [alsa-devel] " Lars-Peter Clausen
2015-05-19 11:16 ` Mark Brown [this message]
2015-05-19 16:37 ` Dylan Reid
2015-05-21 11:10 ` Mark Brown
2015-05-12 9:26 ` [PATCH 2/4] ASoC: rockchip: add rockchip machine driver for max98090 Xing Zheng
2015-05-12 19:26 ` Mark Brown
2015-05-13 13:23 ` zhengxing
2015-05-13 16:47 ` Mark Brown
2015-05-12 9:26 ` [PATCH 3/4] ASoC: rockchip: add rockchip machine driver for rt5650/rt5645 Xing Zheng
2015-05-12 19:30 ` 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=20150519111602.GG2761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acgzxing@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=sonnyrao@chromium.org \
--cc=tiwai@suse.de \
--cc=zhengxing@rock-chips.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