Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"subaparts@yandex.ru" <subaparts@yandex.ru>,
	"Handrigan, Paul" <Paul.Handrigan@cirrus.com>
Subject: Re: [PATCH] ASoC: cs4271: claim reset GPIO in bus probe function
Date: Wed, 19 Feb 2014 17:17:42 +0100	[thread overview]
Message-ID: <5304D926.7070505@zonque.org> (raw)
In-Reply-To: <993D86A8-0838-4A12-9BF7-F7BC1564F355@cirrus.com>

On 02/19/2014 05:08 PM, Austin, Brian wrote:
>> On Feb 19, 2014, at 7:06, "Daniel Mack" <zonque@gmail.com> wrote:

>> -    if (gpio_nreset >= 0)
>> -        if (devm_gpio_request(codec->dev, gpio_nreset, "CS4271 Reset"))
>> -            gpio_nreset = -EINVAL;
>> -    if (gpio_nreset >= 0) {
>> +    if (gpio_is_valid(cs4271->gpio_nreset)) {
>>        /* Reset codec */
>> -        gpio_direction_output(gpio_nreset, 0);
>> +        gpio_direction_output(cs4271->gpio_nreset, 0);
>>        udelay(1);
>> -        gpio_set_value(gpio_nreset, 1);
>> +        gpio_set_value(cs4271->gpio_nreset, 1);
>>        /* Give the codec time to wake up */
>>        udelay(1);
>>    }
>
> Since your moving all the GPIO reset code into a new function that's
> called from the bus probes why not put the reset in there as well?

Because I want the codec to stay in reset until it is actually used, and
the machine drivers builds the DAI link.


Daniel

  reply	other threads:[~2014-02-19 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 13:05 [PATCH] ASoC: cs4271: claim reset GPIO in bus probe function Daniel Mack
2014-02-19 16:08 ` Austin, Brian
2014-02-19 16:17   ` Daniel Mack [this message]
2014-02-19 16:27     ` Austin, Brian
2014-02-19 16:30 ` Austin, Brian
2014-02-19 16:36 ` 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=5304D926.7070505@zonque.org \
    --to=daniel@zonque.org \
    --cc=Brian.Austin@cirrus.com \
    --cc=Paul.Handrigan@cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=subaparts@yandex.ru \
    /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