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
jlinton has joined #armlinux
matthiasbgg[m] has quit [Ping timeout: 240 seconds]
mvaittin has quit [Ping timeout: 252 seconds]
a3f has quit [Ping timeout: 240 seconds]
scosu[m] has quit [Ping timeout: 256 seconds]
shoragan[m] has quit [Ping timeout: 248 seconds]
mripard has quit [Ping timeout: 260 seconds]
amstan has quit [Ping timeout: 260 seconds]
psydroid has quit [Ping timeout: 260 seconds]
leming has quit [Ping timeout: 276 seconds]
Pali has quit [Ping timeout: 240 seconds]
Norkle has quit [Remote host closed the connection]
Norkle has joined #armlinux
leming has joined #armlinux
shailangsa_ has quit []
scosu[m] has joined #armlinux
matthiasbgg[m] has joined #armlinux
psydroid has joined #armlinux
mvaittin has joined #armlinux
shoragan[m] has joined #armlinux
shailangsa has joined #armlinux
mripard has joined #armlinux
a3f has joined #armlinux
amstan has joined #armlinux
Xogium_ has joined #armlinux
Xogium has quit [Ping timeout: 260 seconds]
Xogium_ is now known as Xogium
bps has joined #armlinux
bps has quit [Changing host]
bps has joined #armlinux
<sboyd>
vireshk: this relates to some opp tables where two clks scale together. OPP core doesn't let the driver tell it which clk to use?
<sboyd>
I recall this discussion from many years ago
<marex>
sboyd: oh hello, how is the 900 patch pile going ?
<marex>
sboyd: any news on critical-clock ?
bps has quit [Ping timeout: 276 seconds]
<vireshk>
sboyd, I don't remember such platform support being merged. The core at least thinks there is just one clk available
<vireshk>
sboyd, please respond to the thread if you can. thanks.
archetech has joined #armlinux
Tokamak has quit [Ping timeout: 240 seconds]
Tokamak has joined #armlinux
<tmlind>
ardb, arnd: looks like am335x is also seeing some vmap stack issues, see thread "am335x: 5.18.x: system stalling"
luispm has joined #armlinux
guillaume_g has joined #armlinux
luispm has quit [Ping timeout: 240 seconds]
prabhakarlad has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Read error: Connection reset by peer]
nsaenz has joined #armlinux
apritzel has joined #armlinux
luispm has joined #armlinux
Pali has joined #armlinux
headless has joined #armlinux
djrscally has joined #armlinux
<arnd>
tmlind: I replied to the thread now, but I didn't see an obvious bug this time
<tmlind>
arnd: ok thanks
<tmlind>
hmm the original mail says it happens with a usb adapter.. so musb or cppi41 dma
alexels has joined #armlinux
<arnd>
tmlind: I think for USB DMA, the problem is usually in the USB device driver, not the host controller driver.
<arnd>
it says usb-to-can, any idea which driver that is?
<arnd>
I see 9 separate drivers listed in drivers/net/can/usb/Kconfig
<tmlind>
arnd: oh i thought it was some usb-to-can dongle?
<tmlind>
then again am335x should have integrated can too..
<arnd>
tmlind: the way USB drivers work is that they pass a buffer by virtual address to the USB subsystem, which then does the dma_map_single() call on the buffer. If the usb-to-can adapter passes a buffer to a stack variable, it breaks
<arnd>
it could also be a usb-serial adapter with a serial CAN adapter behind it I think, in this case the usb-serial drvier would be the likely cause of the bug
<tmlind>
yeah so it seems
<arnd>
I looked at the usb-can drivers now, most of them seem totally fine
<arnd>
the first bug I see is in kvaser_usb_hydra_get_software_info(), which puts a 'struct kvaser_cmd' on the stack and waits for the reply
headless has quit [Quit: Konversation terminated!]
<arnd>
no, nevermind, it does another copy, looks like someone found the problem even before it got merged into mainline, but the original design was broken and the workaround was a bit clumsy
<tmlind>
ok
archetech has quit [Quit: Konversation terminated!]
monstr has joined #armlinux
<hanetzer>
maz: I can confirm dtc does not seem to understand enums.
<hanetzer>
at least, the dtc being used by u-boot (does it use system dtc or in tree?)
<hanetzer>
yeh, its the one in tree.
iivanov has quit [Quit: Leaving...]
Amit_T has joined #armlinux
CounterPillow has quit [Quit: Bye.]
CounterPillow has joined #armlinux
CounterPillow has quit [Client Quit]
CounterPillow has joined #armlinux
CounterPillow has quit [Client Quit]
CounterPillow has joined #armlinux
CounterPillow has quit [Client Quit]
CounterPillow has joined #armlinux
Turingtoast has joined #armlinux
<broonie>
hanetzer: DTC uses cpp
<hanetzer>
broonie: yeh, aware.
<hanetzer>
just think it would be useful, less typing, and less chance of fudging up if you are adding more numbered, for example clocks, to the header
<broonie>
Surely more chance of messing up (eg, add things in alphabetic order)?
Turingtoast has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
geertu has quit [Ping timeout: 260 seconds]
geertu has joined #armlinux
iivanov has joined #armlinux
iivanov has quit [Read error: Connection reset by peer]
iivanov has joined #armlinux
<hanetzer>
I don't follow.
<broonie>
If you add something to the middle of an enum you renumber all the constants after it.
<hanetzer>
yeah. thing is, as far as I've seen, the numbers given in include/dt-bindings/*/*.h are never used per se.
sszy has joined #armlinux
<hanetzer>
you use it <&phandle MACRO> in the dts/i and just use MACRO in the driver source
<broonie>
They're ABI, the numbers need to be the same in both the DT and the kernel (and in some cases they are defined such that they can just be passed straight through to hardware).
<hanetzer>
oh, so is renumbering after the fact not allowed, enum or define?
<broonie>
Yeah, the numbering should be static.
<hanetzer>
noted.
<geertu>
hanetzer: include/dt-bindings/*/*.h is append-only
<hanetzer>
gotcha. I'll keep that in mind.
* hanetzer
will have to space out a bit to keep things in a sensible order, then.
<hanetzer>
is 0 a valid number? I don't think I've seen it used tbh.
torez has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
luispm has quit [Ping timeout: 240 seconds]
luispm has joined #armlinux
jlinton has quit [Quit: Client closed]
luispm has quit [Ping timeout: 252 seconds]
luispm has joined #armlinux
luispm has quit [Ping timeout: 246 seconds]
luispm has joined #armlinux
<geertu>
hanetzer: yes it is
jlinton has joined #armlinux
jlinton has quit [Quit: Client closed]
c1728p9 has joined #armlinux
sszy has quit [Ping timeout: 260 seconds]
guillaume_g has quit [Quit: Konversation terminated!]
alexels has quit [Quit: WeeChat 3.5]
headless has joined #armlinux
nsaenz has quit [Quit: Leaving]
monstr has quit [Remote host closed the connection]
luispm has quit [Quit: Leaving]
apritzel has quit [Ping timeout: 256 seconds]
Turingtoast has joined #armlinux
Turingtoast has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
nsaenz has joined #armlinux
Amit_T has quit [Remote host closed the connection]
apritzel has joined #armlinux
qyousef has quit [Quit: WeeChat 2.8]
qyousef has joined #armlinux
headless has quit [Quit: Konversation terminated!]
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
iivanov has quit [Ping timeout: 256 seconds]
palmer has quit [Remote host closed the connection]