Re: [PATCH 2/3] led: Mark device instance with DM_FLAG_PROBE_AFTER_BIND

2022-04-28 Thread Tom Rini
On Fri, Apr 22, 2022 at 03:15:54PM +0200, Marek Vasut wrote: > Calling device_probe() from uclass .post_bind() callback has all kinds > of odd side-effects, e.g. device instances not being available just yet. > Make use of the DM_FLAG_PROBE_AFTER_BIND instead, mark device instances > which need to

Re: [PATCH 2/3] led: Mark device instance with DM_FLAG_PROBE_AFTER_BIND

2022-04-25 Thread Marek Vasut
On 4/25/22 16:31, Tom Rini wrote: On Fri, Apr 22, 2022 at 03:15:54PM +0200, Marek Vasut wrote: Calling device_probe() from uclass .post_bind() callback has all kinds of odd side-effects, e.g. device instances not being available just yet. Make use of the DM_FLAG_PROBE_AFTER_BIND instead, mark d

Re: [PATCH 2/3] led: Mark device instance with DM_FLAG_PROBE_AFTER_BIND

2022-04-25 Thread Tom Rini
On Fri, Apr 22, 2022 at 03:15:54PM +0200, Marek Vasut wrote: > Calling device_probe() from uclass .post_bind() callback has all kinds > of odd side-effects, e.g. device instances not being available just yet. > Make use of the DM_FLAG_PROBE_AFTER_BIND instead, mark device instances > which need to

Re: [PATCH 2/3] led: Mark device instance with DM_FLAG_PROBE_AFTER_BIND

2022-04-22 Thread Patrice CHOTARD
Hi Marek On 4/22/22 15:15, Marek Vasut wrote: > Calling device_probe() from uclass .post_bind() callback has all kinds > of odd side-effects, e.g. device instances not being available just yet. > Make use of the DM_FLAG_PROBE_AFTER_BIND instead, mark device instances > which need to be probe()d in

[PATCH 2/3] led: Mark device instance with DM_FLAG_PROBE_AFTER_BIND

2022-04-22 Thread Marek Vasut
Calling device_probe() from uclass .post_bind() callback has all kinds of odd side-effects, e.g. device instances not being available just yet. Make use of the DM_FLAG_PROBE_AFTER_BIND instead, mark device instances which need to be probe()d in order to configure the LED default state with this fla