All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: nicolas.ferre@atmel.com, linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
	alsa-devel@alsa-project.org, plagnioj@jcrosoft.com,
	jm.lin@atmel.com
Subject: Re: [Patch v2 3/4] ASoC: atmel-ssc-dai: register platform from DAIs
Date: Tue, 6 Nov 2012 09:53:09 +0100	[thread overview]
Message-ID: <20121106085309.GD5044@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5098A280.7070301@atmel.com>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Tue, Nov 06, 2012 at 01:39:12PM +0800, Bo Shen wrote:
> On 11/5/2012 13:25, Bo Shen wrote:

Note that there's less than 24 hours between these two mails...

> >Sorry for misunderstand. I split your e-mail into two parts. May be you
> >miss some parts of my e-mail. You can check the last mail from me. Or
> >check the following fully quote.

> Anyway, I will sent out a RFC patch series (which will be v3) which
> register dai and platform directly in Linux.

> > > This seems to be a purely virtual device which remaps the SSC onto the
> > > Linux audio subsystem?  If that is the case then it shouldn't appear in
> > > the device tree,

> >Yes. This is a purely virtual device. I add this as to the following
> >reason.

> >In our case, the ssc can connect to audio codec, DAC and other devices.
> >In order to avoid duplicate the code, so keep ssc as a library, register
> >it directly in Linux and use remap method to let it work onto other
> >different subsystem.

The whole point here is that this remapping shouldn't appear in the
device tree since it's a purely Linux internal issue, the code that uses
the SSC should have a reference to the SSC and then do whatever
remapping is required.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: nicolas.ferre@atmel.com, linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
	alsa-devel@alsa-project.org, plagnioj@jcrosoft.com,
	jm.lin@atmel.com
Subject: Re: [Patch v2 3/4] ASoC: atmel-ssc-dai: register platform from DAIs
Date: Tue, 06 Nov 2012 08:53:09 +0000	[thread overview]
Message-ID: <20121106085309.GD5044@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5098A280.7070301@atmel.com>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

On Tue, Nov 06, 2012 at 01:39:12PM +0800, Bo Shen wrote:
> On 11/5/2012 13:25, Bo Shen wrote:

Note that there's less than 24 hours between these two mails...

> >Sorry for misunderstand. I split your e-mail into two parts. May be you
> >miss some parts of my e-mail. You can check the last mail from me. Or
> >check the following fully quote.

> Anyway, I will sent out a RFC patch series (which will be v3) which
> register dai and platform directly in Linux.

> > > This seems to be a purely virtual device which remaps the SSC onto the
> > > Linux audio subsystem?  If that is the case then it shouldn't appear in
> > > the device tree,

> >Yes. This is a purely virtual device. I add this as to the following
> >reason.

> >In our case, the ssc can connect to audio codec, DAC and other devices.
> >In order to avoid duplicate the code, so keep ssc as a library, register
> >it directly in Linux and use remap method to let it work onto other
> >different subsystem.

The whole point here is that this remapping shouldn't appear in the
device tree since it's a purely Linux internal issue, the code that uses
the SSC should have a reference to the SSC and then do whatever
remapping is required.

[-- 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: [Patch v2 3/4] ASoC: atmel-ssc-dai: register platform from DAIs
Date: Tue, 6 Nov 2012 09:53:09 +0100	[thread overview]
Message-ID: <20121106085309.GD5044@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5098A280.7070301@atmel.com>

On Tue, Nov 06, 2012 at 01:39:12PM +0800, Bo Shen wrote:
> On 11/5/2012 13:25, Bo Shen wrote:

Note that there's less than 24 hours between these two mails...

> >Sorry for misunderstand. I split your e-mail into two parts. May be you
> >miss some parts of my e-mail. You can check the last mail from me. Or
> >check the following fully quote.

> Anyway, I will sent out a RFC patch series (which will be v3) which
> register dai and platform directly in Linux.

> > > This seems to be a purely virtual device which remaps the SSC onto the
> > > Linux audio subsystem?  If that is the case then it shouldn't appear in
> > > the device tree,

> >Yes. This is a purely virtual device. I add this as to the following
> >reason.

> >In our case, the ssc can connect to audio codec, DAC and other devices.
> >In order to avoid duplicate the code, so keep ssc as a library, register
> >it directly in Linux and use remap method to let it work onto other
> >different subsystem.

The whole point here is that this remapping shouldn't appear in the
device tree since it's a purely Linux internal issue, the code that uses
the SSC should have a reference to the SSC and then do whatever
remapping is required.
-------------- 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/20121106/b4fff9ac/attachment.sig>

  reply	other threads:[~2012-11-06  8:53 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  7:26 [Patch v2 1/4] ARM: at91: atmel-ssc: add platform device id table Bo Shen
2012-10-31  7:26 ` Bo Shen
2012-10-31  7:26 ` Bo Shen
2012-10-31  7:26 ` [Patch v2 2/4] ARM: at91: atmel-ssc: add device tree support Bo Shen
2012-10-31  7:26   ` Bo Shen
2012-10-31  7:26   ` Bo Shen
2012-10-31  8:39   ` Nicolas Ferre
2012-10-31  9:39     ` Nicolas Ferre
2012-10-31  9:39     ` Nicolas Ferre
2012-10-31  7:26 ` [Patch v2 3/4] ASoC: atmel-ssc-dai: register platform from DAIs Bo Shen
2012-10-31  7:26   ` Bo Shen
2012-10-31  7:26   ` Bo Shen
2012-10-31  8:41   ` Nicolas Ferre
2012-10-31  9:41     ` Nicolas Ferre
2012-10-31  9:41     ` Nicolas Ferre
2012-11-01 14:43   ` Mark Brown
2012-11-01 14:43     ` Mark Brown
2012-11-01 14:43     ` Mark Brown
2012-11-02  2:34     ` Bo Shen
2012-11-02  2:34       ` Bo Shen
2012-11-02  2:34       ` Bo Shen
2012-11-02 14:24       ` Mark Brown
2012-11-02 14:24         ` Mark Brown
2012-11-02 14:24         ` Mark Brown
2012-11-05  5:25         ` Bo Shen
2012-11-05  5:25           ` Bo Shen
2012-11-05  5:25           ` Bo Shen
2012-11-06  5:39           ` Bo Shen
2012-11-06  5:39             ` Bo Shen
2012-11-06  5:39             ` Bo Shen
2012-11-06  8:53             ` Mark Brown [this message]
2012-11-06  8:53               ` Mark Brown
2012-11-06  8:53               ` Mark Brown
2012-10-31  7:27 ` [Patch v2 4/4] ASoC: sam9g20-wm8731: convert to device tree support Bo Shen
2012-10-31  7:27   ` Bo Shen
2012-10-31  7:27   ` Bo Shen
2012-10-31  8:42   ` Nicolas Ferre
2012-10-31  9:42     ` Nicolas Ferre
2012-10-31  9:42     ` Nicolas Ferre
2012-10-31  8:38 ` [Patch v2 1/4] ARM: at91: atmel-ssc: add platform device id table Nicolas Ferre
2012-10-31  9:38   ` Nicolas Ferre
2012-10-31  9:38   ` 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=20121106085309.GD5044@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --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 \
    --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.