public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Petrini" <d.pensator@gmail.com>
To: "Menon, Nishanth" <x0nishan@ti.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] Alsa modularisations and support for tsc2101 2/7
Date: Tue, 21 Feb 2006 10:06:12 -0400	[thread overview]
Message-ID: <9268368b0602210606y5a84b111g459f2b293d4ece4@mail.gmail.com> (raw)
In-Reply-To: <520AB2AD990DC04082102F77CA1726381036EB@dlee03.ent.ti.com>

HI Nishanth,

Thanks for the comments.

On 2/21/06, Menon, Nishanth <x0nishan@ti.com> wrote:
>
>
> Nope, does not look a good idea to me, as we will not be able to pull these
> out for 2420/2430 platforms(unless we move it to plat). why keep the
> tsc2101/aic in platforms specific directory if:
> 1. it can have varied control path
> 2. data transfer paths?
> 3. defined set of apis which can be called  by an higher abstraction layer?

Indeed. We already make up our mind. These files will leave this directory :-) .

> I can see the transfer configuration is mainly setup from board file, which
> is an excellent idea. however for codecs.. err.. sound/... is a nice place
> for it to remain..

You mean the codec files moving to sound/ ? With this board file
approach this cause problems in linking the codec functions in the
board file. They had to stay in the omap tree not in the sound/ .
Maybe a better place to them could be plat-omap/ ?

> This will allow:
> 1. Other platforms other than omap also to be able to use tsc2101
> functionalilty
> 2. have common support for alsa and oss - i dont see oss dying a lot sooner
> ;)
> why would we want to stop the cross leverage?

Anyway, with this approach they can be used in other architectures as
well with small modifications. And in omap oss too.

> Regards,
> Nishanth Menon

Regards,
Daniel
--
INdT - Manaus - Brazil

  reply	other threads:[~2006-02-21 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 17:47 [PATCH] Alsa modularisations and support for tsc2101 2/7 Daniel Petrini
2006-02-21 13:31 ` Menon, Nishanth
2006-02-21 14:06   ` Daniel Petrini [this message]
2006-02-21 14:08     ` Menon, Nishanth
2006-02-21 23:53       ` lamikr
2006-02-22 18:15         ` Tony Lindgren

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=9268368b0602210606y5a84b111g459f2b293d4ece4@mail.gmail.com \
    --to=d.pensator@gmail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=x0nishan@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox