On 10/17/23 08:31, Luca Weiss wrote:
On Mon Oct 16, 2023 at 11:41 PM CEST, Nia Espera wrote:
Hi,
On 10/16/23 15:50, Luca Weiss wrote:
Hi Nia,
On Mon Oct 16, 2023 at 2:47 PM CEST, Nia Espera wrote:
[ ... ]
+&i2c13 {
+ clock-frequency = <100000>;
+ status = "okay";
+
+ fsa4480@42 {
+ compatible = "fcs,fsa4480";
+ reg = <0x42>;
+ mode-switch;
+ orientation-switch;
+ };
+
+ /* Qualcomm PM8008i/PM8008j (?) @ 8, 9, c, d */
Check again in downstream if the @c and @d are actually enabled, at
least they're not on my boards and the PM8008 is only addressable on @8
and @9.
Seems like they all are used on this device; (d) in particular seems to
be needed for the camera.
PM8008 is a I2C-addressable regulator that is just used for camera. But
still if you have some time, double check if really both 8+9 and c+d are
used. For example you could use i2cdetect on the bus, I think the PM8008
shows up without manually flipping some enable GPIO. Or check downstream
dmesg to see what it says, or at runtime in /sys (e.g. in TWRP should be
enough).
It looks like there's something there, though it might not be touched
downstream on this device. dmesg spits out:
[ 2.005455] (3)[9:kworker/u24:0][ 2.005452]@3 qcom,pm8008-chip:
probe of a94000.i2c:pm8008j@c:pm8008-chip@900 failed with error -107
which seems to imply c/d are unused; however, they do show up under
/sys/bus/i2c/devices/9-000[c/d], so I'm not quite sure what to make of it.
