narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
rah has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 256 seconds]
sputnik_ has quit [Ping timeout: 240 seconds]
sputnik_ has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
saintdev has quit [Ping timeout: 244 seconds]
saintdev has joined #linux-amlogic
buzzmarshall has quit [Quit: Leaving]
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-amlogic
sputnik__ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
camus1 has joined #linux-amlogic
kaspter has quit [Ping timeout: 246 seconds]
camus1 is now known as kaspter
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-amlogic
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-amlogic
cmeerw has joined #linux-amlogic
<warpme_> jbrunet: oh finally got audio devices in sm1. Unfortunatelly speaker-test not works:
<warpme_> 5.8rc1 kernel dmesg is like this: https://pastebin.com/17BqsxfK
<warpme_> issue is probably here:
<xdarklight> warpme_: random guess, do you have CONFIG_COMMON_CLK_AXG_AUDIO enabled ?
<warpme_> xdarklight: i think so :-)
<xdarklight> then you may want to check with initcall_debug=1 which drivers are being loaded and which aren't
<xdarklight> initcall_debug=1 is a kernel cmdline parameter
<warpme_> here is dmesg with inintcall_debug=1: https://pastebin.com/eYbt7qft
<xdarklight> there's no "no backend DAIs enabled for" message in that dmesg. where did it come from earlier?
<warpme_> entry "fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0" appears after any attempt of audio usage i.e. by running "speaker-test -c2"
<xdarklight> can you please also pastebin the output of "cat /proc/iomem" ?
<warpme_> here it is:
<xdarklight> OK, that confirms we have the following enabled and loaded: clkc_audio, frddr_a, frddr_b, frddr_c, arb, tdmout_b, tohdmitx
<plntyk> i remember chewitt having similar problems with audio, alsa and no backend DAIs too - he had some change on alsa side too iirc
<xdarklight> it's missing spdifout_b though and not trying to probe it (axg_spdifout_probe) either
<xdarklight> I have zero knowledge about the alsa side
<plntyk> chewitt is active in libreelec - https://github.com/chewitt/alsa-lib/commits/amlogic there are some changes there - dunno if those are required
<warpme_> plntyk: indeed. I already applied alas-lib changes developed by chewitt (cards config and alias.conf from https://github.com/chewitt/alsa-lib/commits/amlogic)
<warpme_> pls see last 3 commits
<plntyk> with the dai channel / alsa stuff - I already wrote sth https://freenode.irclog.whitequark.org/linux-amlogic/2020-05-17 check that old log maybe
<plntyk> i found some example / mentioning of DAI how they supposed to work there
<plntyk> maybe the kernel hw side and connection w. alsa should be more documented for devs if its continuing to be a src of problems
camus1 has joined #linux-amlogic
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
<warpme_> silly me. forgot bout amixer thing. works now!
sputnik_ has quit [Ping timeout: 256 seconds]
<rah> I'm considering buying a Khadas VIM3 but I'm wondering how far I'll get with a mainline kernel
<rah> the .dts file is not clear
<rah> can anyone tell me how I can determine what is and isn't supported?
<xdarklight> rah: http://linux-meson.com/doku.php has a support matrix. the only thing that's specific to the Khadas boards is the standby/etc. MCU - which is not listed in that table
<xdarklight> also mainline GPU drivers are still very much work-in-progress
<rah> xdarklight: aye, I saw that but that matrix is per-SoC rather than per device
<rah> if it's mostly-1:1 between the SoC support and device support that's useful though
<rah> I notice it says "No" for USB though, is there a problem with USB on the G12 SoCs?
<xdarklight> rah: typically it's pretty much "if the SoC support it then there will be support for the boards as well" and if not it's usually mostly an easy copy job
<xdarklight> rah: I have recently tested USB on G12A so that's a "bug" in the support matrix. thanks for reporting, I'll fix that
<rah> no problem
<rah> the thing about the easy copying is that it basically means having to maintain your own kernel fork
<rah> I'd very much prefer to stick with vanilla mainline
<xdarklight> what I meant is you can copy from another device and submit the patch upstream. Khadas VIM is generally good supported though because many devs have one for testing
<xdarklight> (that's valid for VIM, VIM2, VIM3 and VIM3L afaik)
<rah> what I mean is, I'd rather avoid having to upstream things :-)
<rah> but there seems to be very good upstream support as-is which is encouraging
buzzmarshall has joined #linux-amlogic
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
cmeerw has quit [Ping timeout: 260 seconds]
buzzmarshall has joined #linux-amlogic
cmeerw has joined #linux-amlogic
cmeerw has quit [Ping timeout: 246 seconds]
ldevulder_ has joined #linux-amlogic
ldevulder__ has quit [Ping timeout: 256 seconds]