sensor_hub_...tribute_info(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 sensor_hub_input_get_attribute_info(9) 🎀

okay so welcome to the Kernel API Manual, section 9 bestie — this is the page for sensor_hub_input_get_attribute_info, and no I will not be shortening that name, it's giving full government name energy and we respect it 💅

✨ NAME ✨

sensor_hub_input_get_attribute_info — get an attribute information 🫶

🌸 SYNOPSIS 🌸

int sensor_hub_input_get_attribute_info (struct hid_sensor_hub_device
*hsdev , u8 type , u32 usage_id , u32 attr_usage_id , struct
hid_sensor_hub_attribute_info *info );

like, that's the whole signature, no cap 📎

🦋 ARGUMENTS 🦋

  • hsdev — the hub device instance, aka the main character of this whole situation 👑
  • type — type of this attribute, and it's one of input/output/feature 🍓
  • usage_id — the attribute usage id of the parent physical device, as per spec 📖
  • attr_usage_id — the attribute usage id, also as per spec, yes there are two of them and yes you need both 🙈
  • info — where the info goes: it returns information about the attribute after parsing the report 💌

💖 DESCRIPTION 💖

so what it actually does: it parses the report and hands you back the attribute information — think report id, field index, units, exponent, etc. ✨ literally the whole little info bundle, parsed and served 🧚

ngl the "etc." at the end is doing a lot of heavy lifting, but that's what the original says so that's what we're saying 💀

💫 SEE ALSO 💫

kernel file ./include/linux/hid-sensor-hub.h — go read it, iykyk 📂

like a whole friend group of functions, obsessed 🌈

okay that's the page!! sourced from ./include/linux, dated October 2026, and yes the title up top still says sensor_hub_...tribute_info(9) because the header truncates it and we simply don't fight the header 💜 mwah, go parse some reports bestie 🫶✨🎀

📦 where this page comes from