From: Sameer Pujar <spujar@nvidia.com>
To: <robh+dt@kernel.org>, <broonie@kernel.org>
Cc: <kuninori.morimoto.gx@renesas.com>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH 0/2] Refactor Audio Graph schema
Date: Wed, 11 Nov 2020 17:56:51 +0530 [thread overview]
Message-ID: <1605097613-25301-1-git-send-email-spujar@nvidia.com> (raw)
There can be custom sound cards reusing most of the audio-graph
implementation. To allow this refactor the audio-graph-card schema into
following files.
* audio-graph.yaml : defines all common bindings
* audio-graph-card.yaml : define compatible property
Custom sound cards can just reference 'audio-graph.yaml' and define its
own compatible and specific properties.
This depends on following series:
http://patchwork.ozlabs.org/project/devicetree-bindings/patch/20201102203656.220187-2-robh@kernel.org/
Sameer Pujar (2):
ASoC: audio-graph-card: Refactor schema
ASoC: renesas,rsnd: Update audio graph references
.../bindings/sound/audio-graph-card.yaml | 102 +-------------------
.../devicetree/bindings/sound/audio-graph.yaml | 107 +++++++++++++++++++++
.../devicetree/bindings/sound/renesas,rsnd.yaml | 6 +-
3 files changed, 112 insertions(+), 103 deletions(-)
create mode 100644 Documentation/devicetree/bindings/sound/audio-graph.yaml
--
2.7.4
next reply other threads:[~2020-11-11 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 12:26 Sameer Pujar [this message]
2020-11-11 12:26 ` [PATCH 1/2] ASoC: audio-graph-card: Refactor schema Sameer Pujar
2020-11-12 16:06 ` Rob Herring
2020-11-11 12:26 ` [PATCH 2/2] ASoC: renesas,rsnd: Update audio graph references Sameer Pujar
2020-11-12 16:07 ` Rob Herring
2020-11-12 16:15 ` Rob Herring
2020-11-11 23:24 ` [PATCH 0/2] Refactor Audio Graph schema 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=1605097613-25301-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).