<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックThermal driver with 5.4 kernel issues</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1185186#M165111</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;following issue occurs on a board using IMX8MNSL using the &lt;EM&gt;drivers/thermal/imx8mm_thermal.c&lt;/EM&gt; thermal driver (though it should affect all &lt;EM&gt;i.MX 8M Mini/Nano/Mplus&lt;/EM&gt; non quadcore variants):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;root@phyboard-polis-imx8mn-1:~# dmesg | grep tmu
[    2.905043] platform 30260000.tmu: Retrying from deferred list
[    2.905596] bus: &lt;SPAN class="code-quote"&gt;'platform'&lt;/SPAN&gt;: driver_probe_device: matched device 30260000.tmu with driver i.mx8mm_thermal
[    2.905603] bus: &lt;SPAN class="code-quote"&gt;'platform'&lt;/SPAN&gt;: really_probe: probing driver i.mx8mm_thermal with device 30260000.tmu
[    2.905620] i.mx8mm_thermal 30260000.tmu: no pinctrl handle
[    2.905710] i.mx8mm_thermal 30260000.tmu: failed to register thermal zone sensor[0]: 0&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;Which can be traced back to &lt;EM&gt;drivers/thermal/of-thermal.c:&lt;/EM&gt;&lt;/P&gt;&lt;PRE&gt;count = of_count_phandle_with_args(np, &lt;SPAN class="code-quote"&gt;"cooling-device"&lt;/SPAN&gt;,
                                           &lt;SPAN class="code-quote"&gt;"#cooling-cells"&lt;/SPAN&gt;);&lt;/PRE&gt;&lt;P&gt;count is -22 EINVAL.&lt;/P&gt;&lt;P&gt;In the SoC dtsi devicetree file &lt;EM&gt;arch/arm64/boot/dts/freescale/imx8mn.dtsi &lt;/EM&gt;the cooling map0 contains four cooling devices linked to the four A53 cpu cores:&lt;/P&gt;&lt;PRE&gt; cooling-maps {&lt;BR /&gt;map0 {&lt;BR /&gt;trip = &amp;lt;&amp;amp;cpu_alert0&amp;gt;;&lt;BR /&gt;cooling-device =&lt;BR /&gt;&amp;lt;&amp;amp;A53_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_2 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_3 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;;&lt;BR /&gt;};&lt;/PRE&gt;&lt;P&gt;However in case of a single core or dual core CPU the boatloader U-Boot deletes the unused CPU nodes but doesn't update the the cooling map. This results in the described error.&lt;/P&gt;&lt;P&gt;Possible solutions are either add just one cooling device for the first CPU-core in the devicetree SoC-file for all CPU-variants like it's used to be in the 4.19 kernel versions&lt;/P&gt;&lt;PRE&gt;cooling-maps {
			map0 {
				trip = &amp;lt;&amp;amp;cpu_alert0&amp;gt;;
				cooling-device =
				&amp;lt;&amp;amp;A53_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;;
				};
			};&lt;/PRE&gt;&lt;P&gt;or add a function to update the cooling map in U-Boot similar to the one deleting the CPU-core nodes.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Dominik&lt;/P&gt;</description>
    <pubDate>Wed, 18 Nov 2020 11:37:56 GMT</pubDate>
    <dc:creator>dmhaller</dc:creator>
    <dc:date>2020-11-18T11:37:56Z</dc:date>
    <item>
      <title>Thermal driver with 5.4 kernel issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1185186#M165111</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;following issue occurs on a board using IMX8MNSL using the &lt;EM&gt;drivers/thermal/imx8mm_thermal.c&lt;/EM&gt; thermal driver (though it should affect all &lt;EM&gt;i.MX 8M Mini/Nano/Mplus&lt;/EM&gt; non quadcore variants):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;root@phyboard-polis-imx8mn-1:~# dmesg | grep tmu
[    2.905043] platform 30260000.tmu: Retrying from deferred list
[    2.905596] bus: &lt;SPAN class="code-quote"&gt;'platform'&lt;/SPAN&gt;: driver_probe_device: matched device 30260000.tmu with driver i.mx8mm_thermal
[    2.905603] bus: &lt;SPAN class="code-quote"&gt;'platform'&lt;/SPAN&gt;: really_probe: probing driver i.mx8mm_thermal with device 30260000.tmu
[    2.905620] i.mx8mm_thermal 30260000.tmu: no pinctrl handle
[    2.905710] i.mx8mm_thermal 30260000.tmu: failed to register thermal zone sensor[0]: 0&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;Which can be traced back to &lt;EM&gt;drivers/thermal/of-thermal.c:&lt;/EM&gt;&lt;/P&gt;&lt;PRE&gt;count = of_count_phandle_with_args(np, &lt;SPAN class="code-quote"&gt;"cooling-device"&lt;/SPAN&gt;,
                                           &lt;SPAN class="code-quote"&gt;"#cooling-cells"&lt;/SPAN&gt;);&lt;/PRE&gt;&lt;P&gt;count is -22 EINVAL.&lt;/P&gt;&lt;P&gt;In the SoC dtsi devicetree file &lt;EM&gt;arch/arm64/boot/dts/freescale/imx8mn.dtsi &lt;/EM&gt;the cooling map0 contains four cooling devices linked to the four A53 cpu cores:&lt;/P&gt;&lt;PRE&gt; cooling-maps {&lt;BR /&gt;map0 {&lt;BR /&gt;trip = &amp;lt;&amp;amp;cpu_alert0&amp;gt;;&lt;BR /&gt;cooling-device =&lt;BR /&gt;&amp;lt;&amp;amp;A53_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_2 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;A53_3 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;;&lt;BR /&gt;};&lt;/PRE&gt;&lt;P&gt;However in case of a single core or dual core CPU the boatloader U-Boot deletes the unused CPU nodes but doesn't update the the cooling map. This results in the described error.&lt;/P&gt;&lt;P&gt;Possible solutions are either add just one cooling device for the first CPU-core in the devicetree SoC-file for all CPU-variants like it's used to be in the 4.19 kernel versions&lt;/P&gt;&lt;PRE&gt;cooling-maps {
			map0 {
				trip = &amp;lt;&amp;amp;cpu_alert0&amp;gt;;
				cooling-device =
				&amp;lt;&amp;amp;A53_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT&amp;gt;;
				};
			};&lt;/PRE&gt;&lt;P&gt;or add a function to update the cooling map in U-Boot similar to the one deleting the CPU-core nodes.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Dominik&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 11:37:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1185186#M165111</guid>
      <dc:creator>dmhaller</dc:creator>
      <dc:date>2020-11-18T11:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal driver with 5.4 kernel issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1189191#M165510</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/180520"&gt;@dmhaller&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Device tree needs to be adapted for the chip configuration that you use.&lt;/P&gt;
&lt;P&gt;This means removing references to cores not present.&lt;/P&gt;
&lt;P&gt;Please let me know if this information is enough.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Israel H.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 18:09:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1189191#M165510</guid>
      <dc:creator>nxf63675</dc:creator>
      <dc:date>2020-11-25T18:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal driver with 5.4 kernel issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1192215#M165853</link>
      <description>&lt;P&gt;Yeah, that's kinda the first thing that came to my mind.&lt;/P&gt;&lt;P&gt;So take this issue just for informational purposes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dominik&lt;/P&gt;</description>
      <pubDate>Wed, 02 Dec 2020 09:34:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Thermal-driver-with-5-4-kernel-issues/m-p/1192215#M165853</guid>
      <dc:creator>dmhaller</dc:creator>
      <dc:date>2020-12-02T09:34:49Z</dc:date>
    </item>
  </channel>
</rss>

