All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
	quic_chezhou@quicinc.com, wei.deng@oss.qualcomm.com,
	jinwang.li@oss.qualcomm.com, mengshi.wu@oss.qualcomm.com
Subject: Re: [PATCH v2] Bluetooth: hci_qca: disable power control for WCN7850 when bt_en is not defined
Date: Thu, 19 Mar 2026 17:48:37 +0800	[thread overview]
Message-ID: <1faac95b-4c67-46d5-9c59-da4963e7e8de@oss.qualcomm.com> (raw)
In-Reply-To: <CAMRc=MdRGdR=FyQHWC7yfAgpAFxiK6QGjEQXVr7mavWLOPS14g@mail.gmail.com>

Hi  Bartosz

On 3/19/2026 5:35 PM, Bartosz Golaszewski wrote:
> On Thu, Mar 19, 2026 at 8:51 AM Shuai Zhang
> <shuai.zhang@oss.qualcomm.com> wrote:
>> On platforms using an M.2 slot with both UART and USB support, bt_en is
>> pulled high by hardware. In this case, software-based power control
>> should be disabled. The current platforms are Lemans-EVK and Monaco-EVK.
>>
>> Add QCA_WCN7850 to the existing condition so that power_ctrl_enabled is
>> cleared when bt_en is not software-controlled (or absent), aligning its
>> behavior with WCN6750 and WCN6855
>>
>> Signed-off-by: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
>> ---
> What are the changes in v2?


Sorry, I forgot to include the version update differences. v2 only 
updates the commit content
and adds explanations regarding hardware management.


>
> Bartosz


Thanks,

Shuai


      reply	other threads:[~2026-03-19  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  7:51 [PATCH v2] Bluetooth: hci_qca: disable power control for WCN7850 when bt_en is not defined Shuai Zhang
2026-03-19  8:57 ` [v2] " bluez.test.bot
2026-03-19  9:35 ` [PATCH v2] " Bartosz Golaszewski
2026-03-19  9:48   ` Shuai Zhang [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=1faac95b-4c67-46d5-9c59-da4963e7e8de@oss.qualcomm.com \
    --to=shuai.zhang@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=cheng.jiang@oss.qualcomm.com \
    --cc=jinwang.li@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mengshi.wu@oss.qualcomm.com \
    --cc=quic_chezhou@quicinc.com \
    --cc=wei.deng@oss.qualcomm.com \
    /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.