From: Zijun Hu <zijuhu@codeaurora.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-arm-msm@vger.kernel.org, bgodavar@codeaurora.org,
c-hbandi@codeaurora.org, hemantg@codeaurora.org,
mka@chromium.org, rjliao@codeaurora.org
Subject: Re: [PATCH v1] Bluetooth: hci_qca: Fix qca6390 enable failure after warm reboot
Date: Fri, 29 May 2020 21:58:11 +0800 [thread overview]
Message-ID: <7ef3637f-3d49-ab17-fba1-6d29ac6c069a@codeaurora.org> (raw)
In-Reply-To: <6C68EF2F-7DEC-4CA4-A0E8-8C775B3CF62B@holtmann.org>
On 5/29/2020 7:45 PM, Marcel Holtmann wrote:
> Hi Zijun,
>
>> On May 29, 2020, at 04:29, Zijun Hu <zijuhu@codeaurora.org> wrote:
>>
>> Warm reboot can not reset controller qca6390 due to
>> lack of controllable power supply, so causes firmware
>> download failure during enable.
>>
>> Fixed by sending VSC EDL_SOC_RESET to reset qca6390
>> within added device shutdown implementation.
>>
>> Signed-off-by: Zijun Hu <zijuhu@codeaurora.org>
>> Tested-by: Zijun Hu <zijuhu@codeaurora.org>
>> ---
>> drivers/bluetooth/hci_qca.c | 33 +++++++++++++++++++++++++++++++++
>> 1 file changed, 33 insertions(+)
>
> patch does not apply to bluetooth-next tree, please rebase.
>
rebased at v2
> Regards
>
> Marcel
>
next prev parent reply other threads:[~2020-05-29 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 2:29 [PATCH v1] Bluetooth: hci_qca: Fix qca6390 enable failure after warm reboot Zijun Hu
2020-05-29 11:45 ` Marcel Holtmann
2020-05-29 13:58 ` Zijun Hu [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-25 9:31 [PATCH v1] bluetooth: " Zijun Hu
2020-05-25 11:30 ` Marcel Holtmann
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=7ef3637f-3d49-ab17-fba1-6d29ac6c069a@codeaurora.org \
--to=zijuhu@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=hemantg@codeaurora.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=mka@chromium.org \
--cc=rjliao@codeaurora.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).