Display Touch input not mapped properly with primary display

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Display Touch input not mapped properly with primary display

ソリューションへジャンプ
745件の閲覧回数
adithysm65
Contributor I

We are attempting to set up two displays and enable touch on the primary display for the i.MX 8 QuadMax MEK CPU Board using an LVDS to HDMI Adapter Card. We are using a USB Type-C connector (J17) for the touch input.

Here are the observations we have made:

The input is recognized but is not getting mapped when we connect the touch input to the primary display. However, when we connect it to the secondary display, the touch input works perfectly.

As a workaround, we interchanged the display ports, i.e., primary to secondary and vice versa. The secondary screen then takes up the resolution of the primary screen, which is not ideal for our project.

Following are the responses and logs received.

 
 



  • $ adb shell dumpsys SurfaceFlinger --display-id 
    • Display 4632668096568543232 (HWC display 0): port=0 pnpId=RTK displayName="WaveShare"[15.6] 
    • Display 4624778001127622657 (HWC display 1): port=1 pnpId=KTC displayName="WaveShare"[12.3]  
      • [Touch input to primary display] 
        • $ adb shell getevent -i | grep location   
          • location: "imx-sc-pwrkey/input0" 
           
        • adb shell getevent -i  

add device 1: /dev/input/event0 

  bus:      0019 

  vendor    0000 

  product   0000 

  version   0000 

  name:     "sc-powerkey" 

  location: "imx-sc-pwrkey/input0" 

  id:       "" 

  version:  1.0.1 

  events: 

    KEY (0001): 0074  

  input props: 

    <none> 

[Touch input to secondary display] 

  • $adb shell getevent -i | grep location 
    •   location: "usb-xhci-hcd.1.auto-1/input0" 
    •   location: "imx-sc-pwrkey/input0" 

 

  • adb shell getevent -i  

add device 1: /dev/input/event1 

  bus:      0003 

  vendor    0712 

  product   000a 

  version   0111 

  name:     "HID 0712:000a" 

  location: "usb-xhci-hcd.1.auto-1/input0" 

  id:       "" 

  version:  1.0.1 

  events: 

    KEY (0001): 014a  

    ABS (0003): 0000  : value 0, min 0, max 1920, fuzz 0, flat 0, resolution 4 

                0001  : value 0, min 0, max 720, fuzz 0, flat 0, resolution 2 

                002f  : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0 

                0035  : value 0, min 0, max 1920, fuzz 0, flat 0, resolution 4 

                0036  : value 0, min 0, max 720, fuzz 0, flat 0, resolution 2 

                0039  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0 

    MSC (0004): 0005  

  input props: 

    INPUT_PROP_DIRECT 

add device 2: /dev/input/event0 

  bus:      0019 

  vendor    0000 

  product   0000 

  version   0000 

  name:     "sc-powerkey" 

  location: "imx-sc-pwrkey/input0" 

  id:       "" 

  version:  1.0.1 

  events: 

    KEY (0001): 0074  

  input props: 

    <none> 

0 件の賞賛
返信
1 解決策
704件の閲覧回数
Zhiming_Liu
NXP TechSupport
NXP TechSupport
0 件の賞賛
返信
2 返答(返信)
705件の閲覧回数
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @adithysm65 

Have you tried to modify the input-port-associations.xml file in aosp?

https://github.com/nxp-imx-android/android-imx_device_fsl/blob/android-13.0.0_2.2.0/imx8q/mek_8q/inp...

 

0 件の賞賛
返信
698件の閲覧回数
adithysm65
Contributor I

Hello @Zhiming_Liu ,

Thanks for the solution,got the touch mapping right.

Just for someone with same blocker,

1)The 'input-port-associations.xml' is located under  /vendor/etc.
2)Check the input configuration of the display using the command $getevent -i | grep location.
3)Now change the configurations of the display mentioned under the xml file.

0 件の賞賛
返信