From: Peter Oh <peter.oh@eero.com>
To: Kalle Valo <kvalo@codeaurora.org>, ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/6] ath11k: pci: disable VDD4BLOW
Date: Thu, 10 Dec 2020 14:04:43 -0800 [thread overview]
Message-ID: <d9b860d3-4ccc-f16c-9b0c-e0e7a0646e64@eero.com> (raw)
In-Reply-To: <1607609124-17250-6-git-send-email-kvalo@codeaurora.org>
On 12/10/20 6:05 AM, Kalle Valo wrote:
> From: Carl Huang <cjhuang@codeaurora.org>
>
> It's recommended to disable VDD4BLOW during initialisation.
Can you explain more about "recommended by whom and why"?
Thanks,
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Oh <peter.oh@eero.com>
To: Kalle Valo <kvalo@codeaurora.org>, ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/6] ath11k: pci: disable VDD4BLOW
Date: Thu, 10 Dec 2020 14:04:43 -0800 [thread overview]
Message-ID: <d9b860d3-4ccc-f16c-9b0c-e0e7a0646e64@eero.com> (raw)
In-Reply-To: <1607609124-17250-6-git-send-email-kvalo@codeaurora.org>
On 12/10/20 6:05 AM, Kalle Valo wrote:
> From: Carl Huang <cjhuang@codeaurora.org>
>
> It's recommended to disable VDD4BLOW during initialisation.
Can you explain more about "recommended by whom and why"?
Thanks,
Peter
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-12-10 23:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 14:05 [PATCH 0/6] ath11k: QCA6390 stability fixes Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 1/6] ath11k: mhi: print a warning if firmware crashed Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-12 4:40 ` Kalle Valo
2020-12-12 4:40 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 2/6] ath11k: put hw to DBS using WMI_PDEV_SET_HW_MODE_CMDID Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 3/6] ath11k: pci: fix hot reset stability issues Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 4/6] ath11k: pci: fix L1ss clock unstable problem Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 5/6] ath11k: pci: disable VDD4BLOW Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 22:04 ` Peter Oh [this message]
2020-12-10 22:04 ` Peter Oh
2020-12-11 6:31 ` Kalle Valo
2020-12-11 6:31 ` Kalle Valo
2020-12-10 14:05 ` [PATCH 6/6] ath11k: Fix incorrect tlvs in scan start command Kalle Valo
2020-12-10 14:05 ` Kalle Valo
2020-12-10 14:14 ` [PATCH 0/6] ath11k: QCA6390 stability fixes 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=d9b860d3-4ccc-f16c-9b0c-e0e7a0646e64@eero.com \
--to=peter.oh@eero.com \
--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.