Add native Switch Pro IMU and player LED support

Route Linux Switch Pro controllers through descriptor-driven UHID, share the native handshake/reply protocol with Windows, and pack live IMU samples into Switch input reports. The API, control UI, tests, and docs now expose Switch Pro player LED output support and document the updated Linux backend behavior.

Author: ReenigneArcher

README.md

@@ -45,14 +45,14 @@ behind backend implementations.
 
 - Gamepad profiles for generic HID, Xbox 360, Xbox One, Xbox Series,
   DualShock 4, DualSense, and Nintendo Switch Pro-style controllers.
-- Descriptor-driven PlayStation gamepads through Linux `uhid`; Generic, Xbox,
-  and Switch Pro gamepads plus keyboard, mouse, touchscreen, trackpad, and pen
-  tablet devices through `uinput`.
+- Descriptor-driven PlayStation and Switch Pro gamepads through Linux `uhid`;
+  Generic and Xbox gamepads plus keyboard, mouse, touchscreen, trackpad, and
+  pen tablet devices through `uinput`.
 - Windows gamepads, keyboards, and Raw Input-visible mice through a user-mode
   UMDF2 control driver backed by Virtual HID Framework, with Win32 keyboard and
   mouse fallbacks when the licensed driver path is unavailable.
-- Output callbacks for profile-specific feedback such as rumble, LEDs,
-  adaptive triggers, and raw HID output reports when available.
+- Output callbacks for profile-specific feedback such as rumble, RGB and player
+  LEDs, adaptive triggers, and raw HID output reports when available.
 - An optional `virtualhid_control` native UI tool for creating, removing,
   controlling, and inspecting test gamepads and mice through the public C++ API.
 - CMake consumption through installed packages, vendored source,

docs/end-user-gamepad-guide.md

@@ -101,26 +101,23 @@ and signing details.
 
 The Linux backend uses standard user-space kernel interfaces:
 
-- `uhid` for descriptor-driven HID gamepads.
-- `uinput` for Generic, Xbox 360, Xbox One, Xbox Series, and Switch Pro
-  gamepads, plus keyboard, mouse, touchscreen, trackpad, and pen tablet
-  devices.
+- `uhid` for descriptor-driven PlayStation and Switch Pro gamepads.
+- `uinput` for Generic, Xbox 360, Xbox One, and Xbox Series gamepads, plus
+  keyboard, mouse, touchscreen, trackpad, and pen tablet devices.
 - `libevdev` internally for uinput device construction.
 - X11/XTest only as a keyboard and mouse fallback when `uinput` cannot be used
   and an X11 session is available.
 
 Gamepad support normally prefers `uhid` because descriptors, raw HID identity,
 feature reports, and output reports matter for controller compatibility.
-Generic, Xbox-family, and Switch Pro profiles instead use `uinput` so SDL,
+Generic and Xbox-family profiles instead use `uinput` so SDL,
 Steam, browser Gamepad API implementations, and other evdev consumers receive
 canonical Linux gamepad events. Face buttons, shoulders, menu buttons, stick
 clicks, and Guide use their native evdev codes; sticks use absolute axes. Every
 uinput gamepad exposes its directional pad through `ABS_HAT0X` and `ABS_HAT0Y`.
 Generic and Xbox triggers remain independent analog `ABS_Z` and `ABS_RZ` axes.
-Switch Pro uses the Nintendo face-button
-positions, button events for ZL/ZR, and `BTN_Z` for Capture. Profiles with rumble
-support normalize rumble, constant, periodic, and ramp uinput force-feedback
-effects back into the public callback. Each requested playback repetition
+Profiles with rumble support normalize rumble, constant, periodic, and ramp
+uinput force-feedback effects back into the public callback. Each requested playback repetition
 restarts the effect's ramp and envelope timing. A zero-length effect remains
 active until its explicit stop event, matching the infinite-effect contract used
 by SDL and Steam. The Linux backend lets a new uinput device settle before
@@ -182,10 +179,14 @@ descriptor, and report framing remain unchanged. This transport-only name is
 confined to the Linux backend; public profile names, Windows names, and VHF
 behavior are unchanged.
 
-Switch Pro keeps its Nintendo identity on the Linux uinput path. This follows
-the evdev layout used by Linux-native virtual-controller implementations and
-allows standard `FF_RUMBLE` effects without emulating the physical controller's
-proprietary initialization handshake.
+Switch Pro uses Linux `uhid` with its native Nintendo descriptor and identity.
+It advertises `BUS_VIRTUAL` so `hid-generic` and HIDAPI consumers can use the
+descriptor without the kernel claiming the virtual endpoint as physical
+Nintendo hardware. The backend answers Nintendo USB and subcommand
+initialization reports, and native `0x30` input reports carry buttons, sticks,
+battery state, and three live IMU samples. The public acceleration and
+gyroscope units remain meters per second squared and degrees per second; the
+packer converts them to Nintendo's coordinate system and sensor scales.
 
 Linux touchscreen and trackpad contacts use the lowest available multitouch
 slot while they are active. A newly placed contact receives a new tracking ID,
@@ -194,7 +195,9 @@ finger cannot overwrite another active finger in standard evdev consumers.
 
 On descriptor-driven backends, native Switch Pro output reports `0x01` and
 `0x10` are decoded into the normalized low- and high-frequency rumble callback.
-The original native report remains available in `GamepadOutput::raw_report`.
+Set Player Lights subcommand `0x30` additionally produces a `player_leds`
+callback with separate solid and flashing states for the four indicators. The
+original native report remains available in `GamepadOutput::raw_report`.
 
 The optional `virtualhid_control` diagnostic UI uses SDL3 and Dear ImGui through
 the repository CPM lockfile. It is intended to stay on the same UI framework for

docs/platform-support.md

@@ -13,8 +13,9 @@ A streaming host should be able to:
   indexes.
 - Submit incremental button, axis, trigger, touchpad, motion, and battery
   updates without recreating a device.
-- Receive output callbacks for rumble, LEDs, adaptive triggers, trigger rumble,
-  and raw output reports where the selected profile supports them.
+- Receive output callbacks for rumble, RGB and player LEDs, adaptive triggers,
+  trigger rumble, and raw output reports where the selected profile supports
+  them.
 - Query profile and backend capabilities before warning users about unsupported
   client features.
 - Read device nodes and platform paths when a downstream consumer or diagnostic
@@ -51,8 +52,10 @@ The core API and adapter shape cover the major streaming-host requirements:
 - Rich controller metadata.
 - Gamepad output callbacks.
 - Keyboard and mouse input paths.
-- Linux PlayStation gamepads through `uhid`, Generic/Xbox/Switch Pro gamepads
-  through `uinput`, and `uinput` keyboard/pointer devices.
+- Linux PlayStation and Switch Pro gamepads through `uhid`, Generic/Xbox
+  gamepads through `uinput`, and `uinput` keyboard/pointer devices.
+- Native Switch Pro motion, initialization replies, rumble, and player-light
+  output handling on Linux and Windows descriptor-driven backends.
 - Linux DualSense and DualShock 4 USB/Bluetooth report handling.
 - Linux touchscreen, trackpad, and pen tablet device types.
 - FreeBSD uinput gamepads and pointer devices, with basic PlayStation input and

docs/streaming-host-integration.md

@@ -105,8 +105,8 @@ default when a static target is available.
 The UI can create and remove gamepads from the built-in profiles, submit
 buttons, sticks, triggers, and battery state, show backend and profile
 capabilities, list device nodes reported for UI-created devices, and display
-normalized gamepad output such as rumble, RGB LED, adaptive trigger, trigger
-rumble, and raw report events delivered through the normal callback path. Button
+normalized gamepad output such as rumble, RGB LED, player LED, adaptive trigger,
+trigger rumble, and raw report events delivered through the normal callback path. Button
 controls are momentary by default, so they behave like physical gamepad buttons;
 on Windows, the UI also displays broker license status and can activate,
 refresh, or deactivate a machine license without elevation. Windows UMDF
@@ -229,10 +229,11 @@ through 16 in the input report. Linux may still route that profile through
 `uinput`, where the backend exposes those same logical directions through the
 standard `ABS_HAT0X` and `ABS_HAT0Y` axes.
 
-Profiles advertise support for features such as rumble, trigger rumble, RGB
-LEDs, adaptive triggers, motion sensors, touchpads, battery state,
-profile-specific buttons, and raw output reports. Consumers should query profile and
-backend capabilities before warning users about unsupported client features.
+Profiles advertise support for features such as rumble, trigger rumble, RGB and
+player LEDs, adaptive triggers, motion sensors, touchpads, battery state,
+profile-specific buttons, and raw output reports. Consumers should query
+profile and backend capabilities before warning users about unsupported client
+features.
 The `misc1` button represents Share/Capture/Mic Mute-style controls and is
 available on the generic, Xbox Series, DualSense, and Switch Pro profiles; Xbox
 360 and Xbox One do not advertise that extra button.

docs/usage.md

@@ -427,7 +427,9 @@ gamepad.
 
 DualShock 4 and DualSense answer the calibration, pairing, and firmware feature
 requests used by their Windows HIDAPI initialization paths. Switch Pro answers
-the native USB and subcommand handshake and submits native `0x30` input reports.
+the native USB and subcommand handshake and submits native `0x30` input reports
+with three live IMU samples. Its Set Player Lights subcommand is normalized into
+solid and flashing player-indicator output states for the creating runtime.
 The built-in Generic profile is presented to Windows as a DirectInput PID
 Joystick with the complete output-report set required for DirectInput
 enumeration. Constant Force and Sine output is normalized to the portable

docs/windows-driver.md

@@ -83,6 +83,7 @@ namespace lvh {
     support.supports_rumble = profile.capabilities.supports_rumble;
     support.supports_rgb_led = profile.capabilities.supports_rgb_led;
     support.supports_adaptive_triggers = profile.capabilities.supports_adaptive_triggers;
+    support.supports_player_leds = profile.capabilities.supports_player_leds;
     support.supports_motion = profile.capabilities.supports_motion;
     support.supports_touchpad = profile.capabilities.supports_touchpad;
     support.supports_battery = profile.capabilities.supports_battery;
@@ -142,6 +143,8 @@ namespace lvh {
         return support.supports_rgb_led;
       case adaptive_triggers:
         return support.supports_adaptive_triggers;
+      case player_leds:
+        return support.supports_player_leds;
       case raw_report:
         return profile.output_report_size > 0U;
     }

src/core/gamepad_adapter.cpp

@@ -2031,7 +2031,12 @@ namespace lvh::profiles {
       profile.output_report_size = switch_pro_output_report_size;
       profile.name = "(libvirtualhid) Nintendo Pro Controller";
       profile.manufacturer = "Nintendo Co., Ltd.";
-      profile.capabilities = {.supports_rumble = true, .supports_motion = true, .supports_battery = true};
+      profile.capabilities = {
+        .supports_rumble = true,
+        .supports_motion = true,
+        .supports_battery = true,
+        .supports_player_leds = true,
+      };
       profile.report_descriptor = make_switch_pro_report_descriptor();
       return profile;
     }

src/core/profiles.cpp

@@ -75,6 +75,12 @@ namespace lvh::reports {
 
     constexpr std::size_t switch_rumble_output_report_size = 10;
 
+    constexpr std::uint8_t switch_set_player_lights_subcommand = 0x30;
+
+    constexpr float switch_acceleration_scale = 4096.0F / 9.80665F;
+
+    constexpr float switch_gyroscope_scale = 14.2842F;
+
     // SDL maps 16-bit rumble strengths to Nintendo's shared 101-step amplitude
     // scale. This is the inverse table for the packed high- and low-band values:
     // https://github.com/libsdl-org/SDL/blob/main/src/joystick/hidapi/SDL_hidapi_switch.c
@@ -1061,6 +1067,22 @@ namespace lvh::reports {
     report[offset + 2U] = to_byte((y >> 4U) & 0xFFU);
   }
 
+  void write_switch_imu_sample(
+    ByteReport &report,
+    std::size_t offset,
+    const Vector3 &acceleration,
+    const Vector3 &gyroscope
+  ) {
+    // Nintendo's native coordinate system differs from the portable
+    // PlayStation-style coordinate system exposed by GamepadState.
+    write_i16(report, offset, scale_i16(-acceleration.z, switch_acceleration_scale));
+    write_i16(report, offset + 2U, scale_i16(-acceleration.x, switch_acceleration_scale));
+    write_i16(report, offset + 4U, scale_i16(acceleration.y, switch_acceleration_scale));
+    write_i16(report, offset + 6U, scale_i16(-gyroscope.z, switch_gyroscope_scale));
+    write_i16(report, offset + 8U, scale_i16(-gyroscope.x, switch_gyroscope_scale));
+    write_i16(report, offset + 10U, scale_i16(gyroscope.y, switch_gyroscope_scale));
+  }
+
   std::byte switch_battery_and_connection(const std::optional<GamepadBattery> &battery) {
     constexpr auto usb_connection = std::byte {0x01};
     if (!battery.has_value()) {
@@ -1222,6 +1244,11 @@ namespace lvh::reports {
       normalize_switch_stick_axis(normalized.right_stick.x),
       normalize_switch_stick_axis(normalized.right_stick.y)
     );
+    const auto acceleration = normalized.acceleration.value_or(Vector3 {.y = 9.80665F});
+    const auto gyroscope = normalized.gyroscope.value_or(Vector3 {});
+    for (const auto offset : {13U, 25U, 37U}) {
+      write_switch_imu_sample(report, offset, acceleration, gyroscope);
+    }
     return to_uint8_report(report);
   }
 
@@ -1309,6 +1336,23 @@ namespace lvh::reports {
         output.high_frequency_rumble = rumble->high_frequency;
         output.raw_report = report;
         outputs.push_back(std::move(output));
+      }
+      if (
+        report.size() >= 12U && report[0] == switch_rumble_and_subcommand_output_report_id &&
+        report[10] == switch_set_player_lights_subcommand
+      ) {
+        GamepadOutput output;
+        output.kind = GamepadOutputKind::player_leds;
+        const auto player_lights = std::byte {report[11]};
+        for (std::size_t index = 0; index < output.player_leds.size(); ++index) {
+          output.player_leds[index] = (player_lights & (std::byte {1} << index)) != zero_byte;
+          output.flashing_player_leds[index] =
+            (player_lights & (std::byte {1} << (index + 4U))) != zero_byte;
+        }
+        output.raw_report = report;
+        outputs.push_back(std::move(output));
+      }
+      if (!outputs.empty()) {
         return outputs;
       }
     }

src/core/report.cpp

@@ -69,6 +69,11 @@ namespace lvh {
      * @brief Number of rear paddle buttons exposed by the profile.
      */
     std::uint8_t supported_rear_paddle_count = 0;
+
+    /**
+     * @brief Whether the profile supports player indicator LED output.
+     */
+    bool supports_player_leds = false;
   };
 
   /**