Am Mittwoch, den 04.11.2015, 21:28 -0600 schrieb Rob Herring: > On Wed, Nov 04, 2015 at 12:44:58PM +0100, Philipp Zabel wrote: > > From: CK Hu <ck.hu@xxxxxxxxxxxx> > > > > Add device tree binding documentation for the display subsystem in > > Mediatek MT8173 SoCs. > > > > Signed-off-by: CK Hu <ck.hu@xxxxxxxxxxxx> > > Signed-off-by: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx> > > If this wasn't an RFC, I'd ack it. :) One thing you missed below though. Alright, thanks for your help in sorting these bindings out. [...] > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt > > new file mode 100644 > > index 0000000..cc3d884 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt [...] > > +DISP function blocks > > +==================== > > + > > +A display stream starts at a source function block that reads pixel data from > > +memory and ends with a sink function block that drives pixels on a display > > +interface, or writes pixels back to memory. All DISP function blocks have > > +their own register space, interrupt, and clock gate. The blocks that can > > +access memory additionally have to list the IOMMU and local arbiter they are > > +connected to. > > + > > +For a description of the display interface sink function blocks, see > > +Documentation/devicetree/bindings/drm/mediatek/mediatek,dsi.txt and > > +Documentation/devicetree/bindings/drm/mediatek/mediatek,dpi.txt. > > Need to update these paths. Will do. regards Philipp -- 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
