public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Egor Vorontsov <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5bc17a: profiles/input: Add cable pairing constants for Du...
Date: Tue, 03 Jun 2025 03:13:45 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/968245/000000-99b6f0@github.com> (raw)

  Branch: refs/heads/968245
  Home:   https://github.com/bluez/bluez
  Commit: 5bc17a3d844bb31c912a943a7bd7ce7a70e303d6
      https://github.com/bluez/bluez/commit/5bc17a3d844bb31c912a943a7bd7ce7a70e303d6
  Author: Egor Vorontsov <sdoregor@sdore.me>
  Date:   2025-06-03 (Tue, 03 Jun 2025)

  Changed paths:
    M profiles/input/server.c
    M profiles/input/sixaxis.h

  Log Message:
  -----------
  profiles/input: Add cable pairing constants for DualSense

Sony DualSense & DualSense Edge controllers support cable pairing
the same way as previous Sixaxis controller generations do.

This patch prepares their input profile for its implementation.


  Commit: 99b6f0c9cfaeade4862708b29183691aa0b7dd7a
      https://github.com/bluez/bluez/commit/99b6f0c9cfaeade4862708b29183691aa0b7dd7a
  Author: Egor Vorontsov <sdoregor@sdore.me>
  Date:   2025-06-03 (Tue, 03 Jun 2025)

  Changed paths:
    M plugins/sixaxis.c

  Log Message:
  -----------
  plugins/sixaxis: Implement cable pairing for DualSense

The code is very similar to that for DS4, but I found it's better
to separate the matters instead of generalizing it via constants.

Also added a request to enable Bluetooth on the controller to initiate
pairing without the need to disconnect it and power on again wirelessly,
basically emulating what PS itself does. Only for DualSense family now,
but can be expanded to DS4 too (I don't have one at hand to test this).


Compare: https://github.com/bluez/bluez/compare/5bc17a3d844b%5E...99b6f0c9cfae

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2025-06-03 10:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/968245/000000-99b6f0@github.com \
    --to=noreply@github.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