linux-kernel - [PATCH 0/2] regulator: max20086: Fixes chip id and enable gpio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250420-fix-max20086-v1-0-8cc9ee0d5a08@gmail.com>
Date: Sun, 20 Apr 2025 15:28:00 -0300
From: João Paulo Gonçalves <jpaulo.silvagoncalves@...il.com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, 
 Watson Chow <watson.chow@...et.com>
Cc: linux-kernel@...r.kernel.org, 
 João Paulo Gonçalves <jpaulo.silvagoncalves@...il.com>, 
 stable@...r.kernel.org
Subject: [PATCH 0/2] regulator: max20086: Fixes chip id and enable gpio

Hello,

I'm working on integrating a system with a MAX20086 and noticed these
small issues in the driver: the chip ID for MAX20086 is 0x30 and not
0x40. Also, in my use case, the enable pin is always enabled by
hardware, so the enable GPIO isn't needed. Without these changes, the
driver fails to probe.

Signed-off-by: João Paulo Gonçalves <jpaulo.silvagoncalves@...il.com>
---
João Paulo Gonçalves (2):
      regulator: max20086: Fix MAX200086 chip id
      regulator: max20086: Change enable gpio to optional

 drivers/regulator/max20086-regulator.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
---
base-commit: 6fea5fabd3323cd27b2ab5143263f37ff29550cb
change-id: 20250420-fix-max20086-430a63f7a9eb

Best regards,
-- 
João Paulo Gonçalves <jpaulo.silvagoncalves@...il.com>