All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [BAD PATCH] ice1712: Add support for Philips PSC724 Ultimate Edge
Date: Wed, 14 Mar 2012 09:07:57 +0100	[thread overview]
Message-ID: <4F6051DD.9000808@ivitera.com> (raw)
In-Reply-To: <20120313213322.GB16460@sirena.org.uk>

Dne 13.3.2012 22:33, Mark Brown napsal(a):
> On Tue, Mar 13, 2012 at 10:25:54PM +0100, Pavel Hofman wrote:
> 
>> I always found that a simple proc interface listing all register values
>> of the chips onboard greatly helped with troubleshooting. E.g.
>> http://git.alsa-project.org/?p=alsa-kmirror.git;a=blob;f=i2c/other/ak4xxx-adda.c;h=cef813d23641afcd39b56a57c5fc8058cb99bfb0;hb=HEAD#l879
> 
>> http://git.alsa-project.org/?p=alsa-kmirror.git;a=blob;f=i2c/other/ak4114.c;h=fdf3c1b65e388414c995a597ef2b351b4ec2a220;hb=HEAD#l451
> 
> If you use regmap for your register I/O you get this for free (plus some
> other infrastructure stuff).


Mark, thanks for the information. I searched sound-2.6 tree and found
the only reference to linux/regmap.h in soc-io.c. Please could you point
me to a place where it is used in alsa source code so that I could take
it as an example? I have no problem with using the latest kernel
infrastructure helpers but there are just too many of them.

Thanks a lot,

Pavel.

  reply	other threads:[~2012-03-14  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 20:59 [BAD PATCH] ice1712: Add support for Philips PSC724 Ultimate Edge Ondrej Zary
2012-03-13 21:25 ` Pavel Hofman
2012-03-13 21:33   ` Mark Brown
2012-03-14  8:07     ` Pavel Hofman [this message]
2012-03-14 12:34       ` Mark Brown
2012-03-20 23:03 ` Ondrej Zary
2012-04-01 19:44   ` Ondrej Zary

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=4F6051DD.9000808@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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.