From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Samuel Ortiz <samuel.ortiz@intel.com>,
Dmitry Torokhov <dtor@mail.ru>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
alsa-devel@alsa-project.org,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: [PATCH v3 0/5] ASoC/MFD/Input: twl6040: Support for audio driven vibra
Date: Wed, 12 Oct 2011 11:57:52 +0300 [thread overview]
Message-ID: <1318409877-21681-1-git-send-email-peter.ujfalusi@ti.com> (raw)
Hello,
Changes since v2:
- Rebased on git://opensource.wolfsonmicro.com/linux-2.6-asoc, for-3.2 branch
- Acked-by lines added to patches.
Intro mail form v1:
The following series adds support for the soc driver to route audio (PCM
stream) to the vibra ports of the twl6040.
We have ALSA controls for the vibra source selection (PDM, or Input/FF).
The route can not be changed from Input/FF to PDM during ongoing effect coming
from Input/FF.
The Input/FF driver can not execute new effect, while the vibra source is
configured to be PDM.
TO get things working in legacy mode the omap-mcpdm, and twl6040 soc codec
driver's channel count needed to be fixed.
To minimize the need for reads through the I2C bus, the MFD driver will cache
the vibra control registers.
With this series we can route PCM audio to drive the twl6040 vibra output.
In order to that we need to play 5 channel audio, and place the vibra sample at
the 5th channel. This will change with ABE support (change == simplified).
The series has been created on top of:
git://opensource.wolfsonmicro.com/linux-2.6-asoc, for-3.2 branch
If there are no objections, it would be good if this series goes via audio.
Regards,
Peter
---
Peter Ujfalusi (5):
Input: twl6040: Simplify vibra regsiter definitions
MFD: twl6040: Cache the vibra control registers
MFD: twl6040: function to query the vibra status for clients
Input: twl6040-vibra: Check the selected path for vibra
ASoC: twl6040: Support for vibra output paths
drivers/input/misc/twl6040-vibra.c | 19 ++++++---
drivers/mfd/twl6040-core.c | 31 +++++++++++++--
include/linux/mfd/twl6040.h | 24 +++++------
sound/soc/codecs/twl6040.c | 72 ++++++++++++++++++++++++++++++++++++
4 files changed, 123 insertions(+), 23 deletions(-)
--
1.7.7
next reply other threads:[~2011-10-12 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 8:57 Peter Ujfalusi [this message]
2011-10-12 8:57 ` [PATCH v3 1/5] Input: twl6040: Simplify vibra regsiter definitions Peter Ujfalusi
2011-10-12 8:57 ` [PATCH v3 2/5] MFD: twl6040: Cache the vibra control registers Peter Ujfalusi
2011-10-12 8:57 ` [PATCH v3 3/5] MFD: twl6040: function to query the vibra status for clients Peter Ujfalusi
2011-10-12 8:57 ` [PATCH v3 4/5] Input: twl6040-vibra: Check the selected path for vibra Peter Ujfalusi
2011-10-12 8:57 ` [PATCH v3 5/5] ASoC: twl6040: Support for vibra output paths Peter Ujfalusi
2011-10-12 10:49 ` [PATCH v3 0/5] ASoC/MFD/Input: twl6040: Support for audio driven vibra 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=1318409877-21681-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dtor@mail.ru \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=samuel.ortiz@intel.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).