From: "Maso Huang (黃加竹)" <Maso.Huang@mediatek.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"Trevor Wu (吳文良)" <Trevor.Wu@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
"renzhijie2@huawei.com" <renzhijie2@huawei.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"perex@perex.cz" <perex@perex.cz>,
"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>
Subject: Re: [PATCH 7/7] ASoC: dt-bindings: mediatek,mt79xx-afe: add audio afe document
Date: Thu, 15 Jun 2023 02:26:57 +0000 [thread overview]
Message-ID: <0e440369465369421f64ce00ee83b46b23c358de.camel@mediatek.com> (raw)
In-Reply-To: <645989de-7a61-29e7-9cf8-f473b9b384fe@kernel.org>
On Wed, 2023-06-14 at 12:26 +0200, Krzysztof Kozlowski wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On 14/06/2023 11:19, Maso Huang (黃加竹) wrote:
> > On Wed, 2023-06-14 at 10:21 +0200, Krzysztof Kozlowski wrote:
> >>
> >> External email : Please do not click links or open attachments
> until
> >> you have verified the sender or the content.
> >> On 14/06/2023 09:37, Maso Huang (黃加竹) wrote:
> >>>>>> I already saw AFE, why it cannot be part of existing bindings?
> >>>>
> >>>> Can you answer this?
> >>>>
> >>>
> >>> Did you mean mtk-afe-pcm.txt?
> >>> If yes, I'll modify mtk-afe-pcm.txt to yaml format, and add
> mt7986
> >> to
> >>> its compatible list.
> >>>
> >>
> >> No, I meant mediatek,mt8188-afe.yaml.
> >>
> >> Aren't you working on some old tree? If so, please don't...
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >
> > Hi Krzysztof,
> > AFE is common name for our audio hardware, and the design might be
> > different for soc, like clock.
> >
> > And the design is the same for mt7981/mt7986/mt7988.
> > Is it better to create a new dtbinding file mediatk,mt7986-
> afe.yaml?
>
> Is it different? That was my question whether it can be part of
> existing
> bindings.
>
> Best regards,
> Krzysztof
Yes, the design is different, I'm afraid that it would be hard to be
part of mt8188 bindings.
Best regards,
Maso
prev parent reply other threads:[~2023-06-15 2:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 10:52 [PATCH 0/7] ASoC: mediatek: Add support for MT79xx SoC Maso Hunag
2023-06-12 10:52 ` [PATCH 1/7] ASoC: mediatek: mt79xx: add common header Maso Hunag
2023-06-14 7:44 ` AngeloGioacchino Del Regno
2023-06-14 7:52 ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 2/7] ASoC: mediatek: mt79xx: support audio clock control Maso Hunag
2023-06-13 7:27 ` Claudiu.Beznea
2023-06-14 7:44 ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 3/7] ASoC: mediatek: mt79xx: add platform driver Maso Hunag
2023-06-14 7:57 ` AngeloGioacchino Del Regno
2023-06-14 9:06 ` Maso Huang (黃加竹)
2023-06-14 12:21 ` kernel test robot
2023-06-12 10:52 ` [PATCH 4/7] ASoC: mediatek: mt79xx: support etdm in " Maso Hunag
2023-06-12 10:52 ` [PATCH 5/7] ASoC: mediatek: mt79xx: add machine driver with wm8960 Maso Hunag
2023-06-12 10:52 ` [PATCH 6/7] ASoC: dt-bindings: mediatek,mt79xx-wm8960: add mt79xx-wm8960 document Maso Hunag
2023-06-13 8:49 ` Krzysztof Kozlowski
2023-06-14 7:40 ` Maso Huang (黃加竹)
2023-06-14 8:22 ` Krzysztof Kozlowski
2023-06-14 8:45 ` Maso Huang (黃加竹)
2023-06-12 10:52 ` [PATCH 7/7] ASoC: dt-bindings: mediatek,mt79xx-afe: add audio afe document Maso Hunag
2023-06-13 8:51 ` Krzysztof Kozlowski
2023-06-14 3:17 ` Maso Huang (黃加竹)
2023-06-14 6:34 ` Krzysztof Kozlowski
2023-06-14 7:37 ` Maso Huang (黃加竹)
2023-06-14 8:21 ` Krzysztof Kozlowski
2023-06-14 9:19 ` Maso Huang (黃加竹)
2023-06-14 10:26 ` Krzysztof Kozlowski
2023-06-15 2:26 ` Maso Huang (黃加竹) [this message]
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=0e440369465369421f64ce00ee83b46b23c358de.camel@mediatek.com \
--to=maso.huang@mediatek.com \
--cc=Allen-KH.Cheng@mediatek.com \
--cc=Jiaxin.Yu@mediatek.com \
--cc=Trevor.Wu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=perex@perex.cz \
--cc=renzhijie2@huawei.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).