On 6/21/25 9:31 PM, cristian_ci wrote:
> On Saturday, June 21st, 2025 at 12:17, Konrad Dybcio
> <konrad.dyb...@oss.qualcomm.com> wrote:
>>> +
>>> +&sdhc_1 {
>>> + vmmc-supply = <&pm8953_l8>;
>>> + vqmmc-supply = <&pm8953_l5>;
>>
>>
>> you should add regulator-allow-set-load to these vregs
>
> So, do you mean I should add 'regulator-allow-set-load' property to
> 'pm8953_l5' and 'pm8953_l8' regulators? If so, should I do that for
> 'pm8953_l11' and 'pm8953_l12' regulators too (sdhc_2)?
Yes
>>> +&tlmm {
>>> + gpio-reserved-ranges = <0 4>,
>>
>>
>> These GPIOs correspond to I2C/SPI_1
>>
>> <135 4>;
>>
>>
>> And these correspond to I2C/SPI_7
>>
>> Without much more knowledge, I would guesstimate one of them is
>> for a fingerprint reader and the other for NFC eSE
>>
>> Konrad
>
> I made that check in past and, while it looks like 'gpio16' and 'gpio17' are
> assigned to nfc pinctrl (though, nfc appears not to be implemented in this
> device, considering also the lack of 'phandle' for such pinctrls) in
> downstream dts, the devicetree pinctrl still doesn't mentions the gpios
> associated with the fingerprint node (which is, instead, implemented in this
> device). So, I'm not able to verify if gpios 0-3 and gpios 135-138 are
> related to fingerprint and secure element, respectively.
If we can't tell, then we can't tell, it's ok
Konrad
