From: Mark Brown <broonie@kernel.org>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Mark Rutland <mark.rutland@arm.com>,
Jean-Francois Moine <moinejf@free.fr>,
Russell King <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
Pawel Moll <pawel.moll@arm.com>,
devicetree@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 1/2] ARM: Dove: Add the audio devices in DT
Date: Thu, 29 Aug 2013 17:12:17 +0100 [thread overview]
Message-ID: <20130829161217.GK10783@sirena.org.uk> (raw)
In-Reply-To: <521DD057.4040208@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
On Wed, Aug 28, 2013 at 12:26:31PM +0200, Sebastian Hesselbarth wrote:
> Unfortunately, mvebu-audio has already been taken by Mark. Also, we
> know the differences for the three SoCs now and should have a compatible
> for each (and maybe mvebu-audio for fallback).
We're not at the merge window yet so we can always change it. We can
also add additional compatible strings to the drivers at any point - the
device can list as many as it likes, this is useful if you've got new
controllers which are supersets of old ones for example.
> Also, we'll need to distinguish between the different audio controllers
> on a single SoC, i.e. i2s0 and i2s1. I suggest checking the (phys) reg
> base passed.
Why is this required - ideally this would have been mentioned in some of
the previous reviews...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-29 16:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 9:34 Jean-Francois Moine
2013-08-28 10:13 ` Sebastian Hesselbarth
2013-08-28 10:19 ` Thomas Petazzoni
2013-08-28 10:26 ` Sebastian Hesselbarth
2013-08-28 11:15 ` Thomas Petazzoni
2013-08-28 11:44 ` Sebastian Hesselbarth
2013-08-28 11:58 ` Thomas Petazzoni
2013-08-28 12:13 ` Russell King - ARM Linux
2013-08-28 12:29 ` Thomas Petazzoni
2013-08-28 12:42 ` Russell King - ARM Linux
2013-08-28 12:51 ` Thomas Petazzoni
2013-08-28 13:58 ` Russell King - ARM Linux
2013-08-28 12:16 ` Sebastian Hesselbarth
2013-08-29 10:07 ` Jean-Francois Moine
2013-08-29 10:13 ` Russell King - ARM Linux
2013-08-29 11:01 ` Sebastian Hesselbarth
2013-08-30 15:08 ` Russell King - ARM Linux
2013-08-29 9:46 ` Jean-Francois Moine
2013-08-29 16:12 ` Mark Brown [this message]
2013-08-29 16:33 ` Russell King - ARM Linux
2013-08-29 17:12 ` Mark Brown
2013-08-29 18:02 ` Sebastian Hesselbarth
2013-08-29 18:20 ` Mark Brown
2013-08-29 18:34 ` Russell King - ARM Linux
2013-08-28 19:49 ` Sergei Shtylyov
2013-08-29 9:38 ` Jean-Francois Moine
2013-08-29 14:13 ` Sergei Shtylyov
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=20130829161217.GK10783@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=ian.campbell@citrix.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=moinejf@free.fr \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=thomas.petazzoni@free-electrons.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
all inboxes | Powered by JetHome®