From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
Andrew Jackson <Andrew.Jackson@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Rajeev Kumar <rajeevkumar.linux@gmail.com>
Subject: Re: [PATCH 4/5] ASoC: dwc: Add devicetree support for Designware I2S
Date: Thu, 04 Dec 2014 10:55:55 +0100 [thread overview]
Message-ID: <2240364.fL8B0EDbFB@wuerfel> (raw)
In-Reply-To: <20141203201905.GO7712@sirena.org.uk>
On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
> On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
>
> > I don't think we even have to worry about the platform_data case here:
> > the only platform using this hardware in Linux is arm/mach-spear, and
> > it defines a device node with a binding that is similar to the one you
> > document here but that is not implemented in the driver.
>
> Not all the world uses DT, this is a DesignWare IP so it's likely to get
> deployed widely - potentially on PCI cards and things like that.
It's not really new though, and we are only seeing the second user.
Maybe this one just isn't as common as a lot of the other designware IP?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ASoC: dwc: Add devicetree support for Designware I2S
Date: Thu, 04 Dec 2014 10:55:55 +0100 [thread overview]
Message-ID: <2240364.fL8B0EDbFB@wuerfel> (raw)
In-Reply-To: <20141203201905.GO7712@sirena.org.uk>
On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
> On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
>
> > I don't think we even have to worry about the platform_data case here:
> > the only platform using this hardware in Linux is arm/mach-spear, and
> > it defines a device node with a binding that is similar to the one you
> > document here but that is not implemented in the driver.
>
> Not all the world uses DT, this is a DesignWare IP so it's likely to get
> deployed widely - potentially on PCI cards and things like that.
It's not really new though, and we are only seeing the second user.
Maybe this one just isn't as common as a lot of the other designware IP?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Brown <broonie@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Jackson <Andrew.Jackson@arm.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>,
Rajeev Kumar <rajeevkumar.linux@gmail.com>
Subject: Re: [PATCH 4/5] ASoC: dwc: Add devicetree support for Designware I2S
Date: Thu, 04 Dec 2014 10:55:55 +0100 [thread overview]
Message-ID: <2240364.fL8B0EDbFB@wuerfel> (raw)
In-Reply-To: <20141203201905.GO7712@sirena.org.uk>
On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
> On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
>
> > I don't think we even have to worry about the platform_data case here:
> > the only platform using this hardware in Linux is arm/mach-spear, and
> > it defines a device node with a binding that is similar to the one you
> > document here but that is not implemented in the driver.
>
> Not all the world uses DT, this is a DesignWare IP so it's likely to get
> deployed widely - potentially on PCI cards and things like that.
It's not really new though, and we are only seeing the second user.
Maybe this one just isn't as common as a lot of the other designware IP?
Arnd
next prev parent reply other threads:[~2014-12-04 9:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:39 [PATCH 4/5] ASoC: dwc: Add devicetree support for Designware I2S Andrew Jackson
2014-12-03 16:39 ` Andrew Jackson
2014-12-03 18:23 ` Mark Brown
2014-12-03 18:23 ` Mark Brown
2014-12-04 9:42 ` Andrew Jackson
2014-12-04 9:42 ` Andrew Jackson
2014-12-04 9:42 ` Andrew Jackson
2014-12-03 20:13 ` Arnd Bergmann
2014-12-03 20:13 ` Arnd Bergmann
2014-12-03 20:19 ` Mark Brown
2014-12-03 20:19 ` Mark Brown
2014-12-03 20:19 ` Mark Brown
2014-12-04 9:55 ` Arnd Bergmann [this message]
2014-12-04 9:55 ` Arnd Bergmann
2014-12-04 9:55 ` Arnd Bergmann
2014-12-04 11:07 ` Mark Brown
2014-12-04 11:07 ` Mark Brown
2014-12-04 11:17 ` Arnd Bergmann
2014-12-04 11:17 ` Arnd Bergmann
2014-12-04 11:33 ` Mark Brown
2014-12-04 11:33 ` Mark Brown
2014-12-04 9:43 ` Andrew Jackson
2014-12-04 9:43 ` Andrew Jackson
2014-12-04 9:43 ` Andrew Jackson
2014-12-04 7:02 ` rajeev kumar
2014-12-04 7:02 ` rajeev kumar
2014-12-04 7:02 ` rajeev kumar
2014-12-04 7:43 ` rajeev kumar
2014-12-04 7:43 ` rajeev kumar
2014-12-04 10:00 ` Andrew Jackson
2014-12-04 10:00 ` Andrew Jackson
2014-12-04 10:00 ` Andrew Jackson
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=2240364.fL8B0EDbFB@wuerfel \
--to=arnd@arndb.de \
--cc=Andrew.Jackson@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajeevkumar.linux@gmail.com \
--cc=tiwai@suse.de \
/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.