From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: snd_soc_hw_bulk_write_raw: Use the codec's hw_write callback
Date: Wed, 11 May 2011 22:00:45 +0200 [thread overview]
Message-ID: <20110511200045.GD21150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1305140714-10953-1-git-send-email-lars@metafoo.de>
On Wed, May 11, 2011 at 12:05:14PM -0700, Lars-Peter Clausen wrote:
> Currently there are two places in the snd_soc_cache code where the function to
> write to the hardware is determined by looking at the control_type.
> One lookup is done when the cache is initialized the other is done in
> snd_soc_hw_bulk_write_raw. This requires, that when the spi or i2c write function
> is changed, that both places are updated.
> To avoid missing one of them use the codec's hw_write callback in
> snd_soc_hw_bulk_write_raw instead of looking at the control_type.
>
> Also this allows to use other bus types to do raw writes instead of limiting it
> to spi and i2c.
You're missing the bigger picture here where the raw bulk write doesn't
work at all at the minute as it doesn't include the register. Dimitris
said he was going to fix this, I suspect this will collide with that
more important fix.
Please do also bear in mind my previous feedback about fixing the line
lengths and general formatting in your commit logs. It's rather hard to
read the above.
next prev parent reply other threads:[~2011-05-11 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 17:25 [PATCH] ASoC: Reintroduce do_spi_write() Mark Brown
2011-05-11 19:05 ` [PATCH] ASoC: snd_soc_hw_bulk_write_raw: Use the codec's hw_write callback Lars-Peter Clausen
2011-05-11 20:00 ` Mark Brown [this message]
2011-05-12 8:42 ` [PATCH] ASoC: Reintroduce do_spi_write() Liam Girdwood
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=20110511200045.GD21150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=lrg@slimlogic.co.uk \
/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.