From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, matt@genesi-usa.com,
eric.nelson@boundarydevices.com, troy.kisky@boundarydevices.com,
zengzm.kernel@gmail.com
Subject: Re: [RFC] ASoC: sgtl5000: Remove cache support
Date: Sun, 5 May 2013 11:15:15 +0100 [thread overview]
Message-ID: <20130505101515.GT4945@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5BG-3SKZF_ZrQ=C51nLvKYSNJEgy-KavzBXJcb=fCk=iA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
On Sat, May 04, 2013 at 05:25:45PM -0300, Fabio Estevam wrote:
> I see this commit from Freescale kernel that workarounds exactly the same issue:
> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/commit/sound/soc/codecs/sgtl5000.c?h=imx_3.0.35_1.1.0&id=2f7d47e760725d33f6b2eb01024b800d64ff8944
> It seems that caching is broking with this codec.
This is nonsensical. Clearly there's something about the use of the
cache that is interacting poorly with the device but we've no idea what
it is. Simply having a copy of the register map in the host memory is
not going to do anything to the device, there must be some other issue
at work.
> If this is true, should we go with the proposal of this RFC patch?
We should understand what the issue is. Looking at the commit above
it's not removing the cache at all, it's both attempting to work around
an issue with the cache not handling the register step size properly
(this looks like it's just a bug in the current driver) and reordering
some of the startup around the regulator (the comment says it's open
coding cache_bypass but it's also moving blocks of code around).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-05-05 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367610549-25542-1-git-send-email-festevam@gmail.com>
[not found] ` <20130503223613.GR4945@sirena.org.uk>
2013-05-04 18:47 ` [RFC] ASoC: sgtl5000: Remove cache support Fabio Estevam
2013-05-04 20:25 ` Fabio Estevam
2013-05-05 10:15 ` Mark Brown [this message]
[not found] ` <CAKGA1bmKdtAoUP7Yn0CJRVwsCNX5JkEWdWVJj1VJBaJn+9PA=A@mail.gmail.com>
2013-05-06 22:06 ` Mark Brown
[not found] ` <CAKGA1b=+j5BpHzWOfkDv+xjLLcauHeD4jDj_Do+6ft6UPhYEtA@mail.gmail.com>
2013-05-07 23:26 ` Fabio Estevam
2013-05-08 0:57 ` Troy Kisky
2013-05-08 10:31 ` Mark Brown
2013-05-08 14:26 ` Eric Nelson
2013-05-08 14:59 ` Mark Brown
2013-05-08 15:11 ` Mark Brown
2013-05-08 16:02 ` Fabio Estevam
2013-05-08 17:14 ` Fabio Estevam
2013-05-03 19:55 Fabio Estevam
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=20130505101515.GT4945@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=eric.nelson@boundarydevices.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=matt@genesi-usa.com \
--cc=troy.kisky@boundarydevices.com \
--cc=zengzm.kernel@gmail.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