ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
xvmt has quit [Read error: Connection reset by peer]
xvmt has joined #armlinux
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 248 seconds]
System_Error has quit [Remote host closed the connection]
bangcat has quit [Read error: Connection reset by peer]
jeeeun has quit [Read error: Connection reset by peer]
jeeeun has joined #armlinux
Esmil has quit [Ping timeout: 244 seconds]
Esmil has joined #armlinux
monstr has joined #armlinux
cbeznea_ has joined #armlinux
cbeznea has joined #armlinux
vigneshr has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
nsaenz has joined #armlinux
mriesch has quit [Remote host closed the connection]
nsaenz_ has quit [Remote host closed the connection]
nsaenz has joined #armlinux
<mwalle>
lag: ah sorry, i've noticed that i accidentally missed the dt binding patch in v2 (which was already acked in v1). I'll respin a v3 anyway. Should I post the series with all patches or just the mfd (and dt patch) then?
HerbY_NL has joined #armlinux
<lag>
mwalle: Post them all and I'll cherry-pick the MFD / DT ones
luispm has quit [Ping timeout: 260 seconds]
<mwalle>
lag: thx will do
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
nsaenz_ has joined #armlinux
nsaenz has quit [Ping timeout: 244 seconds]
<broonie>
mwalle: Probably the easiest thing is a tag with the MFD bits and then I can apply the regulator patches?
<mwalle>
broonie: yep, that's the plan
<mwalle>
btw does anyone knows the difference between the bus modalias and the uevent MODALIAS variable regarding automatic module loading. It seems that for the (relatively) new nvmem layouts bus there is no modalias. I've added the MODALIAS variable to the uevent and module loading now works, but I wonder when the modalias sysfs file is used, or whether it is used at all
atorgue__ has joined #armlinux
<javierm>
mwalle: AFAIK for module autoloading the modalias info in the .ko and the uevent modalias are the important bits. The sysfs is mostly for information
atorgue1 has quit [Ping timeout: 252 seconds]
<javierm>
mwalle: that is, there could be that a DEVICE_ATTR_RO(modalias) and modalias_show() callback isn't present, but will work as long as there's a struct bus_type .uevent defined
<javierm>
and a MODULE_DEVICE_TABLE() defined for the driver of course
atorgue1 has joined #armlinux
<mwalle>
javierm: ok thanks
atorgue__ has quit [Read error: Connection reset by peer]
<javierm>
mwalle: I might be wrong though, but that's my understanding of how it works :)
<broonie>
The sysfs is for bootsrapping isn't it?
<javierm>
broonie: what do you mean by bootstrapping in this context ?
<broonie>
During startup.
<javierm>
broonie: hmm, good question. I don't know tbh
HerbY_NL has joined #armlinux
luispm has joined #armlinux
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
nsaenz_ has quit [Remote host closed the connection]