From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, devicetree-discuss@lists.ozlabs.org,
nicolas.ferre@atmel.com, linux-sound@vger.kernel.org,
plagnioj@jcrosoft.com, jm.lin@atmel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/5] ASoC: sam9g20_wm8731: convert to device tree support
Date: Mon, 29 Oct 2012 14:38:17 +0800 [thread overview]
Message-ID: <508E2459.5090707@atmel.com> (raw)
In-Reply-To: <20121027221204.GL4564@opensource.wolfsonmicro.com>
On 10/28/2012 6:12, Mark Brown wrote:
> On Mon, Oct 22, 2012 at 06:17:58PM +0800, Bo Shen wrote:
>> Covert sam9g20 wm8731 to device tree support
>> And enable it through dts file
>>
>> Tested on sam9g20 EK board
>
> This needs to add binding documentation for the board.
I will add the binding documentation in next version.
>> + dai: dai {
>> + compatible = "atmel,atmel-ssc-dai";
>> + atmel,dai-master = <&ssc0>;
>> + };
>
> This looks wrong - this is a Linux-specific virtual device sitting on
> top of the SSC which is the actual physical device. The usual patterns
> would be something like have the machine driver register the DAI based
> on the SSC specified in the bindings (much like how you're handling the
> platform already).
I have a question for this, do all nodes in dts file should be physical
device?
The SSC part is a little different with other SoC family. So, I think,
if I keep the ssc driver in driver/misc folder as the library code. And
create new code into sound/soc/atmel for ssc which used for audio, would
this be acceptable? If so, the framework will be the same with other SoC
family.
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, devicetree-discuss@lists.ozlabs.org,
nicolas.ferre@atmel.com, linux-sound@vger.kernel.org,
plagnioj@jcrosoft.com, jm.lin@atmel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/5] ASoC: sam9g20_wm8731: convert to device tree support
Date: Mon, 29 Oct 2012 06:38:17 +0000 [thread overview]
Message-ID: <508E2459.5090707@atmel.com> (raw)
In-Reply-To: <20121027221204.GL4564@opensource.wolfsonmicro.com>
On 10/28/2012 6:12, Mark Brown wrote:
> On Mon, Oct 22, 2012 at 06:17:58PM +0800, Bo Shen wrote:
>> Covert sam9g20 wm8731 to device tree support
>> And enable it through dts file
>>
>> Tested on sam9g20 EK board
>
> This needs to add binding documentation for the board.
I will add the binding documentation in next version.
>> + dai: dai {
>> + compatible = "atmel,atmel-ssc-dai";
>> + atmel,dai-master = <&ssc0>;
>> + };
>
> This looks wrong - this is a Linux-specific virtual device sitting on
> top of the SSC which is the actual physical device. The usual patterns
> would be something like have the machine driver register the DAI based
> on the SSC specified in the bindings (much like how you're handling the
> platform already).
I have a question for this, do all nodes in dts file should be physical
device?
The SSC part is a little different with other SoC family. So, I think,
if I keep the ssc driver in driver/misc folder as the library code. And
create new code into sound/soc/atmel for ssc which used for audio, would
this be acceptable? If so, the framework will be the same with other SoC
family.
WARNING: multiple messages have this Message-ID (diff)
From: voice.shen@atmel.com (Bo Shen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ASoC: sam9g20_wm8731: convert to device tree support
Date: Mon, 29 Oct 2012 14:38:17 +0800 [thread overview]
Message-ID: <508E2459.5090707@atmel.com> (raw)
In-Reply-To: <20121027221204.GL4564@opensource.wolfsonmicro.com>
On 10/28/2012 6:12, Mark Brown wrote:
> On Mon, Oct 22, 2012 at 06:17:58PM +0800, Bo Shen wrote:
>> Covert sam9g20 wm8731 to device tree support
>> And enable it through dts file
>>
>> Tested on sam9g20 EK board
>
> This needs to add binding documentation for the board.
I will add the binding documentation in next version.
>> + dai: dai {
>> + compatible = "atmel,atmel-ssc-dai";
>> + atmel,dai-master = <&ssc0>;
>> + };
>
> This looks wrong - this is a Linux-specific virtual device sitting on
> top of the SSC which is the actual physical device. The usual patterns
> would be something like have the machine driver register the DAI based
> on the SSC specified in the bindings (much like how you're handling the
> platform already).
I have a question for this, do all nodes in dts file should be physical
device?
The SSC part is a little different with other SoC family. So, I think,
if I keep the ssc driver in driver/misc folder as the library code. And
create new code into sound/soc/atmel for ssc which used for audio, would
this be acceptable? If so, the framework will be the same with other SoC
family.
next prev parent reply other threads:[~2012-10-29 6:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 10:17 [PATCH 1/5] ARM: at91: atmel-ssc: add platform device id table Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` [PATCH 2/5] ARM: at91: atmel-ssc: add device tree support Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-30 17:13 ` Nicolas Ferre
2012-10-30 17:13 ` Nicolas Ferre
2012-10-30 17:13 ` Nicolas Ferre
2012-10-22 10:17 ` [PATCH 3/5] ASoC: atmel-ssc-dai: register 'platform' from DAIs Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` [PATCH 4/5] ASoC: sam9g20_wm8731: convert to device tree support Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-27 22:12 ` Mark Brown
2012-10-27 22:12 ` Mark Brown
2012-10-27 22:12 ` Mark Brown
2012-10-29 6:38 ` Bo Shen [this message]
2012-10-29 6:38 ` Bo Shen
2012-10-29 6:38 ` Bo Shen
2012-10-22 10:17 ` [PATCH 5/5] ASoC: sam9g20_wm8731: fix the issue for non-DT kernel Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-22 10:17 ` Bo Shen
2012-10-27 22:14 ` Mark Brown
2012-10-27 22:14 ` Mark Brown
2012-10-27 22:14 ` Mark Brown
2012-10-29 6:15 ` Bo Shen
2012-10-29 6:15 ` Bo Shen
2012-10-29 6:15 ` Bo Shen
2012-10-30 16:07 ` [PATCH 1/5] ARM: at91: atmel-ssc: add platform device id table Mark Brown
2012-10-30 16:07 ` Mark Brown
2012-10-30 17:14 ` Nicolas Ferre
2012-10-30 17:14 ` Nicolas Ferre
2012-10-30 17:14 ` Nicolas Ferre
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=508E2459.5090707@atmel.com \
--to=voice.shen@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jm.lin@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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.