From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Marc Reilly <marc@cpdesign.com.au>,
u.kleine-koenig@pengutronix.de, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, linaro-kernel@lists.linaro.org,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 2/3] mfd: mc13xxx: Move SPI erratum workaround into SPI I/O function
Date: Thu, 19 Sep 2013 10:13:18 +0100 [thread overview]
Message-ID: <20130919091318.GA22389@lee--X1> (raw)
In-Reply-To: <1379527587-14567-2-git-send-email-broonie@kernel.org>
On Wed, 18 Sep 2013, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> Move the workaround for double sending AUDIO_CODEC and AUDIO_DAC writes
> into the SPI core, aiding refactoring to eliminate the ASoC custom I/O
> functions and avoiding the extra writes for I2C.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
> drivers/mfd/mc13xxx-spi.c | 5 +++++
> include/linux/mfd/mc13xxx.h | 7 +++++++
> sound/soc/codecs/mc13783.c | 4 ----
> 3 files changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mfd/mc13xxx-spi.c b/drivers/mfd/mc13xxx-spi.c
> index 77189da..363c359 100644
> --- a/drivers/mfd/mc13xxx-spi.c
> +++ b/drivers/mfd/mc13xxx-spi.c
> @@ -94,10 +94,15 @@ static int mc13xxx_spi_write(void *context, const void *data, size_t count)
> {
> struct device *dev = context;
> struct spi_device *spi = to_spi_device(dev);
> + char *reg = data;
I think this requires a cast.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-09-19 9:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 18:06 [PATCH 1/3] mfd: mc13xxx: Don't require lock for simple register I/O Mark Brown
2013-09-18 18:06 ` Mark Brown
2013-09-18 18:06 ` [PATCH 2/3] mfd: mc13xxx: Move SPI erratum workaround into SPI I/O function Mark Brown
2013-09-18 18:06 ` Mark Brown
2013-09-19 9:13 ` Lee Jones [this message]
2013-09-19 9:56 ` Mark Brown
2013-09-19 9:56 ` Mark Brown
2013-09-19 10:04 ` Lee Jones
2013-09-19 11:41 ` Mark Brown
2013-09-19 11:49 ` Lee Jones
2013-09-19 12:09 ` Mark Brown
2013-09-19 12:09 ` Mark Brown
2013-09-18 18:06 ` [PATCH 3/3] ASoC: mc13783: Use regmap directly from ASoC Mark Brown
2013-09-18 18:06 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2013-09-23 18:14 [PATCH 1/3] mfd: mc13xxx: Don't require lock for simple register I/O Mark Brown
2013-09-23 18:14 ` [PATCH 2/3] mfd: mc13xxx: Move SPI erratum workaround into SPI I/O function Mark Brown
2013-09-23 18:14 ` Mark Brown
2013-09-25 11:19 ` Lee Jones
2013-09-25 11:31 ` Mark Brown
2013-09-25 11:31 ` Mark Brown
2013-09-25 11:46 ` Lee Jones
2013-09-25 11:55 ` Lee Jones
2013-09-25 11:55 ` Lee Jones
2013-09-25 12:35 ` Mark Brown
2013-09-25 12:35 ` Mark Brown
2013-09-25 12:51 ` Lee Jones
2013-09-25 12:51 ` Lee Jones
2013-09-25 12:55 ` Mark Brown
2013-09-25 12:55 ` Mark Brown
2013-09-25 13:05 ` Lee Jones
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=20130919091318.GA22389@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@cpdesign.com.au \
--cc=sameo@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.