alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Michal Bachraty <michal.bachraty@streamunlimited.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	Grant Likely <grant.likely@secretlab.ca>,
	alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"Hebbar, Gururaja" <gururaja.hebbar@ti.com>
Subject: Re: davici-mcasp: "tx-num-evt" confusion with number of serializers
Date: Thu, 28 Feb 2013 14:19:21 +0100	[thread overview]
Message-ID: <512F5959.9030004@gmail.com> (raw)
In-Reply-To: <2559045.s5gCxPtNFX@ganymedes>

On 28.02.2013 12:02, Michal Bachraty wrote:
> On Thursday, February 28, 2013 10:32:15 Mike Looijmans wrote:
> 
>> That's a big improvement over "rx_num_evt". The first time I saw this
>> struct, I thought I had to set rx_num_evt to the number of receiving AXR
>> pins in use.
>>
>> Maybe call it "rx_min_fifo_depth" because just "depth" might be
>> interpreted as the capaciity or maximum size of the fifo, while in fact
>> the parameter is a minimum amount of data to be put into the FIFO
>> buffer. Of maybe "rx_fifo_thd" to indicate it's a threshhold. And use
>> the same name for the "tx" part as well (tx_fifo_thd or tx_fifo_min_depth).
> 
>  "rx_min_fifo_depth" or  "tx_min_fifo_depth"  seem to be fine.
> If I'll have time, I'll prepare patch. That's cosmetic upgrade, but should 
> help others.

Be careful with such changes. In general, DT bindings are forever in
general, because you can't update all the users out there, and so every
binding that has ever existed has to be supported in the future, for
backwards compatibility.

In this case, we might make an exception, given that for AM33xx, the
necessary DMA bits are still not missing, and Davinci is not yet fully
ported to DT either. So nobody really uses the driver on this platforms.

I copied Mark, Grant and Hebbar to get their opinions.


Daniel

  reply	other threads:[~2013-02-28 13:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 14:06 davici-mcasp: "tx-num-evt" confusion with number of serializers Michal Bachraty
2013-02-26 18:40 ` Mike Looijmans
2013-02-27 11:36   ` Michal Bachraty
2013-02-27 12:05     ` Mike Looijmans
2013-02-28  9:06       ` Michal Bachraty
2013-02-28  9:32         ` Mike Looijmans
2013-02-28 11:02           ` Michal Bachraty
2013-02-28 13:19             ` Daniel Mack [this message]
2013-02-28 13:26               ` Daniel Mack
2013-03-01 10:08                 ` Mark Brown
2013-03-06 10:51                   ` Bedia, Vaibhav
2013-03-08 16:11                     ` Michal Bachraty
2013-03-11  7:09                       ` Bedia, Vaibhav

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=512F5959.9030004@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gururaja.hebbar@ti.com \
    --cc=michal.bachraty@streamunlimited.com \
    --cc=mike.looijmans@topic.nl \
    /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;
as well as URLs for NNTP newsgroup(s).