All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Zeng Zhaoming <zhaoming.zeng@freescale.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Dong Aisheng <b29396@freescale.com>,
	Zeng Zhaoming <b32542@freescale.com>
Subject: Re: [PATCH 0/3] make the sgtl5000-codec work
Date: Tue, 19 Jul 2011 11:04:04 +0200	[thread overview]
Message-ID: <20110719090404.GD1951@pengutronix.de> (raw)
In-Reply-To: <20110718191602.GA8576@ubuntu.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]

Hi,

>     pls check http://comments.gmane.org/gmane.linux.alsa.devel/83781
> 
>     I think Mark is right, sgtl5000 already declared its register_step is 2, soc_cache.c
>     should generate a dense cache layout instead of padding it by driver.

Thanks for the pointer. I can follow Mark's reasoning. In fact, I was
wondering why ASoC does not consider the step, but I assumed it was
intentional. With my holidays coming along, nothing I am going to
tackle in the next time, though ;)

>     But after check soc_cache.c, ASoC mix up index and register address to index cache,
>     and many places need to modify to correct it, so I think we should re-consider
>     if register_step != 1 is not a common case.

I think it should be properly fixed in ASoC. It should be carefully
done, but otherwise not be a major task IMO. Note that sgtl5000 will
need adaptions nonetheless. Which brings me back to the question: In
what setup did the driver work for you? Did you have regulators on that
board? I am still trying to understand the side-effects of what I am
seeing...

Mark: Will you pick up patches 1 and 2 nonetheless?

Thanks,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2011-07-19  9:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 15:53 [PATCH 0/3] make the sgtl5000-codec work Wolfram Sang
2011-07-18 15:53 ` [PATCH 1/3] ASoC: sgtl5000: refactor registering internal ldo Wolfram Sang
2011-07-19 15:20   ` Mark Brown
2011-07-18 15:53 ` [PATCH 2/3] ASoC: sgtl5000: guide user when regulator support is needed Wolfram Sang
2011-07-18 15:53 ` [PATCH 3/3] ASoC: sgtl5000: fix cache handling Wolfram Sang
2011-07-18 19:16 ` [PATCH 0/3] make the sgtl5000-codec work Zeng Zhaoming
2011-07-19  9:04   ` Wolfram Sang [this message]
2011-07-19 10:09     ` Liam Girdwood
2011-07-19 15:13     ` Mark Brown
2011-07-19 16:46       ` Wolfram Sang
2011-07-19 16:59         ` Mark Brown
2011-07-19  2:56 ` Dong Aisheng
2011-07-19  5:09 ` Shawn Guo
2011-07-19  5:32 ` Dong Aisheng
2011-07-19 15:09 ` Mark Brown
2011-07-19 16:52   ` Wolfram Sang

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=20110719090404.GD1951@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=b29396@freescale.com \
    --cc=b32542@freescale.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=zhaoming.zeng@freescale.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 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.