In the past I've seen (and contributed to) hacks that model the chips as
phy or even (really!) clock drivers. Since the chip usually sits between
a signal that is (almost) HDMI and a HDMI connector, I decided to stop
lying and write it as a DRM bridge driver.
I'm fully aware that both bindings and driver require some more rework,
the bindings aren't complete yet and the driver needs some more #defines
for bitfields and such (the core code is over 5 years old).
My main question to the maintainers here: Is this a viable solution?
And if so, I'll do my best to document and clean it up further...
Mike Looijmans (2):
dt-bindings: drm/bridge: ti-tmds181: Add TI TMDS181 and SN65DP159
bindings
drm: bridge: Add TI tmds181 and sn65dp159 driver
.../bindings/display/bridge/ti,tmds181.yaml | 104 ++++
drivers/gpu/drm/bridge/Kconfig | 11 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/ti-tmds181.c | 512 ++++++++++++++++++
4 files changed, 628 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/ti,tmds181.yaml
create mode 100644 drivers/gpu/drm/bridge/ti-tmds181.c
--
2.43.0
base-commit: 53e760d8949895390e256e723e7ee46618310361
branch: drm-ti-tmds181
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topic.nl
W: www.topic.nl
Please consider the environment before printing this e-mail
