public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Komal Shah <komal_shah802003@yahoo.com>
To: Daniel Petrini <d.pensator@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Alsa modularisations and support for tsc2101 0/7
Date: Mon, 20 Feb 2006 13:25:27 -0800 (PST)	[thread overview]
Message-ID: <20060220212527.13306.qmail@web32909.mail.mud.yahoo.com> (raw)
In-Reply-To: <9268368b0602201316q4533a165p75a4bd0ab489681d@mail.gmail.com>

--- Daniel Petrini <d.pensator@gmail.com> wrote:

> 
> That is actually good news. This means that with this proposed
> modularisation, alsa can easily work in these platforms, unless the
> 2420 dma for audio be quite different.
> Regarding the #ifdefs, one can always (carefully) insert a field in
> the new omap_alsa_codec_config and pass the architecture difference
> in
> the board* files.

Yes, it is true, being careful is good, but I think it is better to
write down a thin mcbsp framework, which does expose the apis like
mcbsp.c is doing, but the as we know that same codec chip can be
connected to different mcbsps for the same OMAP chip, which can be
passed from board-* files, also which will reduce lots of #ifders of
arch selection in mcbsp.c itself. 

I think it can be derived somewhat from the existing SPI framework, but
the difference will be no real protocol drivers, and only one master
driver (as McBSP functionality remained same irrespective of OMAP1/2
series...and I hope same for DaVinci and OMAP3, and OMAP2430 is having
5 McBSPs :)). Protocol driver can be thought of as actual codec chip,
which calls the apis exposed by McBSP fwk and gets terminated at Master driver.

---Komal Shah
http://komalshah.blogspot.com/

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  parent reply	other threads:[~2006-02-20 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 17:33 [PATCH] Alsa modularisations and support for tsc2101 0/7 Daniel Petrini
2006-02-20 19:45 ` Dirk Behme
2006-02-20 20:33 ` Komal Shah
2006-02-20 20:35   ` Daniel Petrini
2006-02-20 20:58     ` Komal Shah
     [not found]       ` <9268368b0602201316q4533a165p75a4bd0ab489681d@mail.gmail.com>
2006-02-20 21:20         ` Daniel Petrini
2006-02-20 21:25         ` Komal Shah [this message]
2006-02-20 22:35       ` lamikr
2006-02-21 13:22 ` Menon, Nishanth
2006-02-21 13:49   ` Daniel Petrini

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=20060220212527.13306.qmail@web32909.mail.mud.yahoo.com \
    --to=komal_shah802003@yahoo.com \
    --cc=d.pensator@gmail.com \
    --cc=linux-omap-open-source@linux.omap.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