From: Stefan Wahren <wahrenst@gmx.net>
To: "Marcel Holtmann" <marcel@holtmann.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"Ondřej Jirman" <megous@megous.com>
Cc: linux-bluetooth@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 01/10] bluetooth: hci_bcm: Fix RTS handling during startup
Date: Mon, 16 Dec 2019 20:56:12 +0100 [thread overview]
Message-ID: <ff0206e0-8290-0639-5399-5304b9454110@gmx.net> (raw)
In-Reply-To: <20191216194235.4pq2xpfl7nz3p55w@core.my.home>
Hello Ondrej,
Am 16.12.19 um 20:42 schrieb Ondřej Jirman:
> Hello Stefan,
>
> On Mon, Dec 16, 2019 at 07:28:04PM +0100, Stefan Wahren wrote:
>> Hi Ondrej,
>>
>> sorry, i don't have access to a Orange Pi 3.
>>
>> I looked at a AP6256 datasheet [1], but i couldn't find any helpful
>> information about flow control during power up.
>>
>> Are you able to analyze this issue more further before we revert this patch?
> I'd like to, but I'll not be able to attach logic probe to the AP6256
> module. It's too fine pitch for soldering.
this the same issue, i had with the Raspberry Pi 4 :-(
> I may try setting CTS/RTS to gpio/input mode and grab the capture of
> the GPIO port states in time to see what's happening during probe
> of bt_bcm module.
>
> I don't really understand what effect your patch is supposed to have
> on the CTS/RTS lines during power up from the commit description.
> Can you please explain it more concretely?
I hope a picture explain more than thousand words. Please look at figure
7 at page 22 of the datasheet [2]. The patch tries to achieve the proper
timing of BT_UART_CTS_N.
>
> I'll be able to get to playing with this after the holidays.
Okay
Stefan
[2] -
https://www.verical.com/datasheet/cypress-semiconductor-combo-wireless-module-cyw43455xkubgt-5770595.pdf
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-16 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 15:28 [PATCH V4 00/10] ARM: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 01/10] bluetooth: hci_bcm: Fix RTS handling during startup Stefan Wahren
2019-10-20 21:17 ` Stefan Wahren
2019-12-16 13:25 ` Ondřej Jirman
2019-12-16 18:28 ` Stefan Wahren
2019-12-16 19:42 ` Ondřej Jirman
2019-12-16 19:56 ` Stefan Wahren [this message]
2019-12-17 12:59 ` Stefan Wahren
2019-12-17 13:41 ` Ondřej Jirman
2019-12-19 19:54 ` Marcel Holtmann
2019-10-21 15:05 ` Marcel Holtmann
2019-10-06 15:28 ` [PATCH V4 02/10] ARM: dts: bcm283x: Remove simple-bus from fixed clocks Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 03/10] ARM: dts: bcm283x: Remove brcm, bcm2835-pl011 compatible Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 04/10] ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 05/10] dt-bindings: arm: Convert BCM2835 board/soc bindings to json-schema Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 06/10] dt-bindings: arm: bcm2835: Add Raspberry Pi 4 to DT schema Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 07/10] ARM: bcm: Add support for BCM2711 SoC Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 08/10] ARM: dts: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 09/10] arm64: dts: broadcom: Add reference to RPi 4 B Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 10/10] MAINTAINERS: Add BCM2711 to BCM2835 ARCH Stefan Wahren
2019-10-07 10:07 ` [PATCH V4 00/10] ARM: Add minimal Raspberry Pi 4 support Matthias Brugger
2019-10-11 14:46 ` Stefan Wahren
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=ff0206e0-8290-0639-5399-5304b9454110@gmx.net \
--to=wahrenst@gmx.net \
--cc=f.fainelli@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=megous@megous.com \
--cc=nsaenzjulienne@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).