Linux-Devicetree Archive on lore.kernel.org
 help / color / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Daniel Baluta <daniel.baluta@nxp.com>
Cc: perex@perex.cz, tiwai@suse.com, kuninori.morimoto.gx@renesas.com,
	lgirdwood@gmail.com, robh+dt@kernel.org,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [RFC PATCH 2/2] ASoC: simple-card: Add documentation for force-dpcm property
Date: Mon, 14 Oct 2019 12:56:35 +0100
Message-ID: <20191014115635.GB4826@sirena.co.uk> (raw)
In-Reply-To: <20191013190014.32138-3-daniel.baluta@nxp.com>

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

On Sun, Oct 13, 2019 at 10:00:14PM +0300, Daniel Baluta wrote:

> This property can be global in which case all links created will be DPCM
> or present in certian dai-link subnode in which case only that specific
> link is forced to be DPCM.

> +- force-dpcm				: Indicates dai-link is always DPCM.

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply index

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 [this message]
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

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=20191014115635.GB4826@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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

Linux-Devicetree Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-devicetree/0 linux-devicetree/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-devicetree linux-devicetree/ https://lore.kernel.org/linux-devicetree \
		devicetree@vger.kernel.org
	public-inbox-index linux-devicetree

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-devicetree


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git