All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: devicetree@vger.kernel.org,  linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 Emil Renner Berthing <kernel@esmil.dk>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v1 0/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards
Date: Fri, 10 May 2024 11:35:34 +0200	[thread overview]
Message-ID: <87zfsy102h.fsf@igel.home> (raw)
In-Reply-To: <CAJM55Z-F6N6ua5LoqyMFogDtLp=FaRPoDv4osXFDMjR1b8r9nw@mail.gmail.com> (Emil Renner Berthing's message of "Fri, 10 May 2024 04:02:58 -0500")

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

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: devicetree@vger.kernel.org,  linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 Emil Renner Berthing <kernel@esmil.dk>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v1 0/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards
Date: Fri, 10 May 2024 11:35:34 +0200	[thread overview]
Message-ID: <87zfsy102h.fsf@igel.home> (raw)
In-Reply-To: <CAJM55Z-F6N6ua5LoqyMFogDtLp=FaRPoDv4osXFDMjR1b8r9nw@mail.gmail.com> (Emil Renner Berthing's message of "Fri, 10 May 2024 04:02:58 -0500")

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

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2024-05-10  9:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 11:15 [PATCH v1 0/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards Emil Renner Berthing
2024-05-08 11:15 ` Emil Renner Berthing
2024-05-08 11:15 ` [PATCH v1 1/2] riscv: dts: starfive: Add JH7100 high speed UARTs Emil Renner Berthing
2024-05-08 11:15   ` Emil Renner Berthing
2024-05-08 11:15 ` [PATCH v1 2/2] riscv: dts: starfive: Enable Bluetooth on JH7100 boards Emil Renner Berthing
2024-05-08 11:15   ` Emil Renner Berthing
2024-05-10  7:42 ` [PATCH v1 0/2] " Andreas Schwab
2024-05-10  7:42   ` Andreas Schwab
2024-05-10  9:02   ` Emil Renner Berthing
2024-05-10  9:02     ` Emil Renner Berthing
2024-05-10  9:35     ` Andreas Schwab [this message]
2024-05-10  9:35       ` Andreas Schwab
2024-05-28 11:30       ` Conor Dooley
2024-05-28 11:30         ` Conor Dooley
2024-05-28 15:37         ` Andreas Schwab
2024-05-28 15:37           ` Andreas Schwab
2024-05-28 15:38           ` Conor Dooley
2024-05-28 15:38             ` Conor Dooley
2024-05-29  8:49       ` Emil Renner Berthing
2024-05-29  8:49         ` Emil Renner Berthing
2024-05-29  8:57         ` Emil Renner Berthing
2024-05-29  8:57           ` Emil Renner Berthing
2024-05-29 15:53         ` Andreas Schwab
2024-05-29 15:53           ` Andreas Schwab
2024-05-29 19:30           ` Samuel Holland
2024-05-29 19:30             ` Samuel Holland
2024-05-29 19:49             ` Andreas Schwab
2024-05-29 19:49               ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfsy102h.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=emil.renner.berthing@canonical.com \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.