From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: alsa-devel@alsa-project.org, "Lin, JM" <JM.Lin@atmel.com>,
"Ferre, Nicolas" <Nicolas.FERRE@atmel.com>,
linux-sound@vger.kernel.org,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Question about move atmel audio part to DT support
Date: Thu, 25 Oct 2012 17:40:08 +0100 [thread overview]
Message-ID: <20121025164008.GQ18814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50810CC8.4050009@atmel.com>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
On Fri, Oct 19, 2012 at 04:18:16PM +0800, Bo Shen wrote:
> Cc:
> linux-arm-kernel mailing list
> devicetree-discuss mailing list
> alsa-devel mailing list
> linux-sound mailing list
Better to resend for things like this rather than double quote.
>
> > Atmel audio part has three platform device:
> > -> atmel ssc: ssc library (different SOC has different number)
> > -> atmel ssc dai: dai for audio
> > -> atmel pcm: for pdc or dma transfer (now only support pdc, dma
> >support will add soon)
> > In DT support kernel, I don't find any similar case. So, if I want to
> >keep ssc as library, and use dai to register pcm. Then the dts file will
> >like:
I'm not seeing anything at all unusual about the above situation - it'd
help if you could explain what you think is complex here?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: alsa-devel@alsa-project.org, "Lin, JM" <JM.Lin@atmel.com>,
"Ferre, Nicolas" <Nicolas.FERRE@atmel.com>,
linux-sound@vger.kernel.org,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Question about move atmel audio part to DT support
Date: Thu, 25 Oct 2012 16:40:08 +0000 [thread overview]
Message-ID: <20121025164008.GQ18814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50810CC8.4050009@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Fri, Oct 19, 2012 at 04:18:16PM +0800, Bo Shen wrote:
> Cc:
> linux-arm-kernel mailing list
> devicetree-discuss mailing list
> alsa-devel mailing list
> linux-sound mailing list
Better to resend for things like this rather than double quote.
>
> > Atmel audio part has three platform device:
> > -> atmel ssc: ssc library (different SOC has different number)
> > -> atmel ssc dai: dai for audio
> > -> atmel pcm: for pdc or dma transfer (now only support pdc, dma
> >support will add soon)
> > In DT support kernel, I don't find any similar case. So, if I want to
> >keep ssc as library, and use dai to register pcm. Then the dts file will
> >like:
I'm not seeing anything at all unusual about the above situation - it'd
help if you could explain what you think is complex here?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Question about move atmel audio part to DT support
Date: Thu, 25 Oct 2012 17:40:08 +0100 [thread overview]
Message-ID: <20121025164008.GQ18814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50810CC8.4050009@atmel.com>
On Fri, Oct 19, 2012 at 04:18:16PM +0800, Bo Shen wrote:
> Cc:
> linux-arm-kernel mailing list
> devicetree-discuss mailing list
> alsa-devel mailing list
> linux-sound mailing list
Better to resend for things like this rather than double quote.
>
> > Atmel audio part has three platform device:
> > -> atmel ssc: ssc library (different SOC has different number)
> > -> atmel ssc dai: dai for audio
> > -> atmel pcm: for pdc or dma transfer (now only support pdc, dma
> >support will add soon)
> > In DT support kernel, I don't find any similar case. So, if I want to
> >keep ssc as library, and use dai to register pcm. Then the dts file will
> >like:
I'm not seeing anything at all unusual about the above situation - it'd
help if you could explain what you think is complex here?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121025/475b32d6/attachment.sig>
next prev parent reply other threads:[~2012-10-25 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5080F54F.4000600@atmel.com>
2012-10-19 8:18 ` Question about move atmel audio part to DT support Bo Shen
2012-10-19 8:18 ` Bo Shen
2012-10-19 8:18 ` Bo Shen
2012-10-25 16:40 ` Mark Brown [this message]
2012-10-25 16:40 ` Mark Brown
2012-10-25 16:40 ` Mark Brown
2012-10-26 1:26 ` Bo Shen
2012-10-26 1:26 ` Bo Shen
2012-10-26 1:26 ` Bo Shen
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=20121025164008.GQ18814@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=JM.Lin@atmel.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=voice.shen@atmel.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.