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: Wed, 29 May 2024 17:53:29 +0200	[thread overview]
Message-ID: <878qzsbona.fsf@igel.home> (raw)
In-Reply-To: <CAJM55Z8Ce1i==pSUj0z4T2y71g713-675mAYQP5qSN5Euz=rLQ@mail.gmail.com> (Emil Renner Berthing's message of "Wed, 29 May 2024 04:49:03 -0400")

On Mai 29 2024, Emil Renner Berthing wrote:

> 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.

I see no difference between Starlight and Visionfive boards, both fail
the same way.

I also see that sometimes the firmware greeting from brcmfmac occurs
_after_ the timeout error from hci0:

# journalctl -b -2 | grep -e brcmf_c_preinit_dcmds -e hci0:
May 16 12:01:54 beaglev kernel: Bluetooth: hci0: command 0x1001 tx timeout
May 16 12:01:54 beaglev kernel: Bluetooth: hci0: BCM: Reading local version info failed (-110)
May 16 12:01:54 beaglev kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766

Is this perhaps a race with the firmware loading?

-- 
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: Wed, 29 May 2024 17:53:29 +0200	[thread overview]
Message-ID: <878qzsbona.fsf@igel.home> (raw)
In-Reply-To: <CAJM55Z8Ce1i==pSUj0z4T2y71g713-675mAYQP5qSN5Euz=rLQ@mail.gmail.com> (Emil Renner Berthing's message of "Wed, 29 May 2024 04:49:03 -0400")

On Mai 29 2024, Emil Renner Berthing wrote:

> 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.

I see no difference between Starlight and Visionfive boards, both fail
the same way.

I also see that sometimes the firmware greeting from brcmfmac occurs
_after_ the timeout error from hci0:

# journalctl -b -2 | grep -e brcmf_c_preinit_dcmds -e hci0:
May 16 12:01:54 beaglev kernel: Bluetooth: hci0: command 0x1001 tx timeout
May 16 12:01:54 beaglev kernel: Bluetooth: hci0: BCM: Reading local version info failed (-110)
May 16 12:01:54 beaglev kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766

Is this perhaps a race with the firmware loading?

-- 
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."

  parent reply	other threads:[~2024-05-29 15:53 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
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 [this message]
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=878qzsbona.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.