public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Chandra shekhar <x0044955@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC/PATCH  0/4] McBSP support  for 34XX
Date: Wed, 18 Jun 2008 10:16:46 +0300	[thread overview]
Message-ID: <20080618101646.b25c6fbd.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <003a01c8cfab$67149ae0$318918ac@ent.ti.com>

> Hi,
> 
> Here is a patch that adds support for McBSP on 34XX.
> It has been verified in digital loopback mode.
> 
Hi,

I tested the set with N810 ASoC audio and still plays :-)

Some comments. First, commit messages should more descriptive than
"McBSP support for 34XX" for all of them. Like:

1. Add support for OMAP34xx McBSP ports 3-4
2. Fix register access width for OMAP34xx (this should be -rc patch?)
3. ...

> The patch includes the following features.
> 
> 1. McBSP enabled in defconfig
This should go as a separate patch since it is for 3430dsp only.

> 2. Supporting all the LP features.
> 3. Support of DMA chaining mode and one time configuration for entire
> transfer to improve performance.
> 4. Independent configurations and transfer of Rx and Tx
> 5. MCBSP data transfer in 8, 16 and 32 bit mode.
>
I think we should have some expected use case for these before adding
the features?

> 6. instead of mcbsp client configuring all the register, it allows
> clients to  configure parameters like clk polarity, clk src and other
> parameters.
> 
This would be good direction. E.g. it's bit hacky how configuration is
now done in sound/soc/omap/omap-mcbsp.c where McBSP register cache is
have to use because all of the registers are written in once with
omap_mcbsp_config.


Jarkko

  reply	other threads:[~2008-06-18  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 12:20 [RFC/PATCH 0/4] McBSP support for 34XX Chandra shekhar
2008-06-18  7:16 ` Jarkko Nikula [this message]
2008-06-18  9:17   ` shekhar, chandra

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=20080618101646.b25c6fbd.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=x0044955@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