From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: WM8985: Register notifier for the regulator being disabled
Date: Thu, 30 Sep 2010 10:51:32 +0100 [thread overview]
Message-ID: <1285840292.4722.17.camel@dplaptop> (raw)
In-Reply-To: <20100929174322.GA31934@opensource.wolfsonmicro.com>
On Wed, 2010-09-29 at 10:43 -0700, Mark Brown wrote:
> Note that the whole callback thing is more important for things with
> idle_bias_off (which might get the regulators powered down at runtime)
> than for other things which don't go down to _BIAS_OFF at runtime so
> would only trigger the callback on suspend anyway.
Ok I will revert this patch then. The reason why I did not set
idle_bias_off is that I could not guarantee that the driver would still
function properly without testing it.
> Always split different things out into separate patches unless they
> overlap with each other a lot.
Yup indeed.
> It's better to restructure the code so that the compiler is able to
> follow the control flow and see that there's no uninitialised access -
> this sort of change will just shut up legitimate warnings as well. Some
> of the other CODEC drivers (wm8400 is one) have had similar changes
> which seem to do the trick.
My version of GCC (4.5.1) does not seem to have a problem figuring out
the flow of execution. It is just that some of the people who use this
code and have an older version of GCC get these warnings. I agree this
is not the way to fix it as it silences legitimate warnings. However I
can't really test any changes I make in an attempt to fixing this due
to not having an older version of gcc.
Thanks,
Dimitrios
next prev parent reply other threads:[~2010-09-30 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 10:38 [PATCH] ASoC: WM8985: Register notifier for the regulator being disabled Dimitris Papastamos
2010-09-29 17:43 ` Mark Brown
2010-09-30 9:51 ` Dimitris Papastamos [this message]
2010-09-30 16:40 ` 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=1285840292.4722.17.camel@dplaptop \
--to=dp@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@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.