All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: asoc: s3c24xx+uda1380 - some questions
Date: Tue, 27 Jan 2009 17:19:53 +0200	[thread overview]
Message-ID: <200901271720.03880.anarsoul@gmail.com> (raw)
In-Reply-To: <20090127150040.GD11870@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]

On Tuesday 27 January 2009 17:00:41 Mark Brown wrote:

> CCing in Philipp Zabel who wrote the UDA1380 driver.  Assuming you mean
> control to cut the power to the chip the most standard way of doing it
> would be with the regulator API but if the chip isn't being used much in
> new designs it might not be worth it.

Uh-oh, I didn't thought that it will be so complicated to decide when turn one 
gpio line to 0 or 1 :) Btw, I'm thinking about using own write- and read- 
wrappers for uda1380, in this way I can check on each read/write whether 
codec power is enabled.

> That sounds like something in the teardown path should be done on
> startup as well.  Can't think of any obvious gotchas there, though I'd
> be looking at the codec and machine drivers since the CPU driver for the
> S3C24xx is used in quite a few designs.

Sorry, but what is "teardown path"?

Regards
Vasily

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-01-27 15:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 13:19 asoc: s3c24xx+uda1380 - some questions Vasily Khoruzhick
2009-01-27 15:00 ` Mark Brown
2009-01-27 15:19   ` Vasily Khoruzhick [this message]
2009-01-27 15:25     ` Mark Brown
2009-01-27 15:49       ` Vasily Khoruzhick
2009-01-27 16:06         ` pHilipp Zabel
2009-01-27 16:22           ` Vasily Khoruzhick
2009-01-27 19:49             ` pHilipp Zabel
2009-01-27 20:32               ` Vasily Khoruzhick
2009-02-02 23:46                 ` Vasily Khoruzhick
2009-02-03 11:41                   ` Mark Brown
2009-02-03 11:57                     ` Vasily Khoruzhick
2009-02-03 12:05                       ` Mark Brown
2009-02-03 13:52                         ` Vasily Khoruzhick
2009-02-03 16:09                           ` pHilipp Zabel
2009-02-03 17:21                           ` Mark Brown
2009-01-27 20:00             ` Mark Brown
2009-01-27 20:14               ` Vasily Khoruzhick
2009-01-27 20:19                 ` 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=200901271720.03880.anarsoul@gmail.com \
    --to=anarsoul@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=philipp.zabel@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 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.