Message-ID: <CAL_JsqJLB+jsWxnXO9f-yFfY=1JPibV_4pNLxJNPwRE9CeePyg@mail.gmail.com>
Date:   Tue, 22 Jan 2019 10:06:12 -0600
From:   Rob Herring <robh+dt@...nel.org>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     Lubomir Rintel <lkundrak@...sk>,
        Mark Rutland <mark.rutland@....com>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/6] dt-bindings: display: armada: Add display subsystem binding

On Tue, Jan 22, 2019 at 4:58 AM Russell King - ARM Linux admin
<linux@...linux.org.uk> wrote:
>
> On Mon, Jan 21, 2019 at 05:58:50PM -0600, Rob Herring wrote:
> > On Mon, Jan 21, 2019 at 11:53 AM Russell King - ARM Linux admin
> > <linux@...linux.org.uk> wrote:
> > >
> > > On Mon, Jan 21, 2019 at 10:07:11AM -0600, Rob Herring wrote:
> > > > On Mon, Jan 21, 2019 at 9:46 AM Lubomir Rintel <lkundrak@...sk> wrote:
> > > > >
> > > > > On Mon, 2019-01-21 at 09:35 -0600, Rob Herring wrote:
> > > > > > On Sun, Jan 20, 2019 at 11:26 AM Lubomir Rintel <lkundrak@...sk> wrote:
> > > > > > > The Marvell Armada DRM master device is a virtual device needed to list all
> > > > > > > nodes that comprise the graphics subsystem.
> > > > > > >
> > > > > > > Signed-off-by: Lubomir Rintel <lkundrak@...sk>
> > > > > > > ---
> > > > > > >  .../display/armada/marvell-armada-drm.txt     | 24 +++++++++++++++++++
> > > > > > >  1 file changed, 24 insertions(+)
> > > > > > >
> > > > > > > diff --git a/Documentation/devicetree/bindings/display/armada/marvell-armada-drm.txt b/Documentation/devicetree/bindings/display/armada/marvell-armada-drm.txt
> > > > > > > index de4cca9432c8..3dbfa8047f0b 100644
> > > > > > > --- a/Documentation/devicetree/bindings/display/armada/marvell-armada-drm.txt
> > > > > > > +++ b/Documentation/devicetree/bindings/display/armada/marvell-armada-drm.txt
> > > > > > > @@ -1,3 +1,27 @@
> > > > > > > +Marvell Armada DRM master device
> > > > > > > +================================
> > > > > > > +
> > > > > > > +The Marvell Armada DRM master device is a virtual device needed to list all
> > > > > > > +nodes that comprise the graphics subsystem.
> > > > > > > +
> > > > > > > +Required properties:
> > > > > > > +
> > > > > > > + - compatible: value should be "marvell,dove-display-subsystem",
> > > > > > > +   "marvell,armada-display-subsystem"
> > > > > > > + - ports: a list of phandles pointing to display interface ports of CRTC
> > > > > > > +   devices
> > > > > > > + - memory-region: phandle to a node describing memory to be used for the
> > > > > > > +   framebuffer
> > > > > > > +
> > > > > > > +Example:
> > > > > > > +
> > > > > > > +       display-subsystem {
> > > > > > > +               compatible = "marvell,dove-display-subsystem",
> > > > > > > +                            "marvell,armada-display-subsystem";
> > > > > > > +               memory-region = <&display_reserved>;
> > > > > > > +               ports = <&lcd0_port>;
> > > > > >
> > > > > > If there is only one device, you don't need this virtual node.
> > > > >
> > > > > By "one device" you mean one LCD controller (CRTC)?
> > > >
> > > > Yes.
> > >
> > > How does that work (as far as the Linux implementation) ?  I can't see
> > > a way that could work, while allowing the flexibility that Armada DRM
> > > allows (two completely independent LCD controllers as two separate DRM
> > > devices vs one DRM device containing both LCD controllers.)
> > >
> > > > > I suppose in the (single CRTC) example case, the display-subsystem node
> > > > > used to associate it with the memory region reserved for allocating the
> > > > > frame buffers from. Could that be done differently?
> > > >
> > > > Move memory-region to the LCD controller node.
> > >
> > > That doesn't work - it would appear in the wrong part of the driver.
> >
> > Why? You can fetch properties from other nodes.
> >
> > If you have 2 CRTCs, do you have 1 or 2 reserved memory regions? I'd
> > think 2 with each one in the corresponding LCDC that uses them would
> > be more flexible.
>
> There would still be one reserved memory region, since it is shared
> between both LCDCs.
>
> > Or just get the data out of the /reserved-memory node directly. Surely
> > it has a compatible that you can find it with.
>
> I see that the DT reserved memory support has progressed since I wrote
> the armada code to deal with it, and it's now possible to make use of
> reserved memory via of_reserved_mem_lookup() rather than using the
> RESERVEDMEM_OF_DECLARE() and so forth.
>
> > > > > Also, if the node is indeed made optional, then it's going to
> > > > > complicate things on the DRM side. Currently the driver that binds to
> > > > > the node creates the DRM device once it sees all the components
> > > > > connected to the ports appear. If we loose it, then the LCD controller
> > > > > driver would somehow need to find out that it's alone and create the
> > > > > DRM device itself.
> > > >
> > > > DT is not the only way to create devices. The DRM driver can bind to
> > > > the LCDC node and then create a child CRTC device (or even multiple
> > > > ones for h/w with multiple pipelines).
> > >
> > > That seems completely upside down and rediculous to me - are you
> > > really suggesting that we should have some kind of virtual device
> > > in DT, and omit the _real_ physical devices for that, having the
> > > driver create the device with all the appropriate SoC resources?
> >
> > We create child platform devices that inherit from the parent in DT
> > all the time. MFD child drivers are a common case. Sometime the child
> > devices have DT nodes and sometimes they don't.
>
> I still don't think what you're saying is the right way to go about
> this.
>
> You _appear_ to be saying to group _both_ LCD controllers into one
> DT node, despite the fact that they are two separate devices with
> different mmio resources, interrupts etc, and have code in the
> kernel to split the DT device up into sub-devices.  IOW:

No, not at all. That was just an example of a h/w device having
virtual child platform devices. If you want to have 1 DRM device with
2 CRTCs, you have to do as described below.

I certainly want this to reflect the h/w. That's why we're having this
discussion.

[...]

> > Otherwise, do it the other way around. Create a virtual DRM device
> > conditioned on the SoC:
> >
> > if (of_machine_is_compatible("foo,bar"))
> >   platform_device_register_simple(...)
>
> I guess that's possible at the expense of losing the flexibility - my
> original idea was to allow a case where you could have two DRM devices,
> one per LCD controller if you wanted, rather than having a binding that
> forces one DRM device optionally containing both LCD controllers.

Sure, but that's an OS decision that has nothing to do with the
hardware and DT. You'll just have to pass some flag to the DRM device
platform driver and decide whether to create 1 device or 2. That
decision could be based on either evolving DRM architecture or on the
platform. That is more flexible than fixing it in DT.

Rob

Powered by blists - more mailing lists