On Fri, Sep 16, 2022 at 7:44 AM TimH <t...@jti.uk.com.invalid> wrote: > >> At present (by default/out of the box) there are two drivers - one for > >> the TS, registered as /dev/input0, the other for the ADC, as > >> /dev/adc0. There are, indeed, counts for each separate driver, but no > >"cross-coupling". > >> > >> Perhaps the TS driver needs to be rolled into the ADC driver for this chip? > > > > > > > >If it's using the same physical hardware peripheral then they will indeed > >need > >to be coordinated somehow, or combined. Not sure what specifically to > >suggest here. > > > >Nathan > > Since all SAMA5Dx devices provide touchscreen support using the built-in ADC > there is definitely an argument to move the touchscreen code into the ADC > code. It will need a Kconfig bool to enable/disable this built-in support, as > there is no reason a given design might not use an external TS controller > chip - the built-in ADC support is only for resistive touchscreens, so any > capacitive type will still need the external device, for example.
Sounds sensible to me. Cheers, Nathan
