From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
agross@kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, johan.hedberg@gmail.com
Cc: mka@chromium.org, linux-bluetooth@vger.kernel.org,
quic_hemantg@quicinc.com, quic_saluvala@quicinc.com,
quic_rjliao@quicinc.com, mcchou@chromium.org
Subject: Re: [PATCH v1 0/3] WAR to handle WCN6750 hardware issue
Date: Wed, 22 Jun 2022 10:33:48 +0300 [thread overview]
Message-ID: <b8b21831-8078-fb53-d4be-9feb6138b19d@linaro.org> (raw)
In-Reply-To: <1651228073-1999-1-git-send-email-quic_bgodavar@quicinc.com>
On 29/04/2022 13:27, Balakrishna Godavarthi wrote:
> On WCN6750 sometimes observed AON power source takes 100ms
> time to fully discharge voltage during OFF. As WCN6750 is
> combo chip for WLAN and BT. If any of the tech area ON is
> triggered during discharge phase, it fails to turn ON.
> To overcome this hardware issue, During BT ON, driver check
> for WLAN_EN pin status. If it high, it will pull BT_EN to high
> immediately else it will wait for 100ms assuming WLAN was just
> powered OFF and then BT_EN will be pulled to high.
Ugh. This adds another point to support separate power sequencer device
for WiFi+BT devices. Let me refresh my last patchset, so that we can
implement it as a part of common code, rather than hacking hci_qca on
and on.
>
> Balakrishna Godavarthi (3):
> dt-bindings: net: bluetooth: Add wlan-gpio entry for wcn6750
> arm64: dts: qcom: sc7280: Add wlan enable gpio to bluetooth node
> Bluetooth: hci_qca: WAR to handle WCN6750 HW issue
>
> .../bindings/net/qualcomm-bluetooth.yaml | 6 +++++
> arch/arm64/boot/dts/qcom/sc7280-idp.dtsi | 1 +
> drivers/bluetooth/hci_qca.c | 30 +++++++++++++++++-----
> 3 files changed, 31 insertions(+), 6 deletions(-)
>
--
With best wishes
Dmitry
prev parent reply other threads:[~2022-06-22 7:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:27 [PATCH v1 0/3] WAR to handle WCN6750 hardware issue Balakrishna Godavarthi
2022-04-29 10:27 ` [PATCH v1 1/3] dt-bindings: net: bluetooth: Add wlan-gpio entry for wcn6750 Balakrishna Godavarthi
2022-04-29 12:00 ` WAR to handle WCN6750 hardware issue bluez.test.bot
2022-04-29 14:50 ` [PATCH v1 1/3] dt-bindings: net: bluetooth: Add wlan-gpio entry for wcn6750 Marcel Holtmann
2022-05-04 20:31 ` Rob Herring
2022-04-29 10:27 ` [PATCH v1 2/3] arm64: dts: qcom: sc7280: Add wlan enable gpio to bluetooth node Balakrishna Godavarthi
2022-04-29 10:27 ` [PATCH v1 3/3] Bluetooth: hci_qca: WAR to handle WCN6750 HW issue Balakrishna Godavarthi
2022-04-29 14:54 ` Marcel Holtmann
2022-04-30 3:09 ` Balakrishna Godavarthi (QUIC)
2022-05-10 3:17 ` Miao-chen Chou
2022-06-22 7:27 ` Balakrishna Godavarthi (QUIC)
2022-10-13 19:11 ` mka
2022-10-13 20:06 ` Luiz Augusto von Dentz
2022-10-13 20:12 ` mka
2022-04-29 22:59 ` [PATCH] Bluetooth: hci_qca: fix excluded_middle.cocci warnings kernel test robot
2022-04-29 23:05 ` [PATCH v1 3/3] Bluetooth: hci_qca: WAR to handle WCN6750 HW issue kernel test robot
2022-06-22 7:33 ` Dmitry Baryshkov [this message]
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=b8b21831-8078-fb53-d4be-9feb6138b19d@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=mka@chromium.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hemantg@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=quic_saluvala@quicinc.com \
--cc=robh+dt@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 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).