drivers: input: sbus remote controller support

[PetervdPerk-NXP]

Add support SBUS RC controller connected through UART

@fabiobaltieri Only open point is the discord discourse regarding event id for signalling status.

I think an event id corresponding to the devices becoming available/unavailabile is not a bad idea in principle as that's effectively the equivalent of an /dev/input node appearing and disappearing

[fabiobaltieri]

@fabiobaltieri Only open point is the discord discourse regarding event id for signalling status.

Yeah I thought a bit more about it, since you mentioned you are interested in more transports I'm thinking you probably want more flexibility than just "connected/disconnected", I'd imagine stuff like rssi, transmitter battery, identification, stuff like that... I think it's better to go for a custom callback at this stage so you have full flexibility to add what you need, we can always look into unifying things later and keep the driver api for backward compability.

[PetervdPerk-NXP]

Thanks for the review and coding tips, wasn't aware of the use of BUILD_ASSERT with DT_PROP very nice feature to statically check dts configs.

I think it's better to go for a custom callback at this stage so you have full flexibility to add what you need, we can always look into unifying things later and keep the driver api for backward compability.

I'll take look at the callback when I'll find time to implement CRSF which gives way more metadata.

[bperseghetti]

Tested this with a few SBUS receivers on different boards and works great, I think only thing left is any other things @fabiobaltieri might desire changed?

[fabiobaltieri]

unaddressed