Hi Luiz, > -----Original Message----- > From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth- > owner@xxxxxxxxxxxxxxx] On Behalf Of Luiz Augusto von Dentz > Sent: Monday, August 17, 2015 5:45 PM > To: Bharat Panda > Cc: linux-bluetooth@xxxxxxxxxxxxxxx; cpgs@xxxxxxxxxxx > Subject: Re: [PATCH v2] audio/avrcp: Add Set Addressed Player support > > Hi Bharat, > > On Fri, Aug 14, 2015 at 4:36 PM, Bharat Panda > <bharat.panda@xxxxxxxxxxx> wrote: > > Support added to handle Set Addressed Player PDU in TG role. > > Send EVENT_ADDRESSED_PLAYER_CHANGED on SetAddressedPlayer > SUCCESS and > > follow procedure to reject all player specific events currently > > registered with the player. > > > > Channel: 64 len 15 [PSM 23 mode 0] {chan 0} > > AVCTP Control: Command: type 0x00 label 0 PID 0x110e > > AV/C: Control: address 0x48 opcode 0x00 > > Subunit: Panel > > Opcode: Vendor Dependent > > Company ID: 0x001958 > > AVRCP: SetAddressedPlayer pt Single len 0x0002 > > PlayerID: 0x0000 (0) > > > > Channel: 64 len 15 [PSM 23 mode 0] {chan 0} > > AVCTP Control: Response: type 0x00 label 0 PID 0x110e > > AV/C: Accepted: address 0x48 opcode 0x00 > > Subunit: Panel > > Opcode: Vendor Dependent > > Company ID: 0x001958 > > AVRCP: SetAddressedPlayer pt Single len 0x0002 > > Status: 0x04 (Success) > > > > Channel: 64 len 18 [PSM 23 mode 0] {chan 0} > > AVCTP Control: Response: type 0x00 label 0 PID 0x110e > > AV/C: Changed: address 0x48 opcode 0x00 > > Subunit: Panel > > Opcode: Vendor Dependent > > Company ID: 0x001958 > > AVRCP: RegisterNotification pt Single len 0x0005 > > EventID: 0x0b (EVENT_ADDRESSED_PLAYER_CHANGED) > > PlayerID: 0x0000 (0) > > UIDCounter: 0x0000 (0) > > --- > > I went ahead and made some changes to make the code look simpler and > reuse avrcp_player_event, please check if it still work as before. I applied the patch with your changes, tested with Mecapp and PTS. It works fine. > > -- > Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
