interrupt-parent = <&gpio1>; // gpio1_17
pin P9_23
interrupts = <0x17 0x0>;
gpio1_17 -> 17
0x17 -> 23 -> gpio1_23...
interrupts = <0x17 0x0> change to interrupts = <0x23 0x0> ?
This is SO confusing sometimes
On 2/24/2018 11:28 AM, Robert Nelson wrote:
> On Sat, Feb 24, 2018 at 12:13 PM, evilwulfie <evilwul...@gmail.com> wrote:
>> Does anybody happen to have a Capacitive touch screen using
>> the edt_ft5x06 driver hooked up to a bone ?
>>
>> If anybody does can you send me the output of "i2cdump 1 0x38"
>>
>> I have a buydisplay.com tft with cap touch.
>>
>> it uses a ft5x06 controller
>>
>> It may be that the current driver built into the kernel will not
>> function with a non etd touch panel
>>
>> Its all hooked up correctly I see the device @ 0x38 I think i have the
>> overlay correct it looks like
>> all other overlays when it comes to this type of touch panel
>> i see nothing using these commands related to a display
>>
>> dmesg | grep i2c
>> dmesg | grep input
>>
>> I can see the IRQ pin go low when i press on the display
>>
>> I dont see any interrupts assigned although i asked for one in the overlay
>>
>>
>> section in fragment@0 of overlay
>>
>> edt_ft5x06_pins: pinmux_edt_ft5x06_pins {
>> pinctrl-single,pins = <
>> BONE_P9_23 (PIN_INPUT_PULLUP |
>> MUX_MODE7) // interrupt for touch
>> >;
>>
>> here is fragment 1 where touch is
>>
>> fragment@1 {
>> target = <&i2c1>;
>> __overlay__ {
>> pinctrl-names = "default";
>> pinctrl-0 = <&bb_i2c1_pins>;
>> status = "okay";
>>
>> clock-frequency = <400000>;
>>
>> /* shut up DTC warnings */
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> // touch screen controller on ER-TFTM070-5
>>
>> touch: edt-ft5x06@38 {
>> status = "okay";
>> compatible =
>> "edt,edt-ft5306","edt,edt-ft5406","edt,edt-ft5206","edt,edt-ft5x06";
>>
>> pinctrl-names = "default";
>> pinctrl-0 = <&edt_ft5x06_pins>;
>>
>> reg = <0x38>;
>> interrupt-parent = <&gpio1>; // gpio1_17
>> pin P9_23
>> interrupts = <0x17 0x0>;
> gpio1_17 -> 17
>
> 0x17 -> 23 -> gpio1_23...
>
> Regards,
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/acd9f54a-80b0-8bfe-d22d-8d3e3afa7d5c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
