alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	Grant Likely <grant.likely@secretlab.ca>,
	alsa-devel@alsa-project.org,
	Michal Bachraty <michal.bachraty@streamunlimited.com>,
	"Hebbar, Gururaja" <gururaja.hebbar@ti.com>
Subject: Re: davici-mcasp: "tx-num-evt" confusion with number of serializers
Date: Fri, 1 Mar 2013 18:08:27 +0800	[thread overview]
Message-ID: <20130301100820.GU25302@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <512F5B1C.4020508@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]

On Thu, Feb 28, 2013 at 02:26:52PM +0100, Daniel Mack wrote:
> On 28.02.2013 14:19, Daniel Mack wrote:

> > 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.

> Sorry, let me rephrase that last paragraph:

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

Sounds plausible, though without having seen the actual change I can't
comment for certain.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2013-03-01 10:08 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
2013-02-28 13:26               ` Daniel Mack
2013-03-01 10:08                 ` Mark Brown [this message]
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=20130301100820.GU25302@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gururaja.hebbar@ti.com \
    --cc=michal.bachraty@streamunlimited.com \
    --cc=mike.looijmans@topic.nl \
    --cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).