All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
	Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH] ASoC: dmic codec: Support for DT
Date: Tue, 15 May 2012 22:39:48 +0100	[thread overview]
Message-ID: <20120515213947.GB4069@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FB241A3.3020104@ti.com>


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

On Tue, May 15, 2012 at 02:44:35PM +0300, Peter Ujfalusi wrote:

> I don't think that we would need platform devices for most of the
> passive components you have listed.

I don't think we do either, but I think we should handle DMICs in a
similar way - we probably want to be able to get to a place where basic
devices that don't need complex clocking arrangements can be described
with the device tree in a generic, cross-device manner.  I think that's
going to mean that we need to be able to enumerate things like which
pins on the CODEC are actually in use and where the headset is which is
going to need at least some level of description of these passives.

For internal Linux purposes we might want to do something noticeably
different with the different devices but that is an orthogonal issue to
representing the hardware in a suitably abstract format.  I would be a
bit worried if a DMIC interface was substantially different to an AMIC
interface in DT since in terms of how they interface it's really not
that big a difference.

> AFAIK (Liam can correct me if I'm wrong) the reason that we have this
> (dmic codec) is to be able to use the OMAP4+ DMIC in a card.

Oh, I understand why it's there but this is more of a Linux internal
implementation issue than anything else.

> Not entirely sure if we will need to have dts section for the dmic, I
> can just create the platform device in the abe-twl6040 machine driver if
> the setup includes digital microphones.

That's another option and certainly seems like a good stopgap when we're
currently doing the same thing for analogue interfaces - I'm much more
comfortable with adding stuff later than with putting something that
I've got concerns about in.

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

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



      reply	other threads:[~2012-05-15 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 11:55 [PATCH] ASoC: dmic codec: Support for DT Peter Ujfalusi
2012-05-08 12:58 ` Mark Brown
2012-05-09 11:28   ` Peter Ujfalusi
2012-05-15 11:44   ` Peter Ujfalusi
2012-05-15 21:39     ` Mark Brown [this message]

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=20120515213947.GB4069@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=misael.lopez@ti.com \
    --cc=peter.ujfalusi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.