06:55 <aka_[m]> seems they differ just a bit

08:12 <DylanVanAssche> Anyone who knows QCOM BAM DMA? I'm trying to figure out where mainline gets the number of `slimbam $NUMBER` from (property `dma`) and DMA names (property `dma-names`)? https://lore.kernel.org/linux-devicetree/20200313135427.GN4885@vkoul-mobl/T/#mfc68bd8e355191aa842f39e969c0921426aa7be0

08:12 <DylanVanAssche> I cannot find where this comes from in downstream.

08:21 <aka_[m]> Dylan Van Assche: which soc you worked on?

08:21 <aka_[m]> 8996?

08:22 <DylanVanAssche> SDM845, I want to enable the second SLIMBus controller for Bluetooth HFP with WCN3990

08:22 <DylanVanAssche> The numbers in that patch are 3,4,5,6. No idea where these are coming from.

08:26 <aka_[m]> Dylan Van Assche: i would look into machine driver

08:40 <aka_[m]> or slimbus driver/bam alone

08:46 <aka_[m]> Dylan Van Assche: wouldn't it fly to add some logging into sps driver on downstream to log you dest_pipe_index ?

08:46 <aka_[m]> i believe these slimbam_dma <number> and number might be pipe index

08:53 <aka_[m]> you probably want 7 and 8

08:54 <DylanVanAssche> aka_: Thanks for the hints! Will have a look. I just couldn't understand from the docs what it was... How do you know this? 7 and 8 would match the SLIMBus names TX/RX 7/8 so that could be right

08:54 <aka_[m]> thats what im thinking too

08:55 <aka_[m]> based on sdn_soc_dai_link from sdm845.c

08:56 <aka_[m]> its still messy because names for dma channels on sdm845 doesn't cover much with snd_soc_dai_link msm_tavil_be_dai_links[]

08:58 <DylanVanAssche> Yeah but the devicetree bindings docs do not explain this right? Maybe I misser it but I read various docs there without finding a clue :p

08:59 <aka_[m]> srinik:

09:00 <DylanVanAssche> (missing docs happens, it is fine. I'm just a bit lost as a noob regarding kernel development where to look in the src, thanks for the hints!)

09:11 <z3ntu> All of this is a bit scarcely documented if at all, I'm also often lost in this