From: Baochen Qiang <bqiang@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath11k: Advertise PLATFORM_CAP_PCIE_GLOBAL_RESET in qmi msg
Date: Tue, 12 Oct 2021 17:14:24 +0800 [thread overview]
Message-ID: <13074ee3556a72cd1f235a493c79f202@codeaurora.org> (raw)
On 2021-10-11 14:30, Kalle Valo wrote:
> Baochen Qiang <bqiang@codeaurora.org> writes:
>
>> Inform firmware that host is capable of triggering a global reset.
>> This is requested by firmware team.
>
> Why?
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches#answer_to_why
In some scenarios like rmmod/insmod, HW target needs to be completely
reset. On ARM platforms we can rely on WL_EN pin and other power
regulators to do this. However on x86 or some third party platforms,
this has to be done by ath11k host by writing HW register
PCIE_SOC_GLOBAL_RESET. But the problem is that some HW registers can not
be cleared/restored. With this flag PLATFORM_CAP_PCIE_GLOBAL_RESET in
QMI host_cap message, firmware can do some platform specific operations
to fix this issue.
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Baochen Qiang <bqiang@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath11k: Advertise PLATFORM_CAP_PCIE_GLOBAL_RESET in qmi msg
Date: Tue, 12 Oct 2021 17:14:24 +0800 [thread overview]
Message-ID: <13074ee3556a72cd1f235a493c79f202@codeaurora.org> (raw)
On 2021-10-11 14:30, Kalle Valo wrote:
> Baochen Qiang <bqiang@codeaurora.org> writes:
>
>> Inform firmware that host is capable of triggering a global reset.
>> This is requested by firmware team.
>
> Why?
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches#answer_to_why
In some scenarios like rmmod/insmod, HW target needs to be completely
reset. On ARM platforms we can rely on WL_EN pin and other power
regulators to do this. However on x86 or some third party platforms,
this has to be done by ath11k host by writing HW register
PCIE_SOC_GLOBAL_RESET. But the problem is that some HW registers can not
be cleared/restored. With this flag PLATFORM_CAP_PCIE_GLOBAL_RESET in
QMI host_cap message, firmware can do some platform specific operations
to fix this issue.
next reply other threads:[~2021-10-12 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:14 Baochen Qiang [this message]
2021-10-12 9:14 ` [PATCH] ath11k: Advertise PLATFORM_CAP_PCIE_GLOBAL_RESET in qmi msg Baochen Qiang
-- strict thread matches above, loose matches on Subject: below --
2021-10-11 5:56 Baochen Qiang
2021-10-11 5:56 ` Baochen Qiang
2021-10-11 6:30 ` Kalle Valo
2021-10-11 6:30 ` Kalle Valo
2022-03-21 13:18 ` Kalle Valo
2022-03-21 13:18 ` Kalle Valo
2022-03-23 9:06 ` Kalle Valo
2022-03-23 9:06 ` Kalle Valo
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=13074ee3556a72cd1f235a493c79f202@codeaurora.org \
--to=bqiang@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.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.