From: Mark Brown <broonie@sirena.org.uk>
To: Troy Kisky <troy.kisky@boundarydevices.com>
Cc: alsa-devel@alsa-project.org, Arun KS <arunks@mistralsolutions.com>
Subject: Re: [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec
Date: Mon, 29 Sep 2008 17:54:05 +0100 [thread overview]
Message-ID: <20080929165404.GA16109@sirena.org.uk> (raw)
In-Reply-To: <48E1068E.7020908@boundarydevices.com>
On Mon, Sep 29, 2008 at 09:47:10AM -0700, Troy Kisky wrote:
> Great. I just finished the same thing for davinci but using spi.
> I was waiting until the adc issue I mentioned yesterday was resolved before posting it.
> I'm glad I won't have to now. But my board also has I2c, just not with this
It'd be great if you could work with Arun to ensure that all the
features which you are using are supported in the driver - it looks like
at least SPI support will need to be added.
> codec. Can the I2c code be moved into the board directory? I have my spi code
> in the board directory and just pass the write function pointer. i.e.
No, the I2C and SPI support should both be part of the driver. The
driver should just be modified to allow both I2C and SPI support to be
compiled in and let the board driver register the appropriate one at run
time.
next prev parent reply other threads:[~2008-09-29 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 9:41 [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec Arun KS
2008-09-29 16:47 ` Troy Kisky
2008-09-29 16:54 ` Mark Brown [this message]
2008-09-29 17:05 ` Troy Kisky
2008-09-29 17:32 ` Mark Brown
2008-09-29 17:27 ` Troy Kisky
2008-09-29 17:39 ` Mark Brown
2008-09-29 17:58 ` Troy Kisky
2008-09-29 18:30 ` Mark Brown
2008-09-29 19:07 ` Troy Kisky
2008-09-29 19:50 ` Mark Brown
2008-09-29 21:15 ` Troy Kisky
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 9:41 Arun KS
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=20080929165404.GA16109@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=troy.kisky@boundarydevices.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.