Tool/software:
Hi Ti-teams,
Our Android system included Android board + DS90UB949-Q1EVM + UB948 + Touchscreen,
and touchscreen used 32-bits controller, and its timing was as below.
Android board connected to DS90UB949-Q1EVM's J20 connector for I2C communication.
We tried 2 settings for touch-controller interrupt (only scanned out its I2C-address 0x5D(7 bits)), but all failed touch-function.
1. Interrupt of touch-controller connected to INTB-IN of UB948, then FPD-link, and connected INTB (J23 pin3 & pin4) of UB949-EVM,
I2C of Android board connected to J20 of UB949-EVM.
Register setting of UB949: 0xC6 was 0x21, 0x03 was 0xDA, 0x07 was 0xBA(touch controller 8bits-address), 0x08 was 0xBA
Register setting of UB948: 0x03 was 0xFB, 0x05 was 0x9E, 0x1E was 0x53
(GPIO1: Touch IC interrupt active high Input, GPIO2: Touch IC Reset active low Output)
2. Interrupt of touch-controller connected to GPIO1 of UB948, then FPD-link, and connected INTB (J23 pin3 & pin4) of UB949-EVM,
I2C of Android board connected to J20 of UB949-EVM.
Register setting of UB949: 0x0E was 0x53, 0x03 was 0xDA, 0x07 was 0xBA(touch controller 8bits-address), 0x08 was 0xBA
Register setting of UB948: 0x03 was 0xFB, 0x05 was 0x9E, 0x1E was 0x53
(GPIO1: Touch IC interrupt active high Input, GPIO2: Touch IC Reset active low Output)
Hope for your support