alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: simle-card DT style for DPCM
Date: Tue, 02 Sep 2014 17:11:22 -0700 (PDT)	[thread overview]
Message-ID: <87fvg97ecd.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <20140902113407.GV29327@sirena.org.uk>


Hi Mark

> > This means BE don't know who is FE.
> > The implementation can be more easy if it has
> > connect-to / connect-from property
> > (I'm not sure this is good naming...)
> 
> We don't need to get this from DT if it's fixed in the SoC - the driver
> for the SoC can know this.  The whole front end/back end thing is a bit
> of a Linuxism.

Yes, FE/BE is very Linuxism, and I know DT shouldn't have Linuxism property.
But, "connect" or "remote" is normal in DT ?

> the driver for the SoC can know this.

I wonder how to know it in driver ?
(How to switch normal <-> FE/BE ?, and how to know FE or BE ?)
Can you show me objectivization example / idea ?

Best regards
---
Kuninori Morimoto

  reply	other threads:[~2014-09-03  0:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01  0:35 simle-card DT style for DPCM Kuninori Morimoto
2014-09-01 14:30 ` Mark Brown
2014-09-02  1:28   ` Kuninori Morimoto
2014-09-02 11:34     ` Mark Brown
2014-09-03  0:11       ` Kuninori Morimoto [this message]
2014-09-05 15:55         ` Mark Brown
2014-09-08  0:20           ` Kuninori Morimoto
2014-09-08  7:39             ` Lars-Peter Clausen
2014-09-08  8:50               ` Kuninori Morimoto
2014-09-09 11:51                 ` Mark Brown
2014-09-10  0:18                   ` Kuninori Morimoto
2014-09-03  5:17   ` Kuninori Morimoto

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=87fvg97ecd.wl%kuninori.morimoto.gx@gmail.com \
    --to=kuninori.morimoto.gx@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).