qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
mmu_man has quit [Ping timeout: 246 seconds]
sbach has quit [Remote host closed the connection]
sbach has joined #u-boot
sakman has quit [Ping timeout: 246 seconds]
rburkholder has quit [Quit: Leaving]
alpernebbi has quit [Ping timeout: 246 seconds]
alpernebbi has joined #u-boot
sakman has joined #u-boot
jclsn has quit [Ping timeout: 245 seconds]
jclsn has joined #u-boot
hanetzer has quit [Ping timeout: 246 seconds]
hanetzer has joined #u-boot
<lvrp16>
marex:
<lvrp16>
i'm just hazarding a guess since I haven't had too much time to debug the issue. the sequence is led gpio bind, led post bind, gpio set, probe after bind, gpio probe
<lvrp16>
led post probe never occurs
<marex>
lvrp16: what is this about ?
<lvrp16>
led default-state never applies after 2022.10
<marex>
2022.10 ?
<marex>
can you bisect the source of this ?
<lvrp16>
doing it now, it might not be 2022.10, I'll debug more. the led post bind happens but the led probe does not until you run the led command. I'll go through the docs and code.
cyrozap has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
cyrozap has joined #u-boot
cyrozap has quit [Client Quit]
cyrozap has joined #u-boot
cyrozap has quit [Client Quit]
cyrozap has joined #u-boot
<lvrp16>
marex: i'm on amlogic platform without spl, the stacktrace is dm_priv_to_rw, dev_get_uclass_plat, led_post_probe. dm_priv_to_rw does not exist since there's no SPL or TPL.
<lvrp16>
so the probe never finished. I guess only platforms with SPL/TPL are tested
<lvrp16>
sorry about the noise, lack of sleep and misread led_gpio_probe as led_post_probe, errors out on uclass_get_dev_by_ofnode -19. stack is uclass_get_dev_by_ofnode, gpio_request_tail, gpio_request_by_name, dev_get_priv, led_gpio_probe. gpio probe is not called before led_gpio_probe. not sure how to create a dependency in DM for led_gpio to depend on gpio.
goliath has joined #u-boot
apritzel has joined #u-boot
sbach has quit [Ping timeout: 246 seconds]
sbach has joined #u-boot
apritzel has quit [Ping timeout: 250 seconds]
mckoan_ is now known as mckoan
<mckoan>
good morning
persmule has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
rainbyte_ is now known as rainbyte
rainbyte has quit [Remote host closed the connection]
<lvrp16>
when the board inits and tries to set the LED state, it cannot find the device. however running the command manually works. I read the docs but couldn't get the heads or tails on how to create a dependency in DM for led-gpios to pinctrl and gpio.
<marex>
lvrp16: youre probing leds before GPIO controller ?
<lvrp16>
marex: That is what the code seems to be doing. Pinctrl and gpio do not seem to be up when gpio_led probes. I don't know how or why it sets that order. Hence I am wondering how it is suppose to work.
<lvrp16>
marex: Is there some dts entries that need to be set on the nodes?
<lvrp16>
marex: as you can see from the logs, gpio_led is not probed since it failed with enodev
<lvrp16>
marex: I would imagine this affect default-state for gpio-leds for all boards, not just mine.
apritzel has joined #u-boot
<marex>
lvrp16: try and add bootph-* tag for one or the other
<marex>
bootph-all I think
<marex>
used to be u-boot,dm-pre-reloc ?
<lvrp16>
marex: I added both to pinctrl and gpio-leds as well as just to pinctrl. same result.
<lvrp16>
marex: do you need the dm debug logs?
<marex>
lvrp16: do those drivers actually get probed ?
<Kwiboo>
lvrp16: marex: looks like meson pinctrl driver bind gpio driver at pinctrl probe time, should probably do that at pinctrl bind so that gpio driver can probe by led