All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Fri, 19 Oct 2012 16:18:16 +0800	[thread overview]
Message-ID: <50810CC8.4050009@atmel.com> (raw)
In-Reply-To: <5080F54F.4000600@atmel.com>

Cc:
    linux-arm-kernel mailing list
    devicetree-discuss mailing list
    alsa-devel mailing list
    linux-sound mailing list


On 10/19/2012 14:38, Bo Shen wrote:
> Hi Mark Brown,
>    Now, I am trying to move atmel audio part to DT support. I meet the
> following issue.
>
>    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:
> ---<8---
> ssc0: ssc@fffbc000 {
>                  status = "okay";
> };
>
> dai0: dai {
>                  compatible = "atmel,atmel-ssc-dai";
>          };
>
> sound {
>                  compatible = "atmel,at91sam9g20-audio";
>                  atmel,model = "wm8731 @ sam9g20ek";
>
>                  atmel,audio-routing =
>                          "Ext Spk", "LHPOUT",
>                          "Int Mic", "MICIN";
>
>                  atmel,audio-codec = <&wm8731>;
>                  atmel,dai = <&dai>;
> };
> --->8---
>
>    Would this be OK?
>    If not, may I add some code for ssc which dedicate for audio into
> sound/soc/atmel (using audio-ssc and ssc to distiguish which dedicate
> for audio, which used for ssc library)? This will broken the exist code
> for audio (only sam9g20-wm8731).
>    Any suggestion?

WARNING: multiple messages have this Message-ID (diff)
From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Fri, 19 Oct 2012 08:18:16 +0000	[thread overview]
Message-ID: <50810CC8.4050009@atmel.com> (raw)
In-Reply-To: <5080F54F.4000600@atmel.com>

Cc:
    linux-arm-kernel mailing list
    devicetree-discuss mailing list
    alsa-devel mailing list
    linux-sound mailing list


On 10/19/2012 14:38, Bo Shen wrote:
> Hi Mark Brown,
>    Now, I am trying to move atmel audio part to DT support. I meet the
> following issue.
>
>    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:
> ---<8---
> ssc0: ssc@fffbc000 {
>                  status = "okay";
> };
>
> dai0: dai {
>                  compatible = "atmel,atmel-ssc-dai";
>          };
>
> sound {
>                  compatible = "atmel,at91sam9g20-audio";
>                  atmel,model = "wm8731 @ sam9g20ek";
>
>                  atmel,audio-routing >                          "Ext Spk", "LHPOUT",
>                          "Int Mic", "MICIN";
>
>                  atmel,audio-codec = <&wm8731>;
>                  atmel,dai = <&dai>;
> };
> --->8---
>
>    Would this be OK?
>    If not, may I add some code for ssc which dedicate for audio into
> sound/soc/atmel (using audio-ssc and ssc to distiguish which dedicate
> for audio, which used for ssc library)? This will broken the exist code
> for audio (only sam9g20-wm8731).
>    Any suggestion?


WARNING: multiple messages have this Message-ID (diff)
From: voice.shen@atmel.com (Bo Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: Question about move atmel audio part to DT support
Date: Fri, 19 Oct 2012 16:18:16 +0800	[thread overview]
Message-ID: <50810CC8.4050009@atmel.com> (raw)
In-Reply-To: <5080F54F.4000600@atmel.com>

Cc:
    linux-arm-kernel mailing list
    devicetree-discuss mailing list
    alsa-devel mailing list
    linux-sound mailing list


On 10/19/2012 14:38, Bo Shen wrote:
> Hi Mark Brown,
>    Now, I am trying to move atmel audio part to DT support. I meet the
> following issue.
>
>    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:
> ---<8---
> ssc0: ssc at fffbc000 {
>                  status = "okay";
> };
>
> dai0: dai {
>                  compatible = "atmel,atmel-ssc-dai";
>          };
>
> sound {
>                  compatible = "atmel,at91sam9g20-audio";
>                  atmel,model = "wm8731 @ sam9g20ek";
>
>                  atmel,audio-routing =
>                          "Ext Spk", "LHPOUT",
>                          "Int Mic", "MICIN";
>
>                  atmel,audio-codec = <&wm8731>;
>                  atmel,dai = <&dai>;
> };
> --->8---
>
>    Would this be OK?
>    If not, may I add some code for ssc which dedicate for audio into
> sound/soc/atmel (using audio-ssc and ssc to distiguish which dedicate
> for audio, which used for ssc library)? This will broken the exist code
> for audio (only sam9g20-wm8731).
>    Any suggestion?

       reply	other threads:[~2012-10-19  8:18 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 ` Bo Shen [this message]
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-25 16:40   ` Mark Brown
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=50810CC8.4050009@atmel.com \
    --to=voice.shen@atmel.com \
    --cc=JM.Lin@atmel.com \
    --cc=Nicolas.FERRE@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sound@vger.kernel.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 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.