edwinistrator2 has quit [Ping timeout: 255 seconds]
edwinistrator27 is now known as edwinistrator2
Clamor has quit [Ping timeout: 264 seconds]
Clamor has joined #u-boot
f_ is now known as funderscore
funderscore is now known as f_
frieder has quit [Remote host closed the connection]
prabhakarlad has quit [Ping timeout: 250 seconds]
jfsimon1981 has joined #u-boot
prabhakar has quit [Ping timeout: 255 seconds]
<calebccff>
is there a "correct" way to handle multiple device being bound to a single DT node? Currently the best "solution" I've found is to have some UCLASS_NOP device which binds the child drivers, but it gets really complicated when trying to avoid duplicated platform data configuration (and ensuring there's no UAFs)...
<calebccff>
My current approach is stuffing the common data inside dev->plat_ and doing dev_set_plat() for each child device after binding it. This differentiates it from private data at least
<calebccff>
but in the case of the qcom_pmic_gpio driver it also breaks the assumption that dev->parent will be the pmic device (requires for reading/writing on the SPMI bus)
<calebccff>
I guess that's a limitation of UCLASS_PMIC though
gsz has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
gsz has quit [Quit: leaving]
zkrx has quit []
zkrx has joined #u-boot
F0rTex has joined #u-boot
goliath has joined #u-boot
jclsn has quit [Quit: WeeChat 4.1.2]
jclsn has joined #u-boot
jclsn has quit [Client Quit]
jclsn has joined #u-boot
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 264 seconds]
rvalue- is now known as rvalue
ezulian_ has quit [Ping timeout: 264 seconds]
jfsimon1981 has quit [Remote host closed the connection]