kernel/git/next/linux-next.git/drivers/regulator, branch master

Merge branch 'headers' of git://git.infradead.org/users/willy/pagecache.git

2026-09-08T20:26:22+00:00

# Conflicts: # net/ceph/osd_client.c

Merge remote-tracking branch 'regulator/for-7.4' into regulator-next

2026-09-07T23:14:24+00:00

regulator: pf1550: fix which regulator is notified

2026-09-07T17:08:38+00:00

The interrupt handler distinguishes the rail that reported the fault, but the body ignores it. Every SW interrupt walks the regulator array looking for the name "SW3" and every LDO interrupt looks for "LDO3", so an over-current on SW1 is reported to the consumers of SW3 while the consumers of SW1 hear nothing. The lookup itself is unreliable as well. rdev_get_name() returns the device tree regulator-name property whenever the board supplies one, and only falls back to the name in the driver descriptor when it does not. The binding example for this device sets regulator-name to "sw3" and "ldo3", which strcmp() does not match against the upper case literals used here, so a board that follows the documentation gets no over-current notification at all. A board that names its rails after the schematic does not match either. No other driver in the tree selects a notification target this way. Replace the name lookup with rdev_get_id(), which returns the descriptor id set by the driver and cannot be overridden from the device tree, and take both the id and the event from a table indexed by the interrupt. The die temperature interrupts keep notifying every regulator since they report a chip wide condition. Fixes: 7320d41c29bb ("regulator: pf1550: Add support for regulator") Signed-off-by: Donggeun Yoo Link: https://patch.msgid.link/20260904105624.48577-1-donggeunyoo.kernel@gmail.com Signed-off-by: Mark Brown

regulator: fix typos and repeated words in comments

2026-09-04T22:30:49+00:00

Hemanth Selam says: This corrects 2 misspellings and repeated words in comments. Each is a separate patch so that any one of them can be dropped without touching the rest. Nothing outside comments changes. Every touched C file was checked by dropping its comments, replacing each string literal with a placeholder and collapsing whitespace; what remained was identical before and after, so the compiled code cannot differ. The mistakes were found with scripts/checkpatch.pl against the list in scripts/spelling.txt. The scanning, the edits and the changelogs were produced with Cursor running the claude-opus-5 model, from a request to find and fix spelling mistakes across the tree, and every correction was then re-checked by the comparison described above. Words that name an identifier were left alone deliberately, even when they read as typos, because correcting the prose would make the comment disagree with the code it describes. Tested by building x86_64 defconfig at v7.3-rc1-269-gbc35965f6940, which is clean. Nothing else was built, so any patch touching code that x86_64 defconfig does not compile has been read but not compiled. Link: https://patch.msgid.link/20260904110203.10113-1-hemanth.selam@gmail.com

regulator: fix repeated word in log message

2026-09-04T22:30:48+00:00

Drop the word written twice, reported by checkpatch.pl as a possible repeated word. Only the message text changes, no code changes. Assisted-by: Cursor:claude-opus-5 Signed-off-by: Hemanth Selam Link: https://patch.msgid.link/20260904110203.10113-3-hemanth.selam@gmail.com Signed-off-by: Mark Brown

regulator: fix typos in comments

2026-09-04T22:30:47+00:00

Fix typos in comments, reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes. Assisted-by: Cursor:claude-opus-5 Signed-off-by: Hemanth Selam Link: https://patch.msgid.link/20260904110203.10113-2-hemanth.selam@gmail.com Signed-off-by: Mark Brown

Add supply names for PM6350 RPMh regulators on Fairphone 4

2026-09-04T18:45:03+00:00

Luca Weiss says: During bringup no parent supply names were added to the RPMh regulator driver. Add them now. Link: https://patch.msgid.link/20260901-fp4-regulator-supply-v1-0-68288ab70aee@fairphone.com

regulator: qcom-rpmh: Add missing regulators in PM6350

2026-09-04T18:45:02+00:00

Add the missing smps3-6 and ldo17 definitions. While smps3/5 and ldo17 are not used from the rpmh regulator driver on SM6350, the regulators do exist, so add them with the types based on the datasheet. Signed-off-by: Luca Weiss Reviewed-by: Konrad Dybcio Reviewed-by: Abel Vesa Link: https://patch.msgid.link/20260901-fp4-regulator-supply-v1-3-68288ab70aee@fairphone.com Signed-off-by: Mark Brown

regulator: qcom-rpmh: Add supply names for PM6350

2026-09-04T18:45:01+00:00

The supply names for the PM6350 regulators were skipped during initial bringup. Add them. Signed-off-by: Luca Weiss Reviewed-by: Abel Vesa Link: https://patch.msgid.link/20260901-fp4-regulator-supply-v1-2-68288ab70aee@fairphone.com Signed-off-by: Mark Brown

regulator: mp886x: add MP8864 support

2026-09-04T18:12:19+00:00

Jisheng Zhang says: The MP8864 is a 4 A, 21 V synchronous step-down converter. Its register layout and voltage transition handling are compatible with the MP8867, but its selectable switching frequencies are 600 kHz, 850 kHz, 1.1 MHz and 1.6 MHz. Add the compatible and chip-specific switching-frequency table. Link: https://patch.msgid.link/20260901043123.5401-1-jszhang@kernel.org