From: Jinwang Li <jinwang.li@oss.qualcomm.com>
To: linux-bluetooth@vger.kernel.org
Cc: cheng.jiang@oss.qualcomm.com, quic_chezhou@quicinc.com,
wei.deng@oss.qualcomm.com, shuai.zhang@oss.qualcomm.com,
mengshi.wu@oss.qualcomm.com
Subject: Re: [PATCH v1] device: Initialize device volume with a valid value
Date: Wed, 25 Feb 2026 17:10:14 +0800 [thread overview]
Message-ID: <93f63aca-bbdc-4e83-ab2d-9a6f366aa9f9@oss.qualcomm.com> (raw)
In-Reply-To: <20260122063640.310090-1-jinwang.li@oss.qualcomm.com>
On 1/22/2026 2:36 PM, Jinwang Li wrote:
> When AVRCP is connected earlier than AVDTP, this invalid device volume
> causes the A2DP sink to reject the peer's registration for the
> EVENT_VOLUME_CHANGED notification. As a result, subsequent attempts to
> set the volume fail.
>
> Fixes: fa7828bddd21 ("transport: Fix not being able to initialize volume properly")
> Signed-off-by: Jinwang Li <jinwang.li@oss.qualcomm.com>
> ---
> src/device.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/device.c b/src/device.c
> index af8df5f29..cd0b8802e 100644
> --- a/src/device.c
> +++ b/src/device.c
> @@ -4948,7 +4948,7 @@ static struct btd_device *device_new(struct btd_adapter *adapter,
> return NULL;
>
> device->tx_power = 127;
> - device->volume = -1;
> + device->volume = 127;
> device->wake_id = -1U;
>
> device->db = gatt_db_new();
Hi maintainers,
Do you have any comments on this change?
--
with best wishes
Jinwang
next prev parent reply other threads:[~2026-02-25 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 6:36 [PATCH v1] device: Initialize device volume with a valid value Jinwang Li
2026-01-22 7:50 ` [v1] " bluez.test.bot
2026-02-25 9:10 ` Jinwang Li [this message]
2026-02-25 14:52 ` [PATCH v1] " Luiz Augusto von Dentz
2026-03-05 8:41 ` Jinwang Li
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=93f63aca-bbdc-4e83-ab2d-9a6f366aa9f9@oss.qualcomm.com \
--to=jinwang.li@oss.qualcomm.com \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=quic_chezhou@quicinc.com \
--cc=shuai.zhang@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox