From: "Hailong Fan (范海龙)" <Hailong.Fan@mediatek.com>
To: "perex@perex.cz" <perex@perex.cz>,
"krzk@kernel.org" <krzk@kernel.org>,
"pierre-louis.bossart@linux.dev" <pierre-louis.bossart@linux.dev>,
"kai.vehmanen@linux.intel.com" <kai.vehmanen@linux.intel.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"robh@kernel.org" <robh@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"peter.ujfalusi@linux.intel.com" <peter.ujfalusi@linux.intel.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"daniel.baluta@nxp.com" <daniel.baluta@nxp.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"ranjani.sridharan@linux.intel.com"
<ranjani.sridharan@linux.intel.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"sound-open-firmware@alsa-project.org"
<sound-open-firmware@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: dsp: mediatek: add mt8196 dsp document
Date: Wed, 9 Jul 2025 06:34:40 +0000 [thread overview]
Message-ID: <85ca4ceb29caec9acbe77a3d67e3bc57b0b0aeb5.camel@mediatek.com> (raw)
In-Reply-To: <61784658-c71d-458b-8934-5f5db2330bc0@collabora.com>
On Thu, 2025-07-03 at 11:05 +0200, AngeloGioacchino Del Regno wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Il 03/07/25 10:08, Krzysztof Kozlowski ha scritto:
> > On 03/07/2025 09:56, hailong.fan wrote:
> > > From: Hailong Fan <hailong.fan@mediatek.com>
> > >
> > > This patch adds mt8196 dsp document. The dsp is used for Sound
> > > Open
> >
> > Please do not use "This commit/patch/change", but imperative mood.
> > See
> > longer explanation here:
> >
https://urldefense.com/v3/__https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst*L95__;Iw!!CTRNKA9wMg0ARbw!g39q48fUCsDJ5PETUtQ0PK0Bkwf0Ce1F_ZzJiEiWMzuybWQ0dSPzblvLlJ-4saWTSoJWuS5imsXbpdgLBvUy4wxw9C5w7B4m$
> >
> > > Firmware driver node. It includes registers, clocks, memory
> > > regions,
> > > and mailbox for dsp.
> > >
> > > Signed-off-by: Hailong Fan <hailong.fan@mediatek.com>
> > > ---
> > > .../bindings/sound/mediatek,mt8196-dsp.yaml | 95
> > > +++++++++++++++++++
> > > 1 file changed, 95 insertions(+)
> > > create mode 100644
> > > Documentation/devicetree/bindings/sound/mediatek,mt8196-dsp.yaml
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/sound/mediatek,mt8196-
> > > dsp.yaml
> > > b/Documentation/devicetree/bindings/sound/mediatek,mt8196-
> > > dsp.yaml
> > > new file mode 100644
> > > index 000000000000..68f594f476e8
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/sound/mediatek,mt8196-
> > > dsp.yaml
>
> Wrong folder; this should go to dsp/mediatek,mt8196-dsp.yaml ....
>
> ...but then I don't get why MT8196 wasn't simply added to
> mediatek,mt8186-dsp.yaml.
>
Yes, the first version was written this way, but the maintainer
suggested the following, so I'm not sure which approach is more
appropriate. Could you please provide a final recommendation?
v1 link:
https://lore.kernel.org/all/a72988212d0d95bfe76eb9c53bbdb8c57c989377.camel@mediatek.com/
comment:
>
> > ---
> > .../bindings/dsp/mediatek,mt8196-dsp.yaml | 96
> > +++++++++++++++++++
>
> Don't grow dsp directory. Either this is remoteproc or some sound
> component, so place it accordingly.
This is a reference to the approach used in a previous MediaTek
project:
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/dsp
Do we need to move all the files under the DSP directory to the sound
directory?
> > > @@ -0,0 +1,95 @@
> > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id:
> > > https://urldefense.com/v3/__http://devicetree.org/schemas/sound/mediatek,mt8196-dsp.yaml*__;Iw!!CTRNKA9wMg0ARbw!g39q48fUCsDJ5PETUtQ0PK0Bkwf0Ce1F_ZzJiEiWMzuybWQ0dSPzblvLlJ-4saWTSoJWuS5imsXbpdgLBvUy4wxw9GN4ryBQ$
> > > +$schema:
> > > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!g39q48fUCsDJ5PETUtQ0PK0Bkwf0Ce1F_ZzJiEiWMzuybWQ0dSPzblvLlJ-4saWTSoJWuS5imsXbpdgLBvUy4wxw9NKbMuhN$
> > > +
> > > +title: MediaTek mt8196 DSP core
> > > +
> > > +maintainers:
> > > + - Hailong Fan <hailong.fan@mediatek.com>
> > > +
> > > +description: The MediaTek mt8196 SoC mt8196 contain a DSP core
> > > used for advanced
> >
> > Missing blank line. Look at other bindings. Also does not look
> > wrapped
> > at 80 (see Linux coding style doc).
> >
>
> There's also a typo, "mt8196 SoC mt8196"
>
Will update in next version, thanks.
> >
> > > + pre- and post- audio processing.
> > > +
> > > +properties:
> > > + compatible:
> > > + const: mediatek,mt8196-dsp
> > > +
> > > + reg:
> > > + items:
> > > + - description: DSP configuration registers
> > > + - description: DSP SRAM
> > > + - description: DSP secure registers
> > > + - description: DSP bus registers
> > > +
> > > + reg-names:
> > > + items:
> > > + - const: cfg
> > > + - const: sram
> > > + - const: sec
> > > + - const: bus
> > > +
> > > + clocks:
> > > + items:
> > > + - description: mux for dsp clock
> > > + - description: 26M clock
> > > + - description: ADSP PLL clock
> > > +
> > > + clock-names:
> > > + items:
> > > + - const: adsp_sel
> >
> > Isn't this called audiodsp in other bindings?
> >
> > > + - const: clk26m
> >
> > Don't use frequencies. How is the pin or input called in datasheet?
> > How
> > other devices call it?
>
> In the datasheet, this is called.... CLK26M (really).
>
> Cheers,
> Angelo
>
> >
> > > + - const: adsppll
> > > +
> > > + power-domains:
> > > + maxItems: 1
> > > +
> >
> > Best regards,
> > Krzysztof
>
>
next prev parent reply other threads:[~2025-07-09 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 7:56 [PATCH v2 0/2] ASoC: mediatek: Add support of SOF on Mediatek mt8196 SoC hailong.fan
2025-07-03 7:56 ` [PATCH v2 1/2] dt-bindings: dsp: mediatek: add mt8196 dsp document hailong.fan
2025-07-03 8:08 ` Krzysztof Kozlowski
2025-07-03 9:05 ` AngeloGioacchino Del Regno
2025-07-03 10:24 ` Krzysztof Kozlowski
2025-07-09 6:05 ` Hailong Fan (范海龙)
2025-07-09 6:57 ` Krzysztof Kozlowski
2025-08-26 7:16 ` Hailong Fan (范海龙)
2025-07-09 6:34 ` Hailong Fan (范海龙) [this message]
2025-07-09 6:59 ` Krzysztof Kozlowski
2025-08-26 7:21 ` Hailong Fan (范海龙)
2025-07-09 2:52 ` Hailong Fan (范海龙)
2025-07-09 6:55 ` Krzysztof Kozlowski
2025-08-26 7:23 ` Hailong Fan (范海龙)
2025-07-03 10:19 ` Rob Herring (Arm)
2025-07-03 7:56 ` [PATCH v2 2/2] ASoC: SOF: MediaTek: Add mt8196 hardware support hailong.fan
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=85ca4ceb29caec9acbe77a3d67e3bc57b0b0aeb5.camel@mediatek.com \
--to=hailong.fan@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=robh@kernel.org \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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.