shields: nxp: lcd_par_s035: fix gt911 touch initialization

[DerekSnell]

Fixes #98876

Defers init of GT911 touch, MIPI DBI, and display device drivers. lcd_par_s035_init() in shield.c now initializes these to control the GT911 INT_GPIO state during the Reset sequence.

• Fixes issue with this shield caused by shared Reset signal between the GT911 and display driver.
• Removes reset-gpios property from gt911 node. The GT911 driver does not need to assert the Reset signal because the display driver asserts Reset before the GT911 driver initializes.

Tested this fix on the following:

• LCD_PAR_S035 shield with FRDM_MCXN947
• LCD_PAR_S035 shield with FRDM_RW612

This capture is from the LCD_PAR_S035 with the FRDM_RW612 and this change applied. The GT911 INT_GPIO is driven low first, then the LCDIC display driver asserts Reset and INT_GPIO remains low through the init process.

[JarmouniA]

Can't you deffer the initialization of display & touch controllers and do the setup in the right order in the board's (or shield's, if that's a thing) board.c?
I really do not like seeing code in the touch controller driver that actually has nothing to do with it, and it's solving a problem created by the shield.

[decsny]

Can't you deffer the initialization of display & touch controllers and do the setup in the right order in the board's (or shield's, if that's a thing) board.c? I really do not like seeing code in the touch controller driver that actually has nothing to do with it, and it's solving a problem created by the shield.

I don't see how deferred initialization fixes this. Whether you defer or not you still have to have the same patch @DerekSnell submitted here.

[decsny]

Actually I think we added the ability to put code in shields, if I'm remembering correctly, and I think I understand @JarmouniA suggestion now. It could be possible to do this by deferred initialization and handle init in shield code.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[DerekSnell]

Can't you deffer the initialization of display & touch controllers and do the setup in the right order in the board's (or shield's, if that's a thing) board.c?

Hi @JarmouniA ,
Great idea! I reworked this PR as you suggested, and I agree this is much cleaner. The PR only updates the shield and does not need to touch any drivers. Thanks for the feedback

addressed