TPS65235: TPS65235 Detection error problem

Hello, we currently have a case of using TPS65235, and the customer has reported a problem: When 22K is turned on, the cable detection mechanism of TPS65235 will cause false positives.
The simple schematic diagram of our board is as follows. Simply put, when the customer finds that no cable is plugged in, turn on 22k, and the register CABLE_GOOD will switch back and forth between 0/1, which means that the cable detection mechanism of TPS65235 is misjudged , But there is no such problem when 22K is turned off. Please help analyze the problem, is there a way to fix it from the software level, or it needs hardware rectification.

Steps to reproduce:

1. Use Stingray 4.15.59 or later (excluding "special" versions with disabled LNB polling)
2. Make sure Stingray has started in Factory mode
3. Setup Stingray logs. Open UART console and type the following commands:

1. log mute off
2. log Error
3. log named DVBSTuner Info

• Provide LNB power is enabled and 22kHz tone is on. Go to Antenna editor. Select testAntenna0 and make the following settings:

1. LNB Setup: Custom
2. DiSEqC: None
3. Tone 22 kHz: Enabled
4. Voltage mode: Normal

• Save settings. Go to testAntenna2 and do the same settings.
• Go to "STB Settings" / "Antenna" and disable all checkboxes here
• Make sure no any antenna cable is connected.
• Go to "Manual search". Select "ABS 1" (will activate RF IN1). Enter any valid frequency. Don't connect any cable. Observe UART logs for ~1 min
• Select "Apstar 6" (will activate RF IN2). Observe UART logs

          Actual Result:

          For RF IN1. False-positive Cable detection is triggered with random interval:

                   [18/01/2021 13:19:12.505] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: true

       [18/01/2021 13:19:12.510] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: false

       [18/01/2021 13:19:23.828] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: true

       [18/01/2021 13:19:23.833] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: false

       [18/01/2021 13:19:27.602] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: true

       [18/01/2021 13:19:27.607] [Info] {tunerExecutor:serverTuner} [DVBSTuner] serverTuner connected: false

  For RF IN2. False-positive Cable detection is triggered with random interval.             

       [18/01/2021 13:22:24.073] [Info] {tunerExecutor:clientTuner} [DVBSTuner] clientTuner connected: true

       [18/01/2021 13:22:24.076] [Info] {tunerExecutor:clientTuner} [DVBSTuner] clientTuner connected: false

       [18/01/2021 13:22:27.850] [Info] {tunerExecutor:clientTuner} [DVBSTuner] clientTuner connected: true

       [18/01/2021 13:22:27.855] [Info] {tunerExecutor:clientTuner} [DVBSTuner] clientTuner connected: false

  BUT after several minutes there is no Cable detecton and behaviour looks normal.