hidpp10_set_register(9)
β¨ NAME β¨
hidpp10_set_register β bestie, this is the one that modifies a HID++ 1.0 register π
(yes, that's section 9 of the Kernel API Manual, we're in the big leagues now π)
πΈ SYNOPSIS πΈ
int hidpp10_set_register (struct hidpp_device *hidpp_dev , u8
register_address , u8 byte , u8 mask , u8 value );
okay so like, it hands you back an int at the end, we'll get to that π«Ά
π¦ ARGUMENTS π¦
hidpp_devβ the device you're setting the register on. your main character device, if you will πregister_addressβ the address of the register you wanna modify. it's giving "the vibe check location" πbyteβ which byte of that register you're modifying. and listen β this one should be less than 3. no cap, keep it under 3 or it's not it πmaskβ the mask of the bits you're gonna modify. like a little stencil for which bits get the glow-up β¨valueβ the new values for the bits inmask. this is the actual tea being spilled π
π RETURN π
So it returns 0 if it worked β slay, iconic, ate π
β and otherwise you get a negative error code. sad girl hours π Fr fr, anything that isn't 0 means something went sideways.
π SEE ALSO π
./drivers/hid/hid-logitech-hidpp.cβ the kernel file itself, go read it, it's lowkey a whole journey π§struct hidpp_scroll_counter(9)β the struct, very demure, very mindful πhidpp_scroll_counter_handle_scroll(9)β the scroll handler, its bestie π«Ά
β real talk: byte should be less than 3. that's not me being dramatic, that's just what the page says and i would never lie to you π
and that's the whole thing, bestie!! this page is from ./drivers/hid π dated October 2026 β like, future vibes, we love to see it. go forth and set those registers, you've absolutely got this π₯ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms