Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Mark Brown <broonie@sirena.org.uk>
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 10:05:02 -0700	[thread overview]
Message-ID: <48E10ABE.5030703@boundarydevices.com> (raw)
In-Reply-To: <20080929165404.GA16109@sirena.org.uk>

Mark Brown wrote:
> On Mon, Sep 29, 2008 at 09:47:10AM -0700, Troy Kisky wrote:
> 
> 
> 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.
> 

Seems to me a Kconfig option would be more efficient. Otherwise, one of the
two options is just going to waste space.

Troy

  reply	other threads:[~2008-09-29 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dfeb90390809290241h2219ef57q2a7401aebf47efe5@mail.gmail.com>
2008-09-29 16:47 ` [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec Troy Kisky
2008-09-29 16:54   ` Mark Brown
2008-09-29 17:05     ` Troy Kisky [this message]
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
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=48E10ABE.5030703@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arunks@mistralsolutions.com \
    --cc=broonie@sirena.org.uk \
    /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