linux-kernel - Re: [PATCH v1 0/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 29 May 2024 04:57:44 -0400
From: Emil Renner Berthing <emil.renner.berthing@...onical.com>
To: Emil Renner Berthing <emil.renner.berthing@...onical.com>, 
	Andreas Schwab <schwab@...ux-m68k.org>
Cc: devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org, 
	linux-kernel@...r.kernel.org, Emil Renner Berthing <kernel@...il.dk>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>, 
	Albert Ou <aou@...s.berkeley.edu>
Subject: Re: [PATCH v1 0/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards

Emil Renner Berthing wrote:
> Andreas Schwab wrote:
> > On Mai 10 2024, Emil Renner Berthing wrote:
> >
> > > You don't include any information useful for debugging this, but if it get's
> > > far enough to load the firmware could you at least make sure you run the
> > > version below, so that's at least the same.
> > >
> > > https://github.com/esmil/linux/blob/visionfive/firmware/brcm/BCM43430A1.hcd
> >
> > That didn't change anything (and there are no messages related to
> > firmware loading from hci_uart).
> >
> > [  +0.879623] Bluetooth: Core ver 2.22
> > [  +0.004843] NET: Registered PF_BLUETOOTH protocol family
> > [  +0.008787] Bluetooth: HCI device and connection manager initialized
> > [  +0.021944] Bluetooth: HCI socket layer initialized
> > [  +0.008488] Bluetooth: L2CAP socket layer initialized
> > [  +0.006333] Bluetooth: SCO socket layer initialized
> > [  +0.097478] Bluetooth: HCI UART driver ver 2.3
> > [  +0.007943] Bluetooth: HCI UART protocol H4 registered
> > [  +0.006066] Bluetooth: HCI UART protocol BCSP registered
> > [  +0.006962] Bluetooth: HCI UART protocol LL registered
> > [  +0.000015] Bluetooth: HCI UART protocol ATH3K registered
> > [  +0.000084] Bluetooth: HCI UART protocol Three-wire (H5) registered
> > [  +0.000247] Bluetooth: HCI UART protocol Intel registered
> > [  +0.000455] Bluetooth: HCI UART protocol Broadcom registered
> > [  +0.000084] Bluetooth: HCI UART protocol QCA registered
> > [  +0.000008] Bluetooth: HCI UART protocol AG6XX registered
> > [  +0.000057] Bluetooth: HCI UART protocol Marvell registered
> > [  +0.051854] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
> > [  +0.000387] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
> > [  +0.094658] hci_uart_bcm serial0-0: No reset resource, using default baud rate
> > [  +0.990297] Bluetooth: hci0: command 0x1001 tx timeout
> > [  +0.022893] Bluetooth: hci0: BCM: Reading local version info failed (-110)
> > [  +3.306159] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> > [  +0.013336] Bluetooth: BNEP filters: protocol multicast
> > [  +0.124262] Bluetooth: BNEP socket layer initialized
>
> Oddly it doesn't work on my Starlight board either. I was thinking the firmware
> might set up pinconf differently, but comparing
>
>   /sys/kernel/debug/pinctrl/11910000.pinctrl-pinctrl-starfive/pinconf-pins
>
> on the two boards shows no differences. I've also not been able to spot any
> differences in how the AP6236 module is connected in the schematics for the two
> boards, so not really sure how to proceed.
>
> If you're also testing on the Starlight board then I can update the patch to just
> enable Bluetooth on that I guess.

* I meant update the patch to only enable bluetooth on the VisionFive V1 of
  course.

/Emil