From: Jiaxin Yu <jiaxin.yu@mediatek.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: <broonie@kernel.org>, <robh+dt@kernel.org>,
<angelogioacchino.delregno@collabora.com>, <aaronyu@google.com>,
<matthias.bgg@gmail.com>, <trevor.wu@mediatek.com>,
<linmq006@gmail.com>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [v6 1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties
Date: Thu, 24 Mar 2022 13:31:04 +0800 [thread overview]
Message-ID: <6c331bb8e95aa7c1a88a6161622f51ff2fee3f98.camel@mediatek.com> (raw)
In-Reply-To: <YjvBLf/8M1WUS/L+@google.com>
On Thu, 2022-03-24 at 08:54 +0800, Tzung-Bi Shih wrote:
> On Thu, Mar 24, 2022 at 12:44:39AM +0800, Jiaxin Yu wrote:
> > + speaker-codec:
>
> If it is possible to have 1 or more items, would "speaker-codecs" be
> a better
> name?
Hi Tzung-Bi,
Yes, it is better to use "speaker-codecs", I will change it that in
driver patch and bindings patch.
Jiaxin.Yu
Thanks
>
> > + type: object
> > + properties:
> > + sound-dai:
> > + minItems: 2
>
> It should be 1. Consider of rt1015p case.
Yes, I will correct it.
next prev parent reply other threads:[~2022-03-24 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:44 [v6 0/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Jiaxin Yu
2022-03-23 16:44 ` [v6 1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties Jiaxin Yu
2022-03-24 0:54 ` Tzung-Bi Shih
2022-03-24 5:31 ` Jiaxin Yu [this message]
2022-03-23 16:44 ` [v6 2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker Jiaxin Yu
2022-03-24 0:56 ` Tzung-Bi Shih
2022-03-23 16:44 ` [v6 3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset Jiaxin Yu
2022-03-24 0:57 ` Tzung-Bi Shih
2022-03-23 16:44 ` [v6 4/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Jiaxin Yu
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=6c331bb8e95aa7c1a88a6161622f51ff2fee3f98.camel@mediatek.com \
--to=jiaxin.yu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=aaronyu@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=trevor.wu@mediatek.com \
--cc=tzungbi@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
all inboxes | Powered by JetHome®