From: Xing Zheng <zhengxing@rock-chips.com>
To: linux-rockchip@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org,
Mengdong Lin <mengdong.lin@linux.intel.com>,
heiko@sntech.de, Liam Girdwood <lgirdwood@gmail.com>,
dianders@chromium.org, Xing Zheng <zhengxing@rock-chips.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Takashi Iwai <tiwai@suse.com>,
sugar.zhang@rock-chips.com, jay.xu@rock-chips.com,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Jyri Sarha <jsarha@ti.com>, Rob Herring <robh+dt@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
linux-kernel@vger.kernel.org, Adam.Thomson@diasemi.com,
broonie@kernel.org, Kumar Gala <galak@codeaurora.org>,
Jun Nie <jun.nie@linaro.org>
Subject: [PATCH v2 0/3] Add support simple-card parse jack detection via external codec
Date: Mon, 18 Apr 2016 19:20:00 +0800 [thread overview]
Message-ID: <1460978403-4754-1-git-send-email-zhengxing@rock-chips.com> (raw)
Hi,
In most cases, many codecs already supports jack detection,
previouslly, we need to create a customized machine driver every time.
In my opinion, the codec fill the detect_jack explicitly and tell
sound framework it supports the jack detection, the simple-card is
able to parse the dts file and call the export function to initialize
the jace detection via the codec.
I think that it will bring better flexibility.
Thanks.
Changes in v1:
- clean up the commit message and notes
Xing Zheng (3):
ASoC: jack: Add an export of a function that calls the codec jack
detection
ASoC: simple-card: Add support call the codec jack detection after
parse dts
ASoC: da7219: Add detect_jack callback in the snd_soc_codec_driver
.../devicetree/bindings/sound/simple-card.txt | 17 +++
include/sound/soc.h | 7 ++
sound/soc/codecs/da7219.c | 2 +
sound/soc/generic/simple-card.c | 126 +++++++++++++++++++-
sound/soc/soc-jack.c | 17 +++
5 files changed, 166 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-04-18 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 11:20 Xing Zheng [this message]
2016-04-18 11:20 ` [PATCH v2 2/3] ASoC: simple-card: Add support call the codec jack detection after parse dts Xing Zheng
[not found] ` <1460978403-4754-1-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-18 11:20 ` [PATCH v2 1/3] ASoC: jack: Add an export of a function that calls the codec jack detection Xing Zheng
2016-04-18 11:20 ` [PATCH v2 3/3] ASoC: da7219: Add detect_jack callback in the snd_soc_codec_driver Xing Zheng
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=1460978403-4754-1-git-send-email-zhengxing@rock-chips.com \
--to=zhengxing@rock-chips.com \
--cc=Adam.Thomson@diasemi.com \
--cc=aaro.koskinen@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jay.xu@rock-chips.com \
--cc=jsarha@ti.com \
--cc=jun.nie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mengdong.lin@linux.intel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sugar.zhang@rock-chips.com \
--cc=support.opensource@diasemi.com \
--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).