<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/Documentation/hwmon, branch master</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>hwmon: (asus_rog_ryujin) Fix pump control source on the Ryujin III</title>
<updated>2026-11-02T15:00:04+00:00</updated>
<author>
<name>Zac Lanzon</name>
<email>lanzonza@gmail.com</email>
</author>
<published>2026-09-28T11:41:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=743b4481b6112d8ac11c165628daa8e0f0ecf78c'/>
<id>743b4481b6112d8ac11c165628daa8e0f0ecf78c</id>
<content type='text'>
The RYUJIN III pump has a 4-pin cable for a motherboard fan header in
addition to USB. Byte 2 of the set cooler duty command selects the pump
control source: 0 hands the pump to its internal controller, which
follows the PWM of the header its 4-pin cable is plugged into, and 1
makes it follow the pump duty in byte 3. Byte 3 of the cooler duty
report returns the current source.

The driver fills byte 2 with duty_channel, which is 1 for the RYUJIN
III, and a pwm2 write re-sends the reported pump duty with the new fan
duty. So writing only the internal fan duty takes the pump away from
its internal controller.

Measured on a RYUJIN III 360 (firmware AURJ2-S750-0108) with the pump
cable on AIO_PUMP and the header PWM set through nct6775, after loading
the driver with the pump on its internal controller (pump rpm):

                                   header 50%   header 80%   source
  no write yet                        2160         3090         0
  pwm2 = 40%, before this patch       1740         1740         1
  pwm2 = 40%, with this patch         2130         3090         0

Send the reported source with pwm2 writes. The fan duty applies with
either source (40%: 1545 to 1590 rpm, 30%: 870 rpm). A pwm2 write sent
right after a pwm1 write that took the pump over, before the report
could show the change, left the pump on USB and applied its fan duty
(2 of 2 trials, and 7 of 7 with raw commands up to 0.9 s after).

pwm1 writes keep selecting source 1. The cooler reports the pump duty of
the last write, whichever source it selected, and 40% after power-on.
Byte 9 of the status report follows the duty the pump runs at. Measured
from power-on (PSU switched off) once per driver, with the header at
100%:

                                  before this patch   with this patch
                                  source duty  rpm    source duty  rpm
  no write yet                       0    100  3570      0    100  3570
  pwm2 = 40%                         1    100  3570      0    100  3570
  pwm1 = 40%, the reported duty      1    100  3570      1     40  1710
  pwm1 = 60%                         1     60  2430
  pwm1 = 40%                         1     40  1725

So a pwm1 write of the reported duty did not reach the pump, while
other duties applied in one write, also when taking the pump from its
internal controller (60%: 2460 rpm). When a pwm1 write requests the
reported duty, write a duty 1% away first (below at 100%), then the
requested one. Sent back to back, the two writes left the pump at the
requested duty in all 19 trials, 9 with raw commands and 10 through
this driver.

Tested on the RYUJIN III 360 only. The EXTREME, EVA and WHITE EDITION
use the same rog_ryujin_iii_info and send the same command, and Edward
Blair's analysis of the WHITE EDITION firmware shows the same pump
control source. The RYUJIN II, whose duty_channel is 0, is unchanged.

Fixes: cd258aca0dc4 ("hwmon: (asus_rog_ryujin) Add ROG Ryujin III support")
Closes: https://github.com/aleksamagicka/asus_rog_ryujin-hwmon/issues/12
Suggested-by: Edward Blair &lt;edward.blair@gmail.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Zac Lanzon &lt;lanzonza@gmail.com&gt;
Link: https://patch.msgid.link/7ca8fe6cd6b4125813613bd4187ff6cdda72e4b6.1790512964.git.lanzonza@gmail.com
[groeck: Dropped obsolete 'Assisted-by: tag]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The RYUJIN III pump has a 4-pin cable for a motherboard fan header in
addition to USB. Byte 2 of the set cooler duty command selects the pump
control source: 0 hands the pump to its internal controller, which
follows the PWM of the header its 4-pin cable is plugged into, and 1
makes it follow the pump duty in byte 3. Byte 3 of the cooler duty
report returns the current source.

The driver fills byte 2 with duty_channel, which is 1 for the RYUJIN
III, and a pwm2 write re-sends the reported pump duty with the new fan
duty. So writing only the internal fan duty takes the pump away from
its internal controller.

Measured on a RYUJIN III 360 (firmware AURJ2-S750-0108) with the pump
cable on AIO_PUMP and the header PWM set through nct6775, after loading
the driver with the pump on its internal controller (pump rpm):

                                   header 50%   header 80%   source
  no write yet                        2160         3090         0
  pwm2 = 40%, before this patch       1740         1740         1
  pwm2 = 40%, with this patch         2130         3090         0

Send the reported source with pwm2 writes. The fan duty applies with
either source (40%: 1545 to 1590 rpm, 30%: 870 rpm). A pwm2 write sent
right after a pwm1 write that took the pump over, before the report
could show the change, left the pump on USB and applied its fan duty
(2 of 2 trials, and 7 of 7 with raw commands up to 0.9 s after).

pwm1 writes keep selecting source 1. The cooler reports the pump duty of
the last write, whichever source it selected, and 40% after power-on.
Byte 9 of the status report follows the duty the pump runs at. Measured
from power-on (PSU switched off) once per driver, with the header at
100%:

                                  before this patch   with this patch
                                  source duty  rpm    source duty  rpm
  no write yet                       0    100  3570      0    100  3570
  pwm2 = 40%                         1    100  3570      0    100  3570
  pwm1 = 40%, the reported duty      1    100  3570      1     40  1710
  pwm1 = 60%                         1     60  2430
  pwm1 = 40%                         1     40  1725

So a pwm1 write of the reported duty did not reach the pump, while
other duties applied in one write, also when taking the pump from its
internal controller (60%: 2460 rpm). When a pwm1 write requests the
reported duty, write a duty 1% away first (below at 100%), then the
requested one. Sent back to back, the two writes left the pump at the
requested duty in all 19 trials, 9 with raw commands and 10 through
this driver.

Tested on the RYUJIN III 360 only. The EXTREME, EVA and WHITE EDITION
use the same rog_ryujin_iii_info and send the same command, and Edward
Blair's analysis of the WHITE EDITION firmware shows the same pump
control source. The RYUJIN II, whose duty_channel is 0, is unchanged.

Fixes: cd258aca0dc4 ("hwmon: (asus_rog_ryujin) Add ROG Ryujin III support")
Closes: https://github.com/aleksamagicka/asus_rog_ryujin-hwmon/issues/12
Suggested-by: Edward Blair &lt;edward.blair@gmail.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Zac Lanzon &lt;lanzonza@gmail.com&gt;
Link: https://patch.msgid.link/7ca8fe6cd6b4125813613bd4187ff6cdda72e4b6.1790512964.git.lanzonza@gmail.com
[groeck: Dropped obsolete 'Assisted-by: tag]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'hwmon-for-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging</title>
<updated>2026-10-26T16:59:21+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-26T16:59:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=7313d94c67daf04bc1b6ee39b492d2795fe2f3da'/>
<id>7313d94c67daf04bc1b6ee39b492d2795fe2f3da</id>
<content type='text'>
Pull hwmon updates from Guenter Roeck:
 "New drivers:
   - Axiado AX3000 and AX3005 PWM fan controller
   - AX3000/AX3005 TSADC
   - HONOR FMI-XX
   - Minisforum UM780 XTX EC monitoring and fan control
   - pmbus: MAX20826, MAX20855B, MAX20908, MAX20912, MAX20826, and
     MAX20916
   - pmbus: Infineon TDA38740/TDA38725

  Added support to existing drivers:
   - asus-ec-sensors: ROG STRIX X670E-A GAMING WIFI and ROG STRIX Z490-A
     GAMING
   - asus_rog_ryujin: ROG Ryujin III 360
   - dell-smm: Dell 16 DC16250, Dell OptiPlex 7090, Dell Precision 3650
     Tower, Add Latitude 5420
   - it87: IT8613E
   - k10temp: 1ah/80h devices. Drop support for Hygon devices (support
     to be re-added with separate patches later)
   - lm63: Sensylink CTF2301
   - nct6683: MSI MAG B550M MORTAR MAX WIFI, MSI MAG B650 TOMAHAWK WIFI,
     MSI MAG B650M MORTAR WIFI (MS-7D76), and MSI MAG B850M MORTAR WIFI
   - nct6775: NCT6122D and NCT6126D
   - pmbus/isl68137: Renesas RAA229639 and RAA229640
   - pmbus/max34440: ADPM12300
   - pmbus/tps25990: TPS1689
   - pmbus/tps53679: TPS53622, TPS53659 and TPS536C7
   - pmbus/xdpe1a2g7b: xdpe1a2g7c
   - sht4x: Sensirion STS4x
   - socfpga: Agilex 5
   - yogafan: Lenovo Yoga Pro 9 16IMH9, Yoga 14cACN 2021, IdeaPad 3
     15ALC6 Ub, Yoga 740-15IML

  Core updates:
   - Support for currX_emergency and inX_[l]emergency attributes

  Notable bug fixes and changes:
   - Add missing locks to corsair-cpro, ftsteutates, nct7904, and
     npcm750-pwm-fan drivers
   - Fix jiffies wraparound in tmp102 and tmp108 drivers
   - Documentation updates (document missing chip support, typo fixes,
     clarifications)
   - pmbus/ltc4286: Add writable shunt_resistor sysfs attribute
   - coretemp: Document sysfs numbering and label meaning, fix handling
     of isolated SMT siblings, read TjMax only when refreshing the
     temperature, refresh the temperature on the first read, and return
     -ENODATA for invalid temperature readings
   - spd5118: Avoid probing when 16-bit addressing is enabled, and
     select page 0 unconditionally during probe
   - arctic_fan_controller: Default PWM cache to MCU 40%, Dual-license
     GPL-2.0-or-later OR BSD-2-Clause, and update maintainer address

  Various other minor bug fixes and improvements"

* tag 'hwmon-for-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: (97 commits)
  hwmon: (npcm750-pwm-fan) serialize PWM register updates
  hwmon: (nct7904) serialise the watchdog and sensors
  hwmon: (ftsteutates) serialise the watchdog and sensors
  hwmon: (acpi_power_meter) Fix 18.45 TW bug
  hwmon: (sht3x) Return the consumed count for heater writes
  hwmon: (mcp9982) Update the interval cache only after successful writes
  hwmon: (gigabyte_waterforce) reject short input reports
  hwmon: (coretemp) Fix handling of isolated SMT siblings
  hwmon: (coretemp) Document sysfs numbering and label meaning
  hwmon: (asus_wmi_sensors) Reword BIOS upgrade advice
  hwmon: Replace __MODULE_STRING() with __stringify()
  hwmon:(pmbus/xdpe1a2g7b) Add support for xdpe1a2g7c controller
  dt-bindings: trivial-devices: Add support for XDPE1A2G7C
  hwmon: (pmbus/isl68137) Add Renesas RAA229639 and RAA229640
  dt-bindings: hwmon: pmbus/isl68137: Add Renesas RAA229639 and RAA229640
  hwmon: (coretemp) Read TjMax only when refreshing the temperature
  hwmon: (pmbus/ibm-cffps) Avoid format truncation warnings
  hwmon: (dell-smm) Add Dell 16 DC16250 to fan control whitelist
  hwmon: (nct6683) Add more MSI boards to list of tested boards
  hwmon: (nct6683) Add MSI B850M to list of tested boards
  ...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull hwmon updates from Guenter Roeck:
 "New drivers:
   - Axiado AX3000 and AX3005 PWM fan controller
   - AX3000/AX3005 TSADC
   - HONOR FMI-XX
   - Minisforum UM780 XTX EC monitoring and fan control
   - pmbus: MAX20826, MAX20855B, MAX20908, MAX20912, MAX20826, and
     MAX20916
   - pmbus: Infineon TDA38740/TDA38725

  Added support to existing drivers:
   - asus-ec-sensors: ROG STRIX X670E-A GAMING WIFI and ROG STRIX Z490-A
     GAMING
   - asus_rog_ryujin: ROG Ryujin III 360
   - dell-smm: Dell 16 DC16250, Dell OptiPlex 7090, Dell Precision 3650
     Tower, Add Latitude 5420
   - it87: IT8613E
   - k10temp: 1ah/80h devices. Drop support for Hygon devices (support
     to be re-added with separate patches later)
   - lm63: Sensylink CTF2301
   - nct6683: MSI MAG B550M MORTAR MAX WIFI, MSI MAG B650 TOMAHAWK WIFI,
     MSI MAG B650M MORTAR WIFI (MS-7D76), and MSI MAG B850M MORTAR WIFI
   - nct6775: NCT6122D and NCT6126D
   - pmbus/isl68137: Renesas RAA229639 and RAA229640
   - pmbus/max34440: ADPM12300
   - pmbus/tps25990: TPS1689
   - pmbus/tps53679: TPS53622, TPS53659 and TPS536C7
   - pmbus/xdpe1a2g7b: xdpe1a2g7c
   - sht4x: Sensirion STS4x
   - socfpga: Agilex 5
   - yogafan: Lenovo Yoga Pro 9 16IMH9, Yoga 14cACN 2021, IdeaPad 3
     15ALC6 Ub, Yoga 740-15IML

  Core updates:
   - Support for currX_emergency and inX_[l]emergency attributes

  Notable bug fixes and changes:
   - Add missing locks to corsair-cpro, ftsteutates, nct7904, and
     npcm750-pwm-fan drivers
   - Fix jiffies wraparound in tmp102 and tmp108 drivers
   - Documentation updates (document missing chip support, typo fixes,
     clarifications)
   - pmbus/ltc4286: Add writable shunt_resistor sysfs attribute
   - coretemp: Document sysfs numbering and label meaning, fix handling
     of isolated SMT siblings, read TjMax only when refreshing the
     temperature, refresh the temperature on the first read, and return
     -ENODATA for invalid temperature readings
   - spd5118: Avoid probing when 16-bit addressing is enabled, and
     select page 0 unconditionally during probe
   - arctic_fan_controller: Default PWM cache to MCU 40%, Dual-license
     GPL-2.0-or-later OR BSD-2-Clause, and update maintainer address

  Various other minor bug fixes and improvements"

* tag 'hwmon-for-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: (97 commits)
  hwmon: (npcm750-pwm-fan) serialize PWM register updates
  hwmon: (nct7904) serialise the watchdog and sensors
  hwmon: (ftsteutates) serialise the watchdog and sensors
  hwmon: (acpi_power_meter) Fix 18.45 TW bug
  hwmon: (sht3x) Return the consumed count for heater writes
  hwmon: (mcp9982) Update the interval cache only after successful writes
  hwmon: (gigabyte_waterforce) reject short input reports
  hwmon: (coretemp) Fix handling of isolated SMT siblings
  hwmon: (coretemp) Document sysfs numbering and label meaning
  hwmon: (asus_wmi_sensors) Reword BIOS upgrade advice
  hwmon: Replace __MODULE_STRING() with __stringify()
  hwmon:(pmbus/xdpe1a2g7b) Add support for xdpe1a2g7c controller
  dt-bindings: trivial-devices: Add support for XDPE1A2G7C
  hwmon: (pmbus/isl68137) Add Renesas RAA229639 and RAA229640
  dt-bindings: hwmon: pmbus/isl68137: Add Renesas RAA229639 and RAA229640
  hwmon: (coretemp) Read TjMax only when refreshing the temperature
  hwmon: (pmbus/ibm-cffps) Avoid format truncation warnings
  hwmon: (dell-smm) Add Dell 16 DC16250 to fan control whitelist
  hwmon: (nct6683) Add more MSI boards to list of tested boards
  hwmon: (nct6683) Add MSI B850M to list of tested boards
  ...
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (coretemp) Document sysfs numbering and label meaning</title>
<updated>2026-10-19T12:45:07+00:00</updated>
<author>
<name>Asaf Nuri Bertizlioğlu</name>
<email>ycistak@gmail.com</email>
</author>
<published>2026-10-15T17:17:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=8e9bd28236e633238a7773c9dd809bd87a4db1c2'/>
<id>8e9bd28236e633238a7773c9dd809bd87a4db1c2</id>
<content type='text'>
The documentation says that all sysfs entries are named with their
core_id, and that the "Core X" label contains the processor number.
Neither is accurate. create_core_attrs() numbers the per-core
attributes core_id + 2 and always uses temp1 for the package sensor,
and show_label() prints topology_core_id(), not the logical CPU
number.

The difference is easy to see on hybrid CPUs. On an i7-14700F, the
"Core 4" label is on temp6 and belongs to CPUs 2 and 3, and the
E-cores report core IDs 32 to 43.

Describe the actual numbering.

The mismatch was found by an LLM comparing the documentation with the
code, and verified on the i7-14700F above.

Assisted-by: LLM
Signed-off-by: Asaf Nuri Bertizlioğlu &lt;ycistak@gmail.com&gt;
Tested-by: Ximing Zhang &lt;xzhangjr@gmail.com&gt;
Reviewed-by: Ximing Zhang &lt;xzhangjr@gmail.com&gt;
Link: https://patch.msgid.link/20261015171759.704526-1-ycistak@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The documentation says that all sysfs entries are named with their
core_id, and that the "Core X" label contains the processor number.
Neither is accurate. create_core_attrs() numbers the per-core
attributes core_id + 2 and always uses temp1 for the package sensor,
and show_label() prints topology_core_id(), not the logical CPU
number.

The difference is easy to see on hybrid CPUs. On an i7-14700F, the
"Core 4" label is on temp6 and belongs to CPUs 2 and 3, and the
E-cores report core IDs 32 to 43.

Describe the actual numbering.

The mismatch was found by an LLM comparing the documentation with the
code, and verified on the i7-14700F above.

Assisted-by: LLM
Signed-off-by: Asaf Nuri Bertizlioğlu &lt;ycistak@gmail.com&gt;
Tested-by: Ximing Zhang &lt;xzhangjr@gmail.com&gt;
Reviewed-by: Ximing Zhang &lt;xzhangjr@gmail.com&gt;
Link: https://patch.msgid.link/20261015171759.704526-1-ycistak@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (asus_wmi_sensors) Reword BIOS upgrade advice</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Qian Xiao</name>
<email>heyheyco@gmail.com</email>
</author>
<published>2026-10-16T16:35:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=58d7d43e48044642d22c4c7afc4c5b99103dd684'/>
<id>58d7d43e48044642d22c4c7afc4c5b99103dd684</id>
<content type='text'>
The Known Issues section suggests that upgrading to a BIOS with WMI
method version two or greater should rectify the problem. However, the
driver refuses to bind when the BIOS reports a version below two, so
every system using the driver already meets that condition and the
advice does not help.

Instead, suggest that upgrading to a more recent BIOS version might
help. While at it, fix a typo in the preceding sentence.

Link: https://lore.kernel.org/linux-hwmon/CAFGXJCm6ZWK0NsFhZ1_ycgYtTTT3nhqj9mose60t+Rrry1aPvw@mail.gmail.com/
Suggested-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Qian Xiao &lt;heyheyco@gmail.com&gt;
Link: https://patch.msgid.link/20261016163509.249020-1-heyheyco@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Known Issues section suggests that upgrading to a BIOS with WMI
method version two or greater should rectify the problem. However, the
driver refuses to bind when the BIOS reports a version below two, so
every system using the driver already meets that condition and the
advice does not help.

Instead, suggest that upgrading to a more recent BIOS version might
help. While at it, fix a typo in the preceding sentence.

Link: https://lore.kernel.org/linux-hwmon/CAFGXJCm6ZWK0NsFhZ1_ycgYtTTT3nhqj9mose60t+Rrry1aPvw@mail.gmail.com/
Suggested-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Qian Xiao &lt;heyheyco@gmail.com&gt;
Link: https://patch.msgid.link/20261016163509.249020-1-heyheyco@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (nct6683) Add more MSI boards to list of tested boards</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2026-09-22T17:10:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=04f4079ee61a76655781c7be5cf20dac90ebbfde'/>
<id>04f4079ee61a76655781c7be5cf20dac90ebbfde</id>
<content type='text'>
Tested with the following boards:
- MSI MAG B550M MORTAR MAX WIFI (MS-7C94)
- MSI MAG B650 TOMAHAWK WIFI (MS-7D75)
- MSI MAG B650M MORTAR WIFI (MS-7D76)

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tested with the following boards:
- MSI MAG B550M MORTAR MAX WIFI (MS-7C94)
- MSI MAG B650 TOMAHAWK WIFI (MS-7D75)
- MSI MAG B650M MORTAR WIFI (MS-7D76)

Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (nct6683) Add MSI B850M to list of tested boards</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Tomasz Bojanowski</name>
<email>tomasz@bojanowski.me</email>
</author>
<published>2026-09-21T21:13:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=f9c5d495e22f77c0455dacfca627e06219f05881'/>
<id>f9c5d495e22f77c0455dacfca627e06219f05881</id>
<content type='text'>
Tested on MSI MAG B850M MORTAR WIFI with NCT6687D EC firmware version
0.0 build 03/10/25. The driver loads without force=1 and reports
voltages, fan speeds and temperatures.

Signed-off-by: Tomasz Bojanowski &lt;tomasz@bojanowski.me&gt;
Link: https://patch.msgid.link/20260921211304.74729-1-tomasz@bojanowski.me
[groeck: Reordered to retain alphabetical order of boards]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tested on MSI MAG B850M MORTAR WIFI with NCT6687D EC firmware version
0.0 build 03/10/25. The driver loads without force=1 and reports
voltages, fan speeds and temperatures.

Signed-off-by: Tomasz Bojanowski &lt;tomasz@bojanowski.me&gt;
Link: https://patch.msgid.link/20260921211304.74729-1-tomasz@bojanowski.me
[groeck: Reordered to retain alphabetical order of boards]
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: add Axiado AX3000 and AX3005 PWM fan controller driver</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Petar Stepanovic</name>
<email>pstepanovic@axiado.com</email>
</author>
<published>2026-09-21T07:23:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=b9d5d15f8a05e2abb2f278a0b061873cc5f95a14'/>
<id>b9d5d15f8a05e2abb2f278a0b061873cc5f95a14</id>
<content type='text'>
Add support for the PWM fan controller found on the Axiado AX3000 and
AX3005 SoCs.

The controller uses a hardware tachometer block and interrupt to measure
fan speed. Fan speed is controlled through a PWM signal supplied by an
external PWM controller.

Register the controller with the hwmon subsystem and expose the standard
fan1_input and pwm1 attributes. The physical fan is represented by a fan
child node containing the PWM specifier and the optional
pulses-per-revolution property. If pulses-per-revolution is not specified,
the driver uses two pulses per revolution.

The driver was tested on AX3000 and AX3005 boards.

Signed-off-by: Petar Stepanovic &lt;pstepanovic@axiado.com&gt;
Link: https://patch.msgid.link/20260921-axiado-ax3000-pwm-fan-v3-2-3def8b6ffec9@axiado.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add support for the PWM fan controller found on the Axiado AX3000 and
AX3005 SoCs.

The controller uses a hardware tachometer block and interrupt to measure
fan speed. Fan speed is controlled through a PWM signal supplied by an
external PWM controller.

Register the controller with the hwmon subsystem and expose the standard
fan1_input and pwm1 attributes. The physical fan is represented by a fan
child node containing the PWM specifier and the optional
pulses-per-revolution property. If pulses-per-revolution is not specified,
the driver uses two pulses per revolution.

The driver was tested on AX3000 and AX3005 boards.

Signed-off-by: Petar Stepanovic &lt;pstepanovic@axiado.com&gt;
Link: https://patch.msgid.link/20260921-axiado-ax3000-pwm-fan-v3-2-3def8b6ffec9@axiado.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (pmbus/tda38740) Add driver for Infineon TDA38740/TDA38725</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Colin Huang</name>
<email>u8813345@gmail.com</email>
</author>
<published>2026-09-18T10:23:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=3f02ddc3771c93276f17bbcb0f4482f2bf67fe99'/>
<id>3f02ddc3771c93276f17bbcb0f4482f2bf67fe99</id>
<content type='text'>
Add a PMBus driver for Infineon TDA38740 and TDA38725
single-voltage synchronous buck regulators.

Signed-off-by: Colin Huang &lt;u8813345@gmail.com&gt;
Reviewed-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Link: https://patch.msgid.link/20260918-add-tda38740-and-tda38725-v6-2-a8b11018d850@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add a PMBus driver for Infineon TDA38740 and TDA38725
single-voltage synchronous buck regulators.

Signed-off-by: Colin Huang &lt;u8813345@gmail.com&gt;
Reviewed-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Link: https://patch.msgid.link/20260918-add-tda38740-and-tda38725-v6-2-a8b11018d850@gmail.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: documentation: vexpress: point the DT binding reference at the schema</title>
<updated>2026-10-18T16:35:08+00:00</updated>
<author>
<name>Quchaosheng</name>
<email>quchaosheng000406@163.com</email>
</author>
<published>2026-09-17T11:58:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=fbc5cab2e6b671749dd502fdb44803f82e2b7538'/>
<id>fbc5cab2e6b671749dd502fdb44803f82e2b7538</id>
<content type='text'>
Documentation/hwmon/vexpress.rst points at
Documentation/devicetree/bindings/hwmon/vexpress.txt for the device tree
binding of the arm,vexpress-volt, -amp, -temp, -power and -energy sensors.

That file only restates the compatibles and the label property, which the
arm/vexpress-config.yaml schema describes now. Point the reference there.

Assisted-by: LLM
Signed-off-by: Quchaosheng &lt;quchaosheng000406@163.com&gt;
Link: https://patch.msgid.link/20260917115818.540344-1-quchaosheng000406@163.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Documentation/hwmon/vexpress.rst points at
Documentation/devicetree/bindings/hwmon/vexpress.txt for the device tree
binding of the arm,vexpress-volt, -amp, -temp, -power and -energy sensors.

That file only restates the compatibles and the label property, which the
arm/vexpress-config.yaml schema describes now. Point the reference there.

Assisted-by: LLM
Signed-off-by: Quchaosheng &lt;quchaosheng000406@163.com&gt;
Link: https://patch.msgid.link/20260917115818.540344-1-quchaosheng000406@163.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>hwmon: (pmbus/tps53679) Add support for TPS536C7</title>
<updated>2026-10-18T16:35:07+00:00</updated>
<author>
<name>Sanman Pradhan</name>
<email>psanman@juniper.net</email>
</author>
<published>2026-09-15T16:48:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=f173bf7161def6ab83f95363857869b64cfc0c45'/>
<id>f173bf7161def6ab83f95363857869b64cfc0c45</id>
<content type='text'>
TPS536C7 is a dual-channel D-CAP+ step-down controller whose channels are
distributed across a configurable number of phases (N+M, up to 12 total).
Whether channel B (PMBus page 1) exists depends on the phase configuration
register, so the page count is derived at probe time.

Factor the TPS53676 phase-map parsing into a shared helper and reuse it
for TPS536C7. Only aggregate per-channel telemetry is exposed: leave
info-&gt;phases[] unset so the PMBus core never programs the PHASE selector
on every read (and because TPS536C7 can place up to 12 phases on channel
A, exceeding PMBUS_PHASES). Report VOUT in linear format like TPS53676.

Since the core never programs PHASE, set it to 0xff on each populated
page so READ_IOUT reports the aggregate channel current, and verify it
(PHASE can be write-protected). Fail identification if aggregate
selection cannot be established, since otherwise a single phase current
could be reported as the channel total.

A configuration with no channel-A phase is rejected with -EOPNOTSUPP:
the PMBus core models pages as the contiguous range 0..pages-1 and
cannot represent a channel-A-absent topology.

On the tested TPS536C7 (device ID 54 49 53 6c 70 00, CAPABILITY 0xd0),
block reads of IC_DEVICE_ID and USER_DATA_03 return -EBADMSG with PEC
enabled, while retrying those two reads without PEC returns the expected
6- and 24-byte payloads. Standard byte/word telemetry keeps using PEC,
so only those two identification reads fall back to no-PEC.

Co-developed-by: Senthil Muniyappan &lt;smuniyappan@juniper.net&gt;
Co-developed-by: Vaibhav Agarwal &lt;avaibhav@juniper.net&gt;
Signed-off-by: Sanman Pradhan &lt;psanman@juniper.net&gt;
Link: https://patch.msgid.link/20260915164823.160977-4-sanman.pradhan@hpe.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
TPS536C7 is a dual-channel D-CAP+ step-down controller whose channels are
distributed across a configurable number of phases (N+M, up to 12 total).
Whether channel B (PMBus page 1) exists depends on the phase configuration
register, so the page count is derived at probe time.

Factor the TPS53676 phase-map parsing into a shared helper and reuse it
for TPS536C7. Only aggregate per-channel telemetry is exposed: leave
info-&gt;phases[] unset so the PMBus core never programs the PHASE selector
on every read (and because TPS536C7 can place up to 12 phases on channel
A, exceeding PMBUS_PHASES). Report VOUT in linear format like TPS53676.

Since the core never programs PHASE, set it to 0xff on each populated
page so READ_IOUT reports the aggregate channel current, and verify it
(PHASE can be write-protected). Fail identification if aggregate
selection cannot be established, since otherwise a single phase current
could be reported as the channel total.

A configuration with no channel-A phase is rejected with -EOPNOTSUPP:
the PMBus core models pages as the contiguous range 0..pages-1 and
cannot represent a channel-A-absent topology.

On the tested TPS536C7 (device ID 54 49 53 6c 70 00, CAPABILITY 0xd0),
block reads of IC_DEVICE_ID and USER_DATA_03 return -EBADMSG with PEC
enabled, while retrying those two reads without PEC returns the expected
6- and 24-byte payloads. Standard byte/word telemetry keeps using PEC,
so only those two identification reads fall back to no-PEC.

Co-developed-by: Senthil Muniyappan &lt;smuniyappan@juniper.net&gt;
Co-developed-by: Vaibhav Agarwal &lt;avaibhav@juniper.net&gt;
Signed-off-by: Sanman Pradhan &lt;psanman@juniper.net&gt;
Link: https://patch.msgid.link/20260915164823.160977-4-sanman.pradhan@hpe.com
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</pre>
</div>
</content>
</entry>
</feed>
