From: Mark Brown <broonie@kernel.org>
To: "Alvin Šipraga" <alvin@pqrs.dk>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] ASoC: dt-bindings: document new symmetric-clock-role flag
Date: Fri, 2 Jun 2023 12:43:51 +0100 [thread overview]
Message-ID: <3fe93662-82b0-4834-b6c3-473669c66210@sirena.org.uk> (raw)
In-Reply-To: <20230602090322.1876359-2-alvin@pqrs.dk>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Fri, Jun 02, 2023 at 11:03:18AM +0200, Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> The new flag specifies that both ends of the dai-link have the same
> clock consumer/provider role. This should be used to describe hardware
> where e.g. the CPU and codec both receive their bit- and frame-clocks
> from an external source.
Why would we have a property for this and not just describe whatever the
actual clocking arrangement is?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-02 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 9:03 [PATCH 0/4] ASoC: support dai-links with symmetric clock roles Alvin Šipraga
2023-06-02 9:03 ` [PATCH 1/4] ASoC: dt-bindings: document new symmetric-clock-role flag Alvin Šipraga
2023-06-02 10:13 ` Rob Herring
2023-06-02 11:43 ` Mark Brown [this message]
2023-06-02 12:12 ` Alvin Šipraga
2023-06-02 12:19 ` Mark Brown
2023-06-02 12:42 ` Alvin Šipraga
2023-06-06 14:39 ` Mark Brown
2023-06-05 11:42 ` Alvin Šipraga
2023-06-02 9:03 ` [PATCH 2/4] ASoC: core: add support for dai-links with symmetric clock roles Alvin Šipraga
2023-06-02 9:03 ` [PATCH 3/4] ASoC: audio-graph-card2: parse symmetric-clock-roles property Alvin Šipraga
2023-06-05 0:35 ` Kuninori Morimoto
2023-06-05 10:58 ` Alvin Šipraga
2023-06-02 9:03 ` [PATCH 4/4] ASoC: simple-card: " Alvin Šipraga
2023-06-05 0:28 ` Kuninori Morimoto
2023-06-05 11:12 ` Alvin Šipraga
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=3fe93662-82b0-4834-b6c3-473669c66210@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=alsi@bang-olufsen.dk \
--cc=alvin@pqrs.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.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
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.