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
apritzel has quit [Ping timeout: 245 seconds]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #armlinux
Tokamak has quit [Quit: Textual IRC Client: www.textualapp.com]
amitk has joined #armlinux
apritzel has joined #armlinux
amitk has quit [Ping timeout: 268 seconds]
sudeepholla_ has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
sudeepholla_ has quit [Ping timeout: 245 seconds]
sudeepholla_ has joined #armlinux
headless has joined #armlinux
Pali has joined #armlinux
apritzel has joined #armlinux
headless_ has joined #armlinux
headless has quit [Ping timeout: 268 seconds]
headless_ has quit [Client Quit]
apritzel has quit [Ping timeout: 245 seconds]
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #armlinux
djrscally has joined #armlinux
djrscally has quit [Ping timeout: 252 seconds]
SallyAhaj has quit [Remote host closed the connection]
<marex> hmmm, is the tusb320 driver really supposed to be extcon ?
<marex> it looks more like a type-c power controller
SallyAhaj has joined #armlinux
apritzel has joined #armlinux
<marex> of course ... typec_pwr_opmode matches well to what this tusb320 reports ... extcon doesn't, sigh
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
prabhakarlad has joined #armlinux
Misotauros has quit [Ping timeout: 245 seconds]
Misotauros has joined #armlinux
headless has joined #armlinux
apritzel has joined #armlinux
balrog has quit [Quit: Bye]
balrog has joined #armlinux
headless has quit [Quit: Konversation terminated!]
shailangsa has quit [Ping timeout: 240 seconds]
SallyAhaj has quit [Remote host closed the connection]
elastic_dog has quit [Ping timeout: 244 seconds]
shailangsa has joined #armlinux
elastic_dog has joined #armlinux
apritzel has quit [Ping timeout: 268 seconds]