нд, 1 груд. 2024 р. о 17:49 Simon Glass <s...@chromium.org> пише: > > Hi Svyatoslav, > > On Sun, 1 Dec 2024 at 08:24, Svyatoslav Ryhel <clamo...@gmail.com> wrote: > > > > нд, 1 груд. 2024 р. о 17:23 Simon Glass <s...@chromium.org> пише: > > > > > > Hi Svyatoslav, > > > > > > On Sun, 1 Dec 2024 at 08:20, Marek Vasut <ma...@denx.de> wrote: > > > > > > > > On 12/1/24 4:05 PM, Svyatoslav Ryhel wrote: > > > > > > > > [...] > > > > > > > > >> @@ -288,7 +289,8 @@ static int > > > > >> dm_test_power_regulator_autoset(struct unit_test_state *uts) > > > > >> * Expected output state: uV=1200000; uA=200000; output > > > > >> enabled > > > > >> */ > > > > >> platname = regulator_names[BUCK1][PLATNAME]; > > > > >> - ut_asserteq(-EALREADY, regulator_autoset_by_name(platname, > > > > >> &dev_autoset)); > > > > >> + ut_asserteq(-EALREADY, > > > > >> + regulator_autoset_by_name(platname, > > > > >> &dev_autoset)); > > > > >> > > > > >> /* Check, that the returned device is proper */ > > > > >> ut_assertok(regulator_get_by_platname(platname, &dev)); > > > > >> -- > > > > >> 2.43.0 > > > > >> > > > > > > > > > > It seems that I have found a fix for this issue. Simon, please test > > > > > this commit > > > > > https://gitlab.com/clamor-s/u-boot/-/commit/6149722aa48f84d9ea037ae990141a231106244e > > > > > > > > So this regulator problem was a tegra platform specific issue after all. > > > > > > > > Nice find, thanks ! > > > > > > That's great! Are you planning to send a patch? > > > > > > Regards, > > > Simon > > > > I planned pull it directly via tegra custodian tree as an important > > fix. Please confirm if it fixes Nyan. Thanks > > You should send a patch since pull requests cannot contain patches > that have not been posted :-) > > If it has been posted, please can you send the link and I will test it. > > Regards, > Simon
Alright
