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: 264 seconds]
heat_ has quit [Remote host closed the connection]
heat_ has joined #armlinux
heat has joined #armlinux
heat_ has quit [Read error: Connection reset by peer]
System_Error has quit [Remote host closed the connection]
Lockesmith has quit [Remote host closed the connection]
Lockesmith has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 246 seconds]
heat has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 264 seconds]
<diederik>
ukleinek: would setting dma-names property @ rk3566-quartz64-b.dts#n655 (uart node for bluetooth (and wifi)) be safe?
<diederik>
or more general: given that enabling dma-names for (only?) bluetooth is fine, should it then be set on the board level (and not SoC level)?
<ukleinek>
diederik: It should. But I consider this strange. With the POV that dts is hw description there is no reason not to add it to the soc.dtsi.
<ukleinek>
diederik: the real problem then has to be fixed somewhere else
<diederik>
ukleinek: ok, thanks. But wouldn't every board need to have BT on the same UART for that? (uart1 on the case of Q64-B)
<ukleinek>
diederik: the decision to use or not use DMA should be configured somewhere else.
<diederik>
ok, thanks. I'll try other things to get BT working properly on my Q64-B first then
<ukleinek>
the problem is there is no canonical way to configure that. But adding the dma-names property to the dts should make the driver use it.
<wens>
and also revert commit 22a9d9585812 ("dmaengine: pl330: issue_pending waits until WFP state")
<wens>
diederik: ^
<ukleinek>
oh right
<diederik>
wens: thanks :) I'm about to build a 6.7.7 (with custom patches), so I'm not affected now. But will keep it in mind when I switch to 6.8+
<ukleinek>
<advertising>With barebox as bootloader you could just do something like of_property -s -f serial2 dma-names "tx","rx" to modify the dtb accordingly</advertising>
<diederik>
I was mostly worried about getting smoke from my device in case I really shouldn't set that property (there) ;)
<ukleinek>
diederik: I'd be optimistic there
<ukleinek>
FTR: The right syntax is: of_property -s -f serial2 dma-names tx rx
<diederik>
I may try it in the future, but first I'll try the improvements I have now (like PINCTRL_ROCKCHIP=y) and possibly should try whether I have the firmware files from RPi/RPF on it
<diederik>
I had/have it working properly on Rock64, so I need to investigate what's different
apritzel has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 272 seconds]
<wens>
fwiw BT probes and loads firmware fine on my quartz64-b
<diederik>
Yeah, I concluded that earlier, hence my renewed interest in getting it working :)
<diederik>
In my last attempt the controller did load and seem to work, but I was unable to make a connection (to my phone)
headless has joined #armlinux
apritzel has quit [Ping timeout: 264 seconds]
headless has quit [Quit: Konversation terminated!]