Let me share a brief reply here. Since 2017 we have rewritten about half of hid-sony to support our controllers well (in particular ds4) and this is all upstream. The driver wasn't in good shape. Now we use it extensively and pretty much all mobile devices with a Linux kernel will use it this year.
The challenge for us is mostly on the technical side as I mentioned on linux-input as well: https://lore.kernel.org/lkml/CAEc3ja...ail.gmail.com/. These devices kind of look and behave like ours, but they are different. They often use different HID descriptors and have other differences. We don't have their datasheets or know how they work. If the code is in our "official" driver, we can't vouch for the quality, it can cause regressions for our official controllers. We would also have to QA the driver for those devices etcetera. It causes issues for our partners etcetera. Ideally such code would live in a different driver supported by the community, but since these device use our vendor / product ids, that's not that easy.
The challenge for us is mostly on the technical side as I mentioned on linux-input as well: https://lore.kernel.org/lkml/CAEc3ja...ail.gmail.com/. These devices kind of look and behave like ours, but they are different. They often use different HID descriptors and have other differences. We don't have their datasheets or know how they work. If the code is in our "official" driver, we can't vouch for the quality, it can cause regressions for our official controllers. We would also have to QA the driver for those devices etcetera. It causes issues for our partners etcetera. Ideally such code would live in a different driver supported by the community, but since these device use our vendor / product ids, that's not that easy.
Comment