On 02/28/14 13:20, Tomi Valkeinen wrote:
This series is a re-send of
http://article.gmane.org/gmane.linux.drivers.devicetree/61739
...
Shortly about the display components in the series, in the order of probable
public interest:
* Analog TV, DVI and HDMI Connectors represent a respective connector on the
board. They don't do much, but they do mark the end of the video pipeline (from
the board's pov), and they should also in the future offer ways to handle
things like the +5V pin on DVI and HDMI connector and HPD pin.
* MIPI DPI panel and MIPI DSI CM panels represent bindings for simple panels
using the respective video bus.
* Sony acx565akm is an SPI controlled panel using flatlink video bus.
* TFP410 is a DPI to DVI encoder.
* TPD12S015 is a HDMI companion chip, used on OMAP boards.
Tomi,
Out of curiosity, will there be DT nodes for pull-up resistors soon,
too? ;)
Honestly, TPD12S015 is a level shifter, there is nothing in it that
would justify a DT node nor a driver.
Above you already note, that connector nodes should offer HPD in the
future, but I guess the binding should represent that now already.
I will be a DT stub anyway, the corresponding video sink driver will
have to look it up.
Looking through the bindings for DVI and HDMI, I guess HPD gpio is
better kept in those nodes. From the relevant (DT) properties DVI and
HDMI connectors are in no way different.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 28/02/14 14:57, Sebastian Hesselbarth wrote:
Out of curiosity, will there be DT nodes for pull-up resistors soon,
too? ;)
If they don't work automatically, yes, we need DT nodes and drivers for
them.
Honestly, TPD12S015 is a level shifter, there is nothing in it that
would justify a DT node nor a driver.
TPD requires a power. Who turns that on? It also has two GPIOs, LS_OE
and CT_CP_HPD, which need to be controlled based on what the user wants
and the state of the HPD line. Who controls those?
Above you already note, that connector nodes should offer HPD in the
future, but I guess the binding should represent that now already.
I think it can be added when somebody uses it. I don't see why that
would cause trouble later to those that don't use it.
I will be a DT stub anyway, the corresponding video sink driver will
have to look it up.
I'm not sure what you mean with that. Yes, it's not the most complex DT
nodes out there.
Looking through the bindings for DVI and HDMI, I guess HPD gpio is
better kept in those nodes. From the relevant (DT) properties DVI and
HDMI connectors are in no way different.
Well, I think the HPD gpio should be where it's most logical to have it.
I mean, you could have a setup where you have the SoC HDMI encoder and
and the HDMI connector, and the HPD pin goes directly to the HDMI
encoder, which has HW support for it. In that case, the HDMI encoder
node should contain the HPD, and the HDMI encoder should handle it.
Or, your HDMI encoder could not have any kind of support for HPD. In
that case you could have the HDMI connector driver handle the hotplug
event. You could of course make the HDMI encoder driver handle the HPD
gpio, but I usually try to have the driver handle the hardware device in
question.
In OMAP's case, we have the TPD chip between the HDMI encoder and the
connector, and the logical place to handle HPD GPIO in that case is the
TPD driver, as that's where the HPD is connected to and the TPD needs to
be configured according to the state of the HPD.
Tomi
Hi,
Am Freitag, den 28.02.2014, 13:57 +0100 schrieb Sebastian Hesselbarth:
On 02/28/14 13:20, Tomi Valkeinen wrote:
quoted
This series is a re-send of
http://article.gmane.org/gmane.linux.drivers.devicetree/61739
...
quoted
Shortly about the display components in the series, in the order of probable
public interest:
* Analog TV, DVI and HDMI Connectors represent a respective connector on the
board. They don't do much, but they do mark the end of the video pipeline (from
the board's pov), and they should also in the future offer ways to handle
things like the +5V pin on DVI and HDMI connector and HPD pin.
* MIPI DPI panel and MIPI DSI CM panels represent bindings for simple panels
using the respective video bus.
* Sony acx565akm is an SPI controlled panel using flatlink video bus.
* TFP410 is a DPI to DVI encoder.
* TPD12S015 is a HDMI companion chip, used on OMAP boards.
Tomi,
Out of curiosity, will there be DT nodes for pull-up resistors soon,
too? ;)
Honestly, TPD12S015 is a level shifter, there is nothing in it that
would justify a DT node nor a driver.
Above you already note, that connector nodes should offer HPD in the
future, but I guess the binding should represent that now already.
I will be a DT stub anyway, the corresponding video sink driver will
have to look it up.
Looking through the bindings for DVI and HDMI, I guess HPD gpio is
better kept in those nodes. From the relevant (DT) properties DVI and
HDMI connectors are in no way different.
I like the idea of adding actual connector nodes to the board device
trees. A TV encoder driver for example could this way detect from the
device tree whether it is connected to a VGA, Composite, or S-Video
connector (or maybe to both Composite and S-Video connectors at the same
time).
regards
Philipp