From: Feryllt Pryderi <feryllt@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] audio/transport: Emit Volume changed if endpoint is source
Date: Wed, 31 Mar 2021 22:03:00 +0200 [thread overview]
Message-ID: <394e71c9-3abe-7a9d-e47d-0793ba9736f3@gmail.com> (raw)
In-Reply-To: <CABBYNZJ2Hw1+xSvhqwBQa90qkpcmYh+qO3U+Rs1JBaSOz+7AMA@mail.gmail.com>
Hi Luiz,
sure I can update the patch, but is the if at all needed? Can we have transports without any of source_watch and sink_watch?
On 3/31/21 8:33 PM, Luiz Augusto von Dentz wrote:
> Hi Feryllt,
>
> On Wed, Mar 31, 2021 at 4:40 AM Feryllt Pryderi <feryllt@gmail.com> wrote:
>> Change set_volume to send a Volume PropertyChanged signal also if
>> transport->sink_watch is set (and not only if source_watch is set).
>>
>> This fixes volume changes signals not being sent for devices like speakers and
>> headphone adapters with volume control (like Bose Soundlink Revolve or Fiio BTR5).
>> ---
>> profiles/audio/transport.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/profiles/audio/transport.c b/profiles/audio/transport.c
>> index 8248014ae..26aa237a3 100644
>> --- a/profiles/audio/transport.c
>> +++ b/profiles/audio/transport.c
>> @@ -662,6 +662,7 @@ static void set_volume(const GDBusPropertyTable *property,
>> a2dp->volume = volume;
>>
>> notify = transport->source_watch ? true : false;
>> + notify = notify || (transport->sink_watch ? true : false);
> Id replace the following like with:
>
> if (transport->source_watch || transport->sink_watch)
>
>> if (notify)
>> g_dbus_emit_property_changed(btd_get_dbus_connection(),
>> transport->path,
>> --
>> 2.31.0
>>
>
next prev parent reply other threads:[~2021-03-31 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 11:38 [PATCH BlueZ] audio/transport: Emit Volume changed if endpoint is source Feryllt Pryderi
2021-03-31 18:33 ` Luiz Augusto von Dentz
2021-03-31 20:03 ` Feryllt Pryderi [this message]
2021-03-31 20:14 ` Luiz Augusto von Dentz
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=394e71c9-3abe-7a9d-e47d-0793ba9736f3@gmail.com \
--to=feryllt@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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.