From: Sameer Pujar <spujar@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
broonie@kernel.org, lgirdwood@gmail.com, robh+dt@kernel.org,
krzk+dt@kernel.org, perex@perex.cz, tiwai@suse.com,
peter.ujfalusi@linux.intel.com,
pierre-louis.bossart@linux.intel.com
Cc: oder_chiou@realtek.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/6] ASoC: dt-bindings: Add audio-graph-port bindings to rt5659
Date: Mon, 28 Mar 2022 13:28:58 +0530 [thread overview]
Message-ID: <ffe25a55-944a-7912-5cfb-a28a80c97703@nvidia.com> (raw)
In-Reply-To: <95cb1ea9-a737-7d01-f81f-f94ea92c7a4d@kernel.org>
On 28-03-2022 12:33, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
>
>
> On 28/03/2022 08:14, Sameer Pujar wrote:
>> To use rt5658 or rt5659 audio CODEC with generic audio-graph-card machine
>> driver, the CODEC requires "port" bindings. Thus add "audio-graph-port"
>> reference to the rt5659 binding.
>>
>> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
>> Cc: Oder Chiou <oder_chiou@realtek.com>
>> ---
>> Documentation/devicetree/bindings/sound/realtek,rt5659.yaml | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
> This should be squashed with your previous patch, otherwise that one is
> not a complete conversion.
>
OK. I will squash this. Thanks.
next prev parent reply other threads:[~2022-03-28 7:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 6:14 [RFC PATCH v2 0/6] Flexible codec clock configuration Sameer Pujar
2022-03-28 6:14 ` [RFC PATCH v2 1/6] ASoC: dt-bindings: Convert rt5659 bindings to YAML schema Sameer Pujar
2022-03-28 7:02 ` Krzysztof Kozlowski
2022-03-28 12:51 ` Rob Herring
2022-03-28 13:26 ` Sameer Pujar
2022-03-28 6:14 ` [RFC PATCH v2 2/6] ASoC: dt-bindings: Add audio-graph-port bindings to rt5659 Sameer Pujar
2022-03-28 7:03 ` Krzysztof Kozlowski
2022-03-28 7:58 ` Sameer Pujar [this message]
2022-03-28 6:14 ` [RFC PATCH v2 3/6] ASoC: dt-bindings: Extend clock bindings of rt5659 Sameer Pujar
2022-03-28 7:06 ` Krzysztof Kozlowski
2022-03-28 7:58 ` Sameer Pujar
2022-03-28 8:07 ` Krzysztof Kozlowski
2022-03-28 13:19 ` Sameer Pujar
2022-03-28 13:28 ` Krzysztof Kozlowski
2022-03-29 8:27 ` Sameer Pujar
2022-03-28 6:14 ` [RFC PATCH v2 4/6] ASoC: soc-pcm: tweak DPCM BE hw_param() call order Sameer Pujar
2022-03-28 15:11 ` Amadeusz Sławiński
2022-03-29 8:28 ` Sameer Pujar
2022-03-28 15:29 ` Ranjani Sridharan
2022-03-29 8:31 ` Sameer Pujar
2022-03-28 6:14 ` [RFC PATCH v2 5/6] ASoC: rt5659: Expose internal clock relationships Sameer Pujar
2022-03-28 6:14 ` [RFC PATCH v2 6/6] ASoC: tegra: Get clock rate in consumer mode Sameer Pujar
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=ffe25a55-944a-7912-5cfb-a28a80c97703@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--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).