From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpout-03.galae.net (smtpout-03.galae.net [185.246.85.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E08C42F83D3; Tue, 16 Sep 2025 10:24:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.85.4 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758018259; cv=none; b=olmghwwq42mPtfPhDB970yamSWsnaSDVT1tVvePsSxRw0B8ZOu66SO/4P1b7eYIQf3MsCRW8h4ELAX5oUo1wMEaF9SJKqQ/w/vwxBmICt/Cyt9ol8kEpwUzMewq5RlMviZ/3+qUZRBho7JVylmembis3uNsIbjmoCcghg9tFWxo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758018259; c=relaxed/simple; bh=UU/Il9qgUqeyEMGZumr+Zlcvwvbdz3o+XMKlW396uVY=; h=From:Subject:Date:Message-Id:MIME-Version:Content-Type:To:Cc; b=jOf8aCGm6REJBhyvLMjc3/nzCMGh5MXXA3n1POaJOXVetlgPLGLqkp0PQpG0X+F6iQHAufXR+fbkAVCH37MtK6HPefOhRI1OF5vqgRwd7LSeWxRRX2QMmS0wLBrUP2DPP7arbmsBN5EwetMS+p49ZHL44/EIFJVBzImYdV69BjI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=JYGvdWVU; arc=none smtp.client-ip=185.246.85.4 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="JYGvdWVU" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-03.galae.net (Postfix) with ESMTPS id 349914E40BB5; Tue, 16 Sep 2025 10:24:15 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 096F26061E; Tue, 16 Sep 2025 10:24:15 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 15D78102F16D4; Tue, 16 Sep 2025 12:24:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1758018253; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding; bh=4KzDfp80Dzw2CTpAAfNCIAbjQ4ZVlMxWuyH9CtD5l14=; b=JYGvdWVU3yZsRdAlkLHmu8xkLWvKSaUXtFBeQmU7FDgFL+LHfEPMfrtbbn3jd+t4fL435U 4OcypYk8D1VCrUyk6WWODX4GCJ9gD+XM0ksCbw6bLTognSaQyfbSzDjYUYuWqA/nuq0KUQ BTq2ato1jRfE7eN/98NzIjkxn9P0/gnV4cPNiWeoQ6T69YGGbkhA1zR6tKYagi80nNT9bG MGBmHJtYRDfvLSknK4tUZOdDX1YN+B/T4VqnT2U3FlH3uSxrsP5hDL87Ngta+0K64GOm38 myv3meHgL3qyQ3PnbEIUx7hTgXKcvWvPC1QhpAvUoQY7vNOw8evh2vMCckWLFg== From: Romain Gantois Subject: [PATCH 0/4] Add support for the LTM8054 voltage regulator Date: Tue, 16 Sep 2025 12:24:05 +0200 Message-Id: <20250916-ltm8054-driver-v1-0-fd4e781d33b9@bootlin.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-B4-Tracking: v=1; b=H4sIAMY6yWgC/x3MQQqAIBBA0avErBNUtKKrRAuxsQbKYowIxLsnL d/i/wwJmTDB2GRgfCjRGStU24DfXFxR0FINWmorez2I/T4GaY1YmB5koZQPzvRGyc5CjS7GQO8 /nOZSPhbOHExgAAAA X-Change-ID: 20250728-ltm8054-driver-11cfa4741065 To: Liam Girdwood , Mark Brown , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Jonathan Cameron , David Lechner , =?utf-8?q?Nuno_S=C3=A1?= , Andy Shevchenko Cc: Thomas Petazzoni , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-iio@vger.kernel.org, Romain Gantois X-Mailer: b4 0.14.2 X-Last-TLS-Session-Version: TLSv1.3 Hello everyone, This series adds initial support of the Linear Technology LTM8054 voltage regulator. The driver supports a fixed voltage and a tunable output current limit using a DAC-controlled pin. I'd say that the only unusual part of this series is the usage of the IIO consumer API in a regulator driver. I think this makes sense here, since the regulator driver has to access a DAC to read/set the output current limit. Since the regulator driver writes microvolts and the IIO consumer API takes millivolts, the reads and writes to the CTL DAC have to be scaled by a factor of 1000. Scaled reads are already supported in IIO, but scaled writes are not, which is why I've implemented them in patch 2/4. Please let me know what you think. Thanks, Romain Signed-off-by: Romain Gantois --- Romain Gantois (4): regulator: dt-bindings: Add Linear Technology LTM8054 regulator iio: add processed write API regulator: Support the LTM8054 voltage regulator regulator: ltm8054: Support output current limit control .../bindings/regulator/lltc,ltm8054.yaml | 77 +++++++ MAINTAINERS | 6 + drivers/iio/inkern.c | 99 +++++++++ drivers/regulator/Kconfig | 9 + drivers/regulator/Makefile | 1 + drivers/regulator/ltm8054-regulator.c | 229 +++++++++++++++++++++ include/linux/iio/consumer.h | 17 ++ 7 files changed, 438 insertions(+) --- base-commit: f87c2b34768828c4ff535ba7d50dd938838caab9 change-id: 20250728-ltm8054-driver-11cfa4741065 Best regards, -- Romain Gantois