From: Frank Li <Frank.li@nxp.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Daniel Baluta <daniel.baluta@nxp.com>,
robh@kernel.org, krzk+dt@kernel.org, broonie@kernel.org,
shawnguo@kernel.org, conor+dt@kernel.org, peng.fan@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
lgirdwood@gmail.com, peter.ujfalusi@linux.intel.com,
linux-sound@vger.kernel.org, imx@lists.linux.dev,
Liam Girdwood <liam.r.girdwood@intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
Subject: Re: [PATCH 2/4] ASoC: SOF: imx: Add mach entry to select cs42888 topology
Date: Thu, 23 Jan 2025 10:38:39 -0500 [thread overview]
Message-ID: <Z5Jif6CjuSaXfWSA@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <CAEnQRZDcjwK39Ed00+mJw-epcUw2BV3snXsOBQ6-Mk-DXaxCdQ@mail.gmail.com>
On Thu, Jan 23, 2025 at 11:38:33AM +0200, Daniel Baluta wrote:
> On Wed, Jan 22, 2025 at 9:55 PM Frank Li <Frank.li@nxp.com> wrote:
> >
> > On Wed, Jan 22, 2025 at 06:35:42PM +0200, Daniel Baluta wrote:
> > > After commit 2b9cdef13648 ("ASoC: SOF: imx: Add devicetree support
> > > to select topologies") we select topology to be used by the board
> > > compatible string in the dts.
> >
> > I am confused. why not use "sof-imx8-cs42888.tplg" in imx8's dts instead
> > use board's compatible string "fsl,imx8qxp-mek-bb".
> >
> > More and more boards will be added in future. This file will become bigger
> > and bigger!
>
> Hi Frank,
>
> So you mean create a dts property named e.g sof-tplg-name and read the
> topology name from dts?
>
> dsp {
> firmware-name="sof-imx8.ri";
> tplg-name = "sof-imx8-cs428888.tplg";
> };
dsp {
compatible = "imx8-dsp-xxxx";
...
}
in dsp driver, map "imx8-dsp-xxxx" to "sof-imx8-cs428888.tplg" and
"sof-imx8.ri".
>
>
> This was our first approach but then we aligned with the community on
> using compatible to match
> for properties like default fw path, default tplg path, fw name, tplg name.
What's origial email thread. I think "compatible" refer to dsp node, not
to boards level compatible string.
>
> Now dts should somehow describe the hardware not the software (e.g
> tplg binary) used on that platform.
> The growing number of boards will not be a problem, each one will have
> a compatible in the dts.
Yes, but your C files will fill up meansless map code when more board
added.
>
> But the concern here is how we describe a hardware setup where we have
> a CPU board + a baseboard
> like it is the case for cs42888 codec?
>
> Our approach was that in our dts or overlay dts that describes SOF
> with cs428888 codec to put the exact
> compatible "fsl,imx8qxp-mek-bb" and match it with static vector in SOF
> driver that you see in this patch.
>
> SOF core relies on the compatible string in order to identify the
> correct tplg_filename for example.
Any application ctrl tools can link these nodes?
Frank
>
> thanks,
> Daniel.
next prev parent reply other threads:[~2025-01-23 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 16:35 [PATCH 0/4] Add SOF support for new board revisions Daniel Baluta
2025-01-22 16:35 ` [PATCH 1/4] dt-bindings: arm: imx: Add board revisions for i.MX8MP, i.MX8QM and i.MX8QXP Daniel Baluta
2025-01-24 8:25 ` Krzysztof Kozlowski
2025-01-22 16:35 ` [PATCH 2/4] ASoC: SOF: imx: Add mach entry to select cs42888 topology Daniel Baluta
2025-01-22 19:55 ` Frank Li
2025-01-23 9:38 ` Daniel Baluta
2025-01-23 15:38 ` Frank Li [this message]
2025-01-22 16:35 ` [PATCH 3/4] ASoC: SOF: imx8: Add entries for new 8QM and 8QXP revisions Daniel Baluta
2025-01-22 16:35 ` [PATCH 4/4] ASoC: SOF: imx8m: Add entry for new 8M Plus revision Daniel Baluta
2025-01-23 21:21 ` [PATCH 0/4] Add SOF support for new board revisions Mark Brown
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=Z5Jif6CjuSaXfWSA@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.mihalcea@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox