[MISSING DOCS]: Driver device input profiles

[okawo80085]

Last weekend I had it in me to update some OpenVR docs But then I realized that there is no official docs on input profiles at all and my knowledge of them is all over the place (because it's just accumulated from a large number of examples I've seen in the wild)

EDIT: *There is official docs for input profiles in this repo, but they're next to useless, It only gives boiler plate examples that are 3 bazillion years out of date :L

Most of my questions are related to the "input_source" section, mainly:

• List of all allowed values for the "type" field
• What other fields can an input source have? So far I've seen toggleable "click", "touch", "force", "value" fields, and some unfamiliar string fields like "input_activity_path" and "capsense_source", and many many more
• Also what does the "visibility" field do? What values can this field have? (only seen it in index controller profiles)
• What are all paths a source can have or is it just divided into /input/*, /output/* and /pose/*?
• What sources are required for a device to function?
• (If this even makes sense) What is the expected driver implementation for a given input source type?

I have some assumptions for some of those, but most of them I'm completely out of ideas :/ Thanks in advance!

[inlet511]

Can't agree more, I have exactly the same demand on a decent document of input profile, and also legacy-bindings. For now I can only search around the github and look for scattering pieces of infomation.