From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Mark Brown <broonie@kernel.org>,
Devicetree List <devicetree@vger.kernel.org>,
Daniel Baluta <daniel.baluta@gmail.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Jerome Laclavere <jerome.laclavere@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Guido Roncarolo <guido.roncarolo@nxp.com>
Subject: Re: [alsa-devel] [RFC PATCH 2/2] ASoC: simple-card: Add documentation for force-dpcm property
Date: 15 Oct 2019 10:18:41 +0900 [thread overview]
Message-ID: <87mue26c26.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <87pniy6cso.wl-kuninori.morimoto.gx@renesas.com>
Hi
> > > > DPCM is an implementation detail of Linux (and one that we want to phase
> > > > out going forwards too), we shouldn't be putting it in the DT bindings
> > > > where it becomes an ABI.
> >
> > > I see your point. This is way I marked the patch series as RFC. I need to find
> > > another way to reuse simple-card as machine driver for SOF.
> >
> > Have a look at the way the Renesas systems are using this and the audio
> > graph card - they have DPCM.
>
> Indeed we (= Renesas) are using this as DPCM, but unfortunately
> it is not upstreamed. Using local patch.
I mean DT part.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2019-10-15 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 19:00 [RFC PATCH 0/2] Introduce for-dpcm DT property Daniel Baluta
2019-10-13 19:00 ` [RFC PATCH 1/2] ASoC: simple-card: Introduce force-dpcm " Daniel Baluta
2019-10-13 19:00 ` [RFC PATCH 2/2] ASoC: simple-card: Add documentation for force-dpcm property Daniel Baluta
2019-10-14 11:56 ` Mark Brown
2019-10-14 13:17 ` [alsa-devel] " Daniel Baluta
2019-10-14 16:10 ` Mark Brown
2019-10-15 1:02 ` Kuninori Morimoto
2019-10-15 1:18 ` Kuninori Morimoto [this message]
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=87mue26c26.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=guido.roncarolo@nxp.com \
--cc=jerome.laclavere@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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 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).