From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Alexander Sverdlin <subaparts@yandex.ru>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] EDB93xx: Add support for CS4271 CODEC on EDB93xx boards
Date: Wed, 2 Feb 2011 17:00:00 +0000 [thread overview]
Message-ID: <20110202165959.GT12743@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764CEFD45C8@AUSP01VMBX24.collaborationhost.net>
On Wed, Feb 02, 2011 at 10:53:15AM -0600, H Hartley Sweeten wrote:
> I don't have any problem with leaving the reset management in the codec.
> The enable (chip-select) should be handled in the platform code. But,
> gpio_disable should be removed from struct cs4271_platform_data to avoid
> any confusion.
Is that really a chip select or is it a power control?
next prev parent reply other threads:[~2011-02-02 17:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 23:40 [PATCH] EDB93xx: Add support for CS4271 CODEC on EDB93xx boards Alexander Sverdlin
2011-02-02 0:02 ` H Hartley Sweeten
2011-02-02 10:48 ` Alexander Sverdlin
2011-02-02 10:49 ` Mark Brown
2011-02-02 11:12 ` Alexander Sverdlin
2011-02-02 12:53 ` Mark Brown
2011-02-02 13:26 ` Alexander Sverdlin
2011-02-02 16:53 ` H Hartley Sweeten
2011-02-02 17:00 ` Mark Brown [this message]
2011-02-02 17:21 ` H Hartley Sweeten
2011-02-02 17:33 ` Alexander Sverdlin
2011-02-02 17:48 ` H Hartley Sweeten
2011-02-02 18:31 ` Mark Brown
2011-02-02 18:18 ` H Hartley Sweeten
2011-02-02 16:45 ` H Hartley Sweeten
2011-02-02 7:54 ` Mika Westerberg
2011-02-02 16:27 ` [alsa-devel] " H Hartley Sweeten
2011-02-02 10:51 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2011-01-23 0:51 Alexander Sverdlin
2011-01-24 16:30 ` H Hartley Sweeten
2011-01-25 11:46 ` Mark Brown
2011-01-25 12:08 ` Alexander Sverdlin
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=20110202165959.GT12743@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=buytenh@wantstofly.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).