From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Jacky Bai <ping.bai@nxp.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Frank Li <Frank.Li@nxp.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Alice Guo <alice.guo@nxp.com>
Subject: Re: [PATCH v6 2/4] thermal: qoriq: add i.MX93 tmu support
Date: Wed, 6 May 2026 18:17:35 +0200 [thread overview]
Message-ID: <2e9dd9fc-a42b-40ea-8393-3bf66955c4f2@oss.qualcomm.com> (raw)
In-Reply-To: <20260430-imx93_tmu-v6-2-485459d7b54f@nxp.com>
On 4/30/26 04:53, Jacky Bai wrote:
> For Thermal monitor unit(TMU) used on i.MX93, the HW revision info read
> from the ID register is the same the one used on some of the QorIQ
> platform, but the config has some slight differance. Add i.MX93 compatible
> string and corresponding code for it.
>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Signed-off-by: Jacky Bai <ping.bai@nxp.com>
> ---
[ ... ]
> + data->drvdata = of_device_get_match_data(&pdev->dev);
> + if (!data->drvdata)
> + return dev_err_probe(dev, -EINVAL, "Failed to get match data\n");
I'm not sure testing the return value is something very accurate because
it is like the code is testing itself as everything is self-encapsulated
in the driver.
> +
[ ... ]
> static const struct of_device_id qoriq_tmu_match[] = {
> - { .compatible = "fsl,qoriq-tmu", },
> - { .compatible = "fsl,imx8mq-tmu", },
> + { .compatible = "fsl,qoriq-tmu", .data = &qoriq_tmu_data },
> + { .compatible = "fsl,imx8mq-tmu", .data = &imx8mq_tmu_data },
> + { .compatible = "fsl,imx93-tmu", .data = &imx93_data },
> {},
> };
> MODULE_DEVICE_TABLE(of, qoriq_tmu_match);
next prev parent reply other threads:[~2026-05-06 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 2:53 [PATCH v6 0/4] Update the thermal support for imx93 Jacky Bai
2026-04-30 2:53 ` [PATCH v6 1/4] dt-bindings: thermal: qoriq: Add compatible string " Jacky Bai
2026-04-30 2:53 ` [PATCH v6 2/4] thermal: qoriq: add i.MX93 tmu support Jacky Bai
2026-05-06 16:17 ` Daniel Lezcano [this message]
2026-04-30 2:53 ` [PATCH v6 3/4] thermal: qoriq: workaround unexpected temperature readings from tmu Jacky Bai
2026-04-30 2:53 ` [PATCH v6 4/4] arm64: dts: imx93: update the tmu compatible string Jacky Bai
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=2e9dd9fc-a42b-40ea-8393-3bf66955c4f2@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=alice.guo@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=ping.bai@nxp.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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