From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Marek Vasut <marex@denx.de>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Peng Fan <peng.fan@nxp.com>, Adam Ford <aford173@gmail.com>,
Alice Guo <alice.guo@nxp.com>, Amit Kucheria <amitk@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Li Jun <jun.li@nxp.com>, Lucas Stach <l.stach@pengutronix.de>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/5] thermal/drivers/imx: Add support for loading calibration data from OCOTP
Date: Sun, 4 Dec 2022 17:26:16 +0100 [thread overview]
Message-ID: <9f30e38c-61ef-d245-56ce-fc9911f54814@linaro.org> (raw)
In-Reply-To: <20221202162353.274009-5-marex@denx.de>
On 02/12/2022 17:23, Marek Vasut wrote:
> The TMU TASR, TCALIVn, TRIM registers must be explicitly programmed with
> calibration values in OCOTP. Add support for reading the OCOTP calibration
> data and programming those into the TMU hardware.
>
> The MX8MM/MX8MN TMUv1 uses only one OCOTP cell, while MX8MP TMUv2 uses 4,
> the programming differs in each case.
>
> Based on U-Boot commits:
> 70487ff386c ("imx8mm: Load fuse for TMU TCALIV and TASR")
> ebb9aab318b ("imx: load calibration parameters from fuse for i.MX8MP")
>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
> Signed-off-by: Marek Vasut <marex@denx.de>
Applied, thanks
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-12-04 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 16:23 [PATCH v3 1/5] dt-bindings: thermal: imx8mm-thermal: Document optional nvmem-cells Marek Vasut
2022-12-02 16:23 ` [PATCH v3 2/5] arm64: dts: imx8m: Align SoC unique ID node unit address Marek Vasut
2022-12-31 12:36 ` Shawn Guo
2022-12-02 16:23 ` [PATCH v3 3/5] arm64: dts: imx8m: Document the fuse address calculation Marek Vasut
2022-12-02 16:23 ` [PATCH v3 4/5] arm64: dts: imx8m: Add TMU phandle to calibration data in OCOTP Marek Vasut
2022-12-02 16:23 ` [PATCH v3 5/5] thermal/drivers/imx: Add support for loading calibration data from OCOTP Marek Vasut
2022-12-04 16:26 ` Daniel Lezcano [this message]
2022-12-04 16:25 ` [PATCH v3 1/5] dt-bindings: thermal: imx8mm-thermal: Document optional nvmem-cells Daniel Lezcano
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=9f30e38c-61ef-d245-56ce-fc9911f54814@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=aford173@gmail.com \
--cc=alice.guo@nxp.com \
--cc=amitk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=rafael@kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).