On 6/28/24 9:32 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
@@ -473,8 +483,6 @@ static int regulator_pre_probe(struct udevice *dev)
-ENODATA);
uc_pdata->max_uA = dev_read_u32_default(dev, "regulator-max-microamp",
Hi Simon,
This is reading a lot of DT stuff very early, which may be slow. It is
also reading from the DT in the bind() step which we sometimes have to
do, but try to avoid.
Could we set up the livetree pre-bind? What about MMU? On armv8 at least
this would have a huge impact on performance.
Hi Marek,
On Thu, 27 Jun 2024 at 17:05, Marek Vasut wrote:
>
> On 6/27/24 10:37 AM, Simon Glass wrote:
> > Hi Marek,
>
> Hi,
>
> [...]
>
> >> ---
> >> drivers/power/regulator/regulator-uclass.c | 22 +++---
> >> 1 file changed, 15 insertions(+), 7 deletions(-)
> >>
> >> diff
Hi Caleb,
On Fri, 28 Jun 2024 at 01:09, Caleb Connolly wrote:
>
>
>
> On 27/06/2024 11:26, Simon Glass wrote:
> > Hi Caleb,
> >
> > On Thu, 27 Jun 2024 at 09:48, Caleb Connolly
> > wrote:
> >>
> >>
> >>
> >> On 27/06/2024 10:37, Simon Glass wrote:
> >>> Hi Marek,
> >>>
> >>> On Thu, 27 Jun
On 27/06/2024 11:26, Simon Glass wrote:
Hi Caleb,
On Thu, 27 Jun 2024 at 09:48, Caleb Connolly wrote:
On 27/06/2024 10:37, Simon Glass wrote:
Hi Marek,
On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
In case a regulator DT node contains regulator-always-on or regulator-boot-on
On 6/27/24 10:37 AM, Simon Glass wrote:
Hi Marek,
Hi,
[...]
---
drivers/power/regulator/regulator-uclass.c | 22 +++---
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/drivers/power/regulator/regulator-uclass.c
b/drivers/power/regulator/regulator-uclass.c
Hi Svyatoslav,
On Thu, 27 Jun 2024 at 11:34, Svyatoslav Ryhel wrote:
>
> чт, 27 черв. 2024 р. о 12:26 Simon Glass пише:
> >
> > Hi Svyatoslav,
> >
> > On Thu, 27 Jun 2024 at 10:09, Svyatoslav wrote:
> > >
> > >
> > >
> > > 27 червня 2024 р. 11:48:46 GMT+03:00, Caleb Connolly
> > >
чт, 27 черв. 2024 р. о 12:26 Simon Glass пише:
>
> Hi Svyatoslav,
>
> On Thu, 27 Jun 2024 at 10:09, Svyatoslav wrote:
> >
> >
> >
> > 27 червня 2024 р. 11:48:46 GMT+03:00, Caleb Connolly
> > написав(-ла):
> > >
> > >
> > >On 27/06/2024 10:37, Simon Glass wrote:
> > >> Hi Marek,
> > >>
> > >>
Hi Caleb,
On Thu, 27 Jun 2024 at 09:48, Caleb Connolly wrote:
>
>
>
> On 27/06/2024 10:37, Simon Glass wrote:
> > Hi Marek,
> >
> > On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
> >>
> >> In case a regulator DT node contains regulator-always-on or
> >> regulator-boot-on
> >> property, make
Hi Svyatoslav,
On Thu, 27 Jun 2024 at 10:09, Svyatoslav wrote:
>
>
>
> 27 червня 2024 р. 11:48:46 GMT+03:00, Caleb Connolly
> написав(-ла):
> >
> >
> >On 27/06/2024 10:37, Simon Glass wrote:
> >> Hi Marek,
> >>
> >> On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
> >>>
> >>> In case a
27 червня 2024 р. 11:48:46 GMT+03:00, Caleb Connolly
написав(-ла):
>
>
>On 27/06/2024 10:37, Simon Glass wrote:
>> Hi Marek,
>>
>> On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
>>>
>>> In case a regulator DT node contains regulator-always-on or
>>> regulator-boot-on
>>> property, make
On 27/06/2024 10:37, Simon Glass wrote:
Hi Marek,
On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
In case a regulator DT node contains regulator-always-on or regulator-boot-on
property, make sure the regulator gets correctly configured by U-Boot on start
up. Unconditionally probe such
Hi Marek,
On Thu, 27 Jun 2024 at 00:57, Marek Vasut wrote:
>
> In case a regulator DT node contains regulator-always-on or regulator-boot-on
> property, make sure the regulator gets correctly configured by U-Boot on start
> up. Unconditionally probe such regulator drivers. This is a preparatory
13 matches
Mail list logo