From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v2 0/7] Add BIP for AVRCP covert art OBEX client
Date: Thu, 12 Sep 2024 19:49:14 +0200 [thread overview]
Message-ID: <20240912174921.386856-1-frederic.danis@collabora.com> (raw)
If AVRCP Target supports Cover Art download its SDP record contains an
additional access protocol for OBEX with an LCAP PSM on which the OBEX
client session should connect to, with the specific OBEX target header
7163DD54-4A7E-11E2-B47C-0050C2490048.
Once the OBEX session is connected, the AVRCP track metadata will contain
an Image Handle which can be used to get the associated image using
GetImageThumbnail or GetImage with one of the description property found
with GetImageProperties.
v1 -> v2: Parse integer properties as integer instead of string
Return GetImageProperties values as aa{sv} instead of aa{ss}
Get properties for GetImage as a{sv} instead of a{ss}
Set new properties and interface as experimental
Frédéric Danis (7):
obexd: Add PSM support to session create
player: Add OBEX PSM port for cover art support
player: Add image handle support property
obexd: Add BIP client for AVRCP cover art download.
obexd: Add GetImageProperties to bip-avrcp
obexd: Add GetImage to bip-avrcp
doc: Add description of org.bluez.obex.BipAvrcp
Makefile.am | 9 +-
Makefile.obexd | 2 +
doc/org.bluez.MediaPlayer.rst | 11 +
doc/org.bluez.obex.BipAvrcp.rst | 72 +++
doc/org.bluez.obex.Client.rst | 5 +
doc/org.bluez.obex.Session.rst | 5 +
monitor/avctp.c | 3 +
obexd/client/bip-avrcp.c | 427 +++++++++++++++++
obexd/client/bip-avrcp.h | 12 +
obexd/client/bip-common.c | 800 ++++++++++++++++++++++++++++++++
obexd/client/bip-common.h | 24 +
obexd/client/manager.c | 16 +-
obexd/client/session.c | 27 +-
obexd/client/session.h | 1 +
obexd/client/transfer.c | 16 +
obexd/client/transfer.h | 2 +
profiles/audio/avrcp.c | 64 ++-
profiles/audio/avrcp.h | 3 +-
profiles/audio/player.c | 30 ++
profiles/audio/player.h | 1 +
tools/parser/avrcp.c | 3 +
21 files changed, 1514 insertions(+), 19 deletions(-)
create mode 100644 doc/org.bluez.obex.BipAvrcp.rst
create mode 100644 obexd/client/bip-avrcp.c
create mode 100644 obexd/client/bip-avrcp.h
create mode 100644 obexd/client/bip-common.c
create mode 100644 obexd/client/bip-common.h
--
2.34.1
next reply other threads:[~2024-09-12 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 17:49 Frédéric Danis [this message]
2024-09-12 17:49 ` [PATCH BlueZ v2 1/7] obexd: Add PSM support to session create Frédéric Danis
2024-09-12 22:37 ` Add BIP for AVRCP covert art OBEX client bluez.test.bot
2024-09-12 17:49 ` [PATCH BlueZ v2 2/7] player: Add OBEX PSM port for cover art support Frédéric Danis
2024-09-12 17:49 ` [PATCH BlueZ v2 3/7] player: Add image handle support property Frédéric Danis
2024-09-12 17:49 ` [PATCH BlueZ v2 4/7] obexd: Add BIP client for AVRCP cover art download Frédéric Danis
2024-09-13 15:59 ` Luiz Augusto von Dentz
2024-09-12 17:49 ` [PATCH BlueZ v2 5/7] obexd: Add GetImageProperties to bip-avrcp Frédéric Danis
2024-09-12 17:49 ` [PATCH BlueZ v2 6/7] obexd: Add GetImage " Frédéric Danis
2024-09-13 16:05 ` Luiz Augusto von Dentz
2024-09-12 17:49 ` [PATCH BlueZ v2 7/7] doc: Add description of org.bluez.obex.BipAvrcp Frédéric Danis
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=20240912174921.386856-1-frederic.danis@collabora.com \
--to=frederic.danis@collabora.com \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox