[PATCH 1/4] power: regulator: Trigger probe of regulators which are always-on or boot-on

[Marek Vasut]

On 8/1/24 2:28 AM, Marek Vasut wrote:
> On 7/29/24 1:55 PM, Svyatoslav Ryhel wrote:
> 
> [...]
> 
>>>>> What is the problem you observe on tegra 3 ?
>>>> i2c line fails since it probes in spl with your patch, but it does not
>>>> relocate and then probes once more after relocation. Probe fails along
>>>> with all devices on same line.
>>>
>>> Could it be that you either have to:
>>> - Add DM_I2C to tegra 3 SPL
>>> - Remove bootph-* from DT to remove the regulator node from SPL
>>> - /delete-property/ regulator-always-on; and /delete-property/
>>> regulator-boot-on; in -u-boot.dtsi to prevent the regulator from being
>>> enabled in SPL ?
>>>
>> Obviously NO, you propose nonsense. Same dts is used for both stages.
> 
> DT source yes, DT blob likely no.
> 
>> And I have to add hack-ish stuff just because you wanna introduce code
>> which causes known regressions.
> 
> I am trying to understand what problem there is on tegra 3, but it is 
> still not clear to me.
> 
> Is the problem somehow related to PMICs (?) being probed in SPL (?) 
> because they have regulators (?) which are marked as regulator-always-on 
> ? If so, then this is correct behavior, and if this is not desired in 
> SPL, then you can remove this property from SPL DT in -u-boot.dtsi using 
> /delete-property/ .
> 
> [...]
> 
>> "We must not probe things as we go. There might be other
>> dependencies not yet bound. It may also take some time. This is not
>> following driver model design, sorry.
>>
>> So please think of a way to do this properly."
> 
> What is this quote about ? Where is this from ?

What is the problem with Tegra 3 and this patchset ?

Can you please explain that so this patchset can move forward ?

Thank you