All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	patches@opensource.wolfsonmicro.com,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: soc-core: Add support for NULL default register caches
Date: Mon, 10 Jan 2011 16:10:52 -0600	[thread overview]
Message-ID: <4D2B83EC.4000400@freescale.com> (raw)
In-Reply-To: <1294654256-1012-1-git-send-email-dp@opensource.wolfsonmicro.com>

Dimitris Papastamos wrote:
> The infrastructure for handling NULL default register maps is already
> included in the soc-cache code, just ensure that we don't try to dereference
> a NULL pointer while accessing a NULL register cache.
> 
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>

Acked-by: Timur Tabi <timur@freescale.com>

This fixes the kernel panic I was seeing earlier with my CS4270 driver, but it's
not a replacement for my patch, "[v3] ASoC: cs4270: use the built-in register
cache support".

With Dimitris' patch alone, the CS4270 still has other bugs:

# cat ./devices/platform/soc-audio/playback/codec_reg
cs4270-codec.0-004f registers
 0: <no data: -5>
 1:   c3
 2:    0
 3:   30
 4:    0
 5:    0
 6:    0
 7:    0


So both patches need to be applied, however, I can't say whether Dimitris' patch
is sufficient for handling NULL default register maps, since I removed that from
my driver.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2011-01-10 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 10:10 [PATCH] ASoC: soc-core: Add support for NULL default register caches Dimitris Papastamos
2011-01-10 21:48 ` Liam Girdwood
2011-01-10 22:10 ` Timur Tabi [this message]
2011-01-10 22:29   ` Mark Brown
2011-01-10 22:40     ` Timur Tabi
2011-01-10 23:48       ` Mark Brown
2011-01-10 22:25 ` Mark Brown

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=4D2B83EC.4000400@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=patches@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.