linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem
Date: Sat, 10 Aug 2013 11:16:19 +0200	[thread overview]
Message-ID: <20130810111619.3444fda5@skate> (raw)
In-Reply-To: <20130809110623.7bb3e7ad@armhf>

Dear Jean-Francois Moine,

On Fri, 9 Aug 2013 11:06:23 +0200, Jean-Francois Moine wrote:

> > we need at least two more compatibles for the audio controller found on
> > Dove and Kirkwood respectively. This is how we are going to distinguish
> > those two, e.g. Kirkwood has SPDIF in which Dove hasn't.
> 
> Sebastian,
> 
> s/has/hasn't & s/hasn't/has
> 
> Are 2 compatibles enough, i.e. "mvebu-audio" and "mbevu-audio-spdif"?

Or:

	marvell,kirkwood-audio
	marvell,dove-audio

> > Also, we have used "marvell" as prefix for a long time. I know there has
> > been discussion about the stock ticker appreviation, has there been any
> > decision on that already?
> 
> Don't know, but, sure, there are still a lot of "mrvl".

Yes, but they are being converted over to 'marvell', I've seen some
patches posted. Also, as per
Documentation/devicetree/bindings/vendor-prefixes.txt, 'marvell' is the
right prefix for Marvell compatible strings.


> > Also we will need some phandle reference to the audio codec here. As
> > this property is ongoing work in ASoC core, I suggest we wait for it
> > and propose a binding afterwards.
> 
> I don't think that we need any reference to the codec here. The glue is
> done by the audio device. For example, using the (soon?) extended
> simple audio card:

Have you looked at the Samsung DT bindings for audio:

        sound {
                compatible = "samsung,smdk-wm8994";

                samsung,i2s-controller = <&i2s0>;
                samsung,audio-codec = <&wm8994>;
        };

it definitely has a codec phandle reference here.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-08-10  9:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 11:22 [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem Jean-Francois Moine
2013-08-09  8:23 ` Sebastian Hesselbarth
2013-08-09  9:06   ` Jean-Francois Moine
2013-08-09  9:30     ` Russell King - ARM Linux
2013-08-10  9:16     ` Thomas Petazzoni [this message]
2013-08-09  9:19   ` Mark Brown
2013-08-09  9:34     ` Sebastian Hesselbarth
2013-08-09  9:43       ` Russell King - ARM Linux
2013-08-09 10:30         ` [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem [OT] Jean-Francois Moine
2013-08-09 11:01         ` [PATCH v4 1/1] ASoc: kirkwood: add DT support to the mvebu audio subsystem Sebastian Hesselbarth
2013-08-09 11:39           ` Mark Brown
2013-08-09 13:09             ` Russell King - ARM Linux
2013-08-09 18:00               ` Mark Brown
2013-08-09 18:25                 ` Russell King - ARM Linux
2013-08-09 19:44                   ` Mark Brown
2013-08-09 20:38                     ` Russell King - ARM Linux
2013-08-09 23:42                       ` Mark Brown
2013-08-10  9:31                         ` Russell King - ARM Linux
2013-08-10 11:12                           ` Mark Brown
2013-08-09 10:05       ` [alsa-devel] " Lars-Peter Clausen
2013-08-09 10:18         ` Mark Brown

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=20130810111619.3444fda5@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).