On Thu, Jan 19, 2017 at 04:16:01PM +0000, Yannick FERTRE wrote: > On 01/16/2017 09:30 PM, Laurent Pinchart wrote: > > Hi Yannick, > > > > Thank you for the patch. > > > > On Monday 16 Jan 2017 14:28:58 Yannick Fertre wrote: > >> Signed-off-by: Yannick Fertre <yannick.fertre@xxxxxx> > >> --- > >> .../devicetree/bindings/display/st,ltdc.txt | 57 ++++++++++++++++++ > >> 1 file changed, 57 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/display/st,ltdc.txt > >> > >> diff --git a/Documentation/devicetree/bindings/display/st,ltdc.txt > >> b/Documentation/devicetree/bindings/display/st,ltdc.txt new file mode > >> 100644 > >> index 0000000..20e89da > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/display/st,ltdc.txt > >> @@ -0,0 +1,57 @@ > >> +* STMicroelectronics STM32 lcd-tft display controller > >> + > >> +- st-display-subsystem: Master device for DRM sub-components > >> + This device must be the parent of all the sub-components and is > >> responsible > >> + of bind them. > > > > Why do you need this ? At a quick glance the ltdc node should be enough. > Hi Laurent, > To prepare next device upstream of dsi, we need a master node > "st-display-subsystem" and a sub node "st,ltdc". It's the same kind of > node than st,stih4xx. No, you don't. That's what OF graph is for. The DRM driver binds to the LCD controller node and walks the graph to find the DSI node and then the panel. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
