devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	bard.liao@intel.com, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/4] dt-bindings: audio-graph-port: add ch-maps property
Date: Wed, 18 Oct 2023 08:57:17 +0100	[thread overview]
Message-ID: <20231018-object-renewable-6e03bce41ff4@spud> (raw)
In-Reply-To: <871qdskbuu.wl-kuninori.morimoto.gx@renesas.com>

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

On Wed, Oct 18, 2023 at 12:34:01AM +0000, Kuninori Morimoto wrote:
> 
> Hi Conor
> 
> > That seems like a very unintuitive interface. If there were 32 CPUs and
> > 30 codecs, then it'd be very inconvenient for a human reader to grok the
> > configuration.
> 
> I don't think such huge number connection will be used...

Your binding allows for that though!
I really don't like the number of elements inverting the meaning of the
property.

Also, this was not the only item in my mail. Why did you not respond to
the other comments?

Cheers,
Conor.

> Thank you for your help !!
> 
> Best regards
> ---
> Kuninori Morimoto

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

  reply	other threads:[~2023-10-18  7:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  1:31 [PATCH v3 0/4] ASoC: makes CPU/Codec channel connection map more generic Kuninori Morimoto
2023-10-12  1:31 ` [PATCH v3 1/4] " Kuninori Morimoto
2023-10-12  1:32 ` [PATCH v3 2/4] ASoC: audio-graph-card2: add CPU:Codec = N:M support Kuninori Morimoto
2023-10-12  1:32 ` [PATCH v3 3/4] ASoC: audio-graph-card2-custom-sample: add CPU/Codec = N:M sample Kuninori Morimoto
2023-10-12  1:32 ` [PATCH v3 4/4] dt-bindings: audio-graph-port: add ch-maps property Kuninori Morimoto
2023-10-12  7:53   ` Conor Dooley
2023-10-13  0:33     ` Kuninori Morimoto
2023-10-13 15:41       ` Mark Brown
2023-10-13 16:12         ` Conor Dooley
2023-10-16  0:46           ` Kuninori Morimoto
2023-10-17 10:04             ` Conor Dooley
2023-10-18  0:34               ` Kuninori Morimoto
2023-10-18  7:57                 ` Conor Dooley [this message]
2023-10-18 18:25                   ` Mark Brown
2023-10-20  1:13                     ` Kuninori Morimoto
2023-10-20 11:58                       ` Mark Brown
2023-10-23  0:08                         ` 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=20231018-object-renewable-6e03bce41ff4@spud \
    --to=conor@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=robh+dt@kernel.org \
    --cc=yung-chuan.liao@linux.intel.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).