Devicetree
 help / color / mirror / Atom feed
From: Jesse Casco <jesse.casco@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: [RFC PATCH] arm64: dts: qcom: glymur-asus-zenbook-a16: Describe BOB1 and the IR emitter
Date: Sat, 14 Nov 2026 11:52:21 -0500	[thread overview]
Message-ID: <20261114165221.70310-1-jesse.casco@gmail.com> (raw)

PMH0101 BOB1 feeds the PM8010 camera LDOs and the PMH0101 flash module.
Describe it, and wire the IR illuminator: flash channels 1 and 4 ganged,
350 mA torch, 700 mA flash, attached to the HM1092 via flash-leds.

Values:
- channels 1+4, 350 mA torch, 700 mA flash, 1280 ms timeout: Windows
  LEDFLASH configuration (FlashLED_1)
- BOB1 3.384-3.512 V: within the AOP OTP limits for B1B_E0
  (3.296-3.520 V); BOB2 is not populated

Signed-off-by: Jesse Casco <jesse.casco@gmail.com>
---
Konrad, this goes on top of your A16 PM8010 and IR camera commits in
qcom-laptops; feel free to fold it in. Tested on a 7.3 kernel with the
same DT: ir:flash probes with no faults and lights the HM1092 scene.

 .../qcom/glymur-asus-zenbook-a16-ux3607oa.dts | 29 +++++++++++++++++--
 1 file changed, 27 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a16-ux3607oa.dts b/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a16-ux3607oa.dts
index c2ecabb3..75018ccc 100644
--- a/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a16-ux3607oa.dts
+++ b/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a16-ux3607oa.dts
@@ -379,6 +379,17 @@
 		compatible = "qcom,pmh0101-rpmh-regulators";
 		qcom,pmic-id = "B_E0";
 
+		vdd-l6-l7-supply = <&vreg_bob1_e0>;
+		vdd-l8-l9-supply = <&vreg_bob1_e0>;
+
+		/* B2B_E0 (BOB2) is not populated on this board */
+		vreg_bob1_e0: bob1 {
+			regulator-name = "vreg_bob1_e0";
+			regulator-min-microvolt = <3384000>;
+			regulator-max-microvolt = <3512000>;
+			regulator-initial-mode = <RPMH_REGULATOR_MODE_AUTO>;
+		};
+
 		vreg_l1b_e0: ldo1 {
 			regulator-name = "vreg_l1b_e0";
 			regulator-min-microvolt = <1800000>;
@@ -624,6 +635,7 @@
 
 		reset-gpios = <&tlmm 109 GPIO_ACTIVE_LOW>;
 
+		flash-leds = <&ir_led>;
 		leds = <&privacy_led>;
 		led-names = "privacy";
 
@@ -751,10 +763,10 @@
 
 		reset-gpios = <&tlmm 106 GPIO_ACTIVE_LOW>;
 
-		// vdd-l3-l4-supply = <&vreg_bob>;
+		vdd-l3-l4-supply = <&vreg_bob1_e0>;
 		// vdd-l5-supply = <&vreg_bob>;
 		// vdd-l6-supply = <&vreg_bob>;
-		// vdd-l7-supply = <&vreg_bob>;
+		vdd-l7-supply = <&vreg_bob1_e0>;
 
 		gpio-controller;
 		#gpio-cells = <2>;
@@ -1037,6 +1049,19 @@
 	wake-gpios = <&tlmm 154 GPIO_ACTIVE_LOW>;
 };
 
+&pmh0101_flash {
+	status = "okay";
+
+	ir_led: led-0 {
+		function = LED_FUNCTION_FLASH;
+		color = <LED_COLOR_ID_IR>;
+		led-sources = <1>, <4>;
+		led-max-microamp = <350000>;
+		flash-max-microamp = <700000>;
+		flash-max-timeout-us = <1280000>;
+	};
+};
+
 &pmh0101_gpios {
 	nvme_reg_en: nvme-reg-en-state {
 		pins = "gpio14";

base-commit: 2010e0d9557fe1d37d04f13e539adf24cbb785f6
-- 
2.56.0


                 reply	other threads:[~2026-11-14 16:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261114165221.70310-1-jesse.casco@gmail.com \
    --to=jesse.casco@gmail.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=nihal.gupta@oss.qualcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox