Hello there, This RFC introduces support for the FS035VG158 LCD panel, cleaning up the nv3052c driver on the way and documentating existing panel code.
This patch series is at a bit of a standstill: I have gotten feedback that it should instead use the Leadtek LTK035C5444T panel init sequence instead of Fascontek's provided sequence which is almost identical. I don't feel comfortable providing a patch that does this unless someone can explain why the changes Fascontek have made aren't critical. I would like feedback to know if this is a blocker for this patch set, or otherwise what needs to be done to get it merged. John. v3 -> v4: - Mark panel_regs_len as unsigned v2 -> v3: - Dropped patches that add extra sleep time v1 -> v2: - Fixed a variable declaration style error - Cleaned up device tree yaml John Watts (7): drm/panel: nv3052c: Document known register names drm/panel: nv3052c: Add SPI device IDs drm/panel: nv3052c: Allow specifying registers per panel drm/panel: nv3052c: Add Fascontek FS035VG158 LCD display dt-bindings: display: panel: Clean up leadtek,ltk035c5444t properties dt-bindings: vendor-prefixes: Add fascontek dt-bindings: display: panel: add Fascontek FS035VG158 panel .../display/panel/fascontek,fs035vg158.yaml | 56 ++ .../display/panel/leadtek,ltk035c5444t.yaml | 8 +- .../devicetree/bindings/vendor-prefixes.yaml | 2 + .../gpu/drm/panel/panel-newvision-nv3052c.c | 515 +++++++++++++----- 4 files changed, 437 insertions(+), 144 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/panel/fascontek,fs035vg158.yaml -- 2.42.0
