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
wildea01 has quit [Ping timeout: 276 seconds]
wildea01 has joined #linux-amlogic
Elpaulo1 has joined #linux-amlogic
Elpaulo has quit [Ping timeout: 264 seconds]
Elpaulo1 is now known as Elpaulo
sputnik_ has quit [Ping timeout: 240 seconds]
sputnik__ has joined #linux-amlogic
sputnik__ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
random_yanek has quit [Read error: Connection reset by peer]
random_yanek has joined #linux-amlogic
Darkmatter66 has quit [Quit: ZNC 1.7.4 - https://znc.in]
Darkmatter66 has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
tlwoerner has quit [Excess Flood]
tlwoerner has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 268 seconds]
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik__ has quit [Ping timeout: 240 seconds]
sputnik_ has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
tlwoerner has quit [Ping timeout: 240 seconds]
tlwoerner has joined #linux-amlogic
yann has quit [Ping timeout: 245 seconds]
yann has joined #linux-amlogic
Linnaea has quit [Ping timeout: 264 seconds]
wildea01 has quit [Quit: leaving]
wildea01 has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 265 seconds]
sputnik__ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
Darkmatter66 has quit [Ping timeout: 240 seconds]
Linnaea has joined #linux-amlogic
bengal has quit [Ping timeout: 250 seconds]
bengal has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
ldevulder__ has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 268 seconds]
<Darkmatter66> Hi, I'm trying to add bluetooth support to the device tree of an s905 device, I've added the dts changes but I'm getting this in dmesg https://0x0.st/z3hp.txt
<Darkmatter66> I'm guessing it still needs a firmware file but the dmesg output doesn't incdicate which file, so how can I know the filename of the firmware needed ?
<Darkmatter66> the internet indicates that the device uses ampak ap6335 combo card
<repk> Darkmatter66: firmware is not the pb, this is uart communication pb
<Darkmatter66> repk, hmmm, do you have any pointers on what might be causing it ?
<Darkmatter66> repk, one thing that looks wrong is that it says " serial0-0 supply vbat not found, using dummy regulator" so it thinks serial0 is a bluetooth device ! while serial0 is an alias to uart_AO and the bluetooth device is on uart_A
<repk> Darkmatter66: maybe you are using the wrong UART, anyway I would go with a logic analyzer to see what kind of data goes out
<repk> serial0-0 is your bluetooth device
<repk> serial0 is a serdev bus
<repk> so serial0-0 is the first dev on the serdev bus which is the bt device
<repk> (serdev only supports on dev)
<repk> so you are using the wrong uart
<Darkmatter66> repk, so i should add the bluetooth node to the uart_AO ?
<Darkmatter66> repk, let me try
<repk> Darkmatter66: what board do you have and where do you plug the bt device ?
<Darkmatter66> moving the bluetooth node to uart_AO doesn't solve the problem : https://0x0.st/z3hv.txt
<Darkmatter66> repk, it's a tv box (videostrong kii pro) it uses the gxbb-p201 reference design dts
<Darkmatter66> repk, it comes with ampak ap6335 combo, I was able to get the wifi working, but not the bluetooth
<repk> Darkmatter66: what does your devicetree look like ?
<Darkmatter66> repk, https://0x0.st/z3h0.c
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-amlogic
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-amlogic
<repk> Darkmatter66: sorry but I don't have a better idea than trying every uart in meson-gxbb.dtsi. Also how can you be sure about the shutdown gpio and its polarity ?
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-amlogic
nsaenz has quit [Read error: Connection reset by peer]
<chewitt> Darkmatter66: I see the same on all boards/box devices I have since 5.4-rc1 .. I didn't see the errors on 5.3.x
<chewitt> ^ reported to linux-bluetooth the other day.. but ignored by everyone on that list
nsaenz has joined #linux-amlogic
nsaenz has quit [Remote host closed the connection]
<chewitt> I have the impression that you need to be "in the club" or demonstrating some higher order of developer skills to be worthy of a response there
<chewitt> as basically everything I ever posted there has been ignored
<chewitt> ho hum
<chewitt> hopefully someone clever than me gets inconvenienced and spots the issue
<repk> chewitt: yours is a different pb
nsaenz has joined #linux-amlogic
<chewitt> pb?
<repk> issue8
<repk> issue*
<chewitt> problem?
nsaenz has quit [Client Quit]
<chewitt> too much shorthand :)
nsaenz has joined #linux-amlogic
<repk> chewitt: apparently this one is not use in english, sorry :)
<chewitt> it's a much vandalised language :)
<repk> chewitt: have you tried to bisect ?
<chewitt> no, because I suck at bisecting and the overall patch-set that I have been playing with is rather large
<chewitt> and getting a new box booting (more u-boot learning) was more fun!
<chewitt> I'm fairly confident that it's not something in the BT driver stack itself, as there's not many changes to the broadcom bits in recent months
<chewitt> and I've tried reverting them all .. and picking any new fixes floating around on mailing lists
<chewitt> this thread sounds similar https://marc.info/?t=157134782900001&r=1&w=2
<chewitt> and the eventual outcome was a delay change being reverted as the problem is seen to be somewhere else
<repk> chewitt: yes nothing looks that bad between 5.3 and master
<chewitt> that thread also mentions "Frame reassembly failed (-84)" which is the initial error that I see
<repk> chewitt: I remember having hit problem at baud rate negociation with axg because the used UART clock divider was not precise enough to reach the requested baud rate precisely. But this is just me thinking out loud
<chewitt> sounds like something way beyond my copy/pasting skills
<chewitt> a quick review of patchwork submits in recent months for "clock" doesn't turn up anything
<repk> no I havn't seen any obvious baud rate clock change so I don't think this is the issue here
yann has quit [Ping timeout: 264 seconds]
yann has joined #linux-amlogic
<Darkmatter66> chewitt, I was able to get bluetooth working using a v5.3 tree but I can't find the right firmware file for the module: https://0x0.st/z3Fn.txt does any of your boards has the same module as shown in the dmesg ?which firmware file worked for you
<Darkmatter66> ?
<narmstrong> someone should bisect between v5,3 and v5,4... something definitely broke hci_bcm... I don't have time for that, next week is "Embedded Linux Conference" + "Halloween" time :-)
sputnik_ has joined #linux-amlogic
<repk> Darkmatter66: that's good news
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 265 seconds]
Darkmatter66_ has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 276 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 265 seconds]