xinput | grep -m 1 "DeathAdder" | sed 's/^.*id=\([0-9]*\)[ \t].*$/\1/'

returns:

8

xinput list-props 8

returns:

Device 'Razer Razer DeathAdder V2':
	Device Enabled (155):	1
	Coordinate Transformation Matrix (157):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (291):	0
	libinput Natural Scrolling Enabled Default (292):	0
	libinput Scroll Methods Available (293):	0, 0, 1
	libinput Scroll Method Enabled (294):	0, 0, 0
	libinput Scroll Method Enabled Default (295):	0, 0, 0
	libinput Button Scrolling Button (296):	2
	libinput Button Scrolling Button Default (297):	2
	libinput Middle Emulation Enabled (298):	0
	libinput Middle Emulation Enabled Default (299):	0
	libinput Accel Speed (300):	0.698529
	libinput Accel Speed Default (301):	0.000000
	libinput Accel Profiles Available (302):	1, 1
	libinput Accel Profile Enabled (303):	1, 0
	libinput Accel Profile Enabled Default (304):	1, 0
	libinput Left Handed Enabled (305):	0
	libinput Left Handed Enabled Default (306):	0
	libinput Send Events Modes Available (276):	1, 0
	libinput Send Events Mode Enabled (277):	0, 0
	libinput Send Events Mode Enabled Default (278):	0, 0
	Device Node (279):	"/dev/input/event7"
	Device Product ID (280):	5426, 132
	libinput Drag Lock Buttons (307):	<no items>
	libinput Horizontal Scroll Enabled (308):	1

Button drag lock holds a button logically down even when the button itself has been physically released since.

Button drag lock comes in two modes:

1. meta mode: A meta button click activates drag lock for the next button press of any other button.
   • A button click in the future will keep that button held logically down until a subsequent click of that same button.
   • The meta button events themselves are discarded.
   • A separate meta button click is required each time a drag lock should be activated for a button in the future.
2. pairs mode: Each button can be assigned a target locking button.
   • On button click, the target lock button is held logically down until the next click of the same button.
   • The button events themselves are discarded and only the target button events are sent.

The pressure curve affects how stylus pressure is reported.

• By default, the hardware pressure is reported as-is.
• By setting a pressure curve, the feel of the stylus can be adjusted to be more like e.g. a pencil or a brush.

The pressure curve is a cubic Bezier curve, drawn within a normalized range of 0.0 to 1.0 between the four points provided.

• This normalized range is applied to the tablets pressure input so that the highest pressure maps to 1.0.
• The points must have increasing x coordinates, if x0 is larger than 0.0 all pressure values lower than x0 are equivalent to y0.
• If x3 is less than 1.0, all pressure values higher than x3 are equivalent to y3.

The input for a linear curve (default) is “0.0/0.0 0.0/0.0 1.0/1.0 1.0/1.0”;

• a slightly depressed curve (firmer) might be “0.0/0.0 0.05/0.0 1.0/0.95 1.0/1.0”;
• a slightly raised curve (softer) might be “0.0/0.0 0.0/0.05 0.95/1.0 1.0/1.0”.

By default, a tablet tool can access the whole sensor area and the tablet area is mapped to the available screen area.

• For external tablets, the height:width ratio of the tablet may be different to that of the monitor, causing the skew of input data.

To avoid this skew of input data, an area ratio may be set to match the ratio of the screen device.

• For example, a ratio of 4:3 will reduce the available area of the tablet to the largest available area with a ratio of 4:3.
• Events within this area will scale to the tablets announced axis range, the area ratio is thus transparent to the X server.
• Any events outside this area will send events equal to the maximum value of that axis.
• The area always starts at the devices origin in its current rotation, i.e. it takes left-handed-ness into account.

https://wayland.freedesktop.org/libinput/doc/

https://wiki.ubuntu.com/X/InputCoordinateTransformation

https://www.mankier.com/4/libinput#Configuration_Details