From: Marek Vasut <marex@nabladev.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: sashiko-reviews@lists.linux.dev, Frank.Li@kernel.org,
imx@lists.linux.dev, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Fri, 31 Jul 2026 17:56:19 +0200 [thread overview]
Message-ID: <a5bab69f-22db-46f4-a039-cc20fe428abf@nabladev.com> (raw)
In-Reply-To: <amy96HmlzdtBz4nl@SMW015318>
On 7/31/26 5:23 PM, Frank Li wrote:
Hello Frank,
>>> at imx8mm.dts, 30050000 is SAI5, here you change to to use clock-controller
>>>
>>> Suppose address here is wrong.
>> This is correct and we already discussed this in V4, the SAI here is not
>> used as an audio controller (not using sound/soc/fsl/fsl_sai.c driver), but
>> as a clock controller (yes using drivers/clk/clk-fsl-sai.c driver), the
>> bindings differ, hence this node.
>
> Thanks, I forget it. Now, may not allow this method. The same hardware
> have to use one compatible string.
This was already discussed at length when the drivers/clk/clk-fsl-sai.c
was upstreamed, it is clear the two drivers are not ideal. The rationale
for having two separate drivers, one for SAI as audio device and one for
SAI as clock controller, with separate compatible strings, is to make
sound/soc/fsl/fsl_sai.c maintainable. The sound/soc/fsl/fsl_sai.c is
already complex enough and folding a clock driver into it would make it
difficult to maintain, hence the separate clock driver.
prev parent reply other threads:[~2026-07-31 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:47 [PATCH v7 1/7] arm64: dts: imx8mp: Add DT label to SPBA5 bus Marek Vasut
2026-07-29 21:47 ` [PATCH v7 2/7] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-07-29 22:06 ` sashiko-bot
2026-07-30 15:31 ` Frank Li
2026-07-30 19:14 ` Marek Vasut
2026-07-29 21:47 ` [PATCH v7 3/7] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-07-29 21:47 ` [PATCH v7 4/7] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-07-29 21:47 ` [PATCH v7 5/7] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-07-29 21:47 ` [PATCH v7 6/7] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-07-29 21:47 ` [PATCH v7 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-07-29 22:10 ` sashiko-bot
2026-07-30 15:17 ` Frank Li
2026-07-30 19:34 ` Marek Vasut
2026-07-31 15:23 ` Frank Li
2026-07-31 15:56 ` Marek Vasut [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=a5bab69f-22db-46f4-a039-cc20fe428abf@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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