From: Arun Shamanna Lakshmi <aruns@nvidia.com>
To: <broonie@kernel.org>, <lgirdwood@gmail.com>
Cc: <perex@perex.cz>, <tiwai@suse.de>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>,
Arun Shamanna Lakshmi <aruns@nvidia.com>
Subject: [PATCH] Change the prototype of soc_widget_read
Date: Tue, 14 Jan 2014 15:31:53 -0800 [thread overview]
Message-ID: <1389742314-20125-1-git-send-email-aruns@nvidia.com> (raw)
soc_widget_read API returns the register data and it is possible
that a register can contain 0xffffffff at any point of time.
In such cases snd_soc_widget_write is not called after the read
operation inside snd_soc_update_bits_locked API. Thus, change
the prototype of soc_widget_read to return only the error code
and pass the register data through the pointer argument.
Arun Shamanna Lakshmi (1):
ASoC: dapm: Change prototype of soc_widget_read
sound/soc/soc-dapm.c | 26 +++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-01-14 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 23:31 Arun Shamanna Lakshmi [this message]
2014-01-14 23:31 ` [PATCH] ASoC: dapm: Change " Arun Shamanna Lakshmi
2014-01-15 11:44 ` 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=1389742314-20125-1-git-send-email-aruns@nvidia.com \
--to=aruns@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®