Received: by 2002:ac0:b08d:0:0:0:0:0 with SMTP id l13csp3590237imc; Sun, 24 Feb 2019 08:16:14 -0800 (PST) X-Google-Smtp-Source: AHgI3IbBgawhxPoH6K2yWdyB9o+tOpOApRWfzl7T1ZB7e17KlKnPUKjkna4pqOUBOblWzs4gkcJ8 X-Received: by 2002:a63:d205:: with SMTP id a5mr5722794pgg.142.1551024974543; Sun, 24 Feb 2019 08:16:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551024974; cv=none; d=google.com; s=arc-20160816; b=jMw8ZABo3BaxB2R/CSehId1jTaaaVtRW40UEu5iTrWCmXiZ80s3T5tRBhV+knWoADv MXH/NmNLnd2iH1RYzXitaZnklOsHBlAigIfnuTZE4iUqq1G3RwnJHAXKwHur7+aZlc2p Wrxy9+D8hr5HwkYsHRfpKR1zKUGUN8uhOquEQHX9rI6QrkUbgLa1MJHiHWFt2mSsa3op gy367jGQAUxPx27uxRUWR5PivXqlocNC1aVwXtGy1NlJwBZhaUKo8oyWpNvIa0qQbHFe J1jsWn7D6hIWlILsd4Dy8jftIfuFayfMnUzHdclDomS0FKxvtuGapzK36lHdm79zRC9O oRQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=EhHnCNNhWTyWqY77h66VQtqulq9XIZATSTUu/0Ykxig=; b=0dvVMgO515Eeoe17qCKDfKeR3BGyeUxHLB9TU5RsjlJ+0WQFMwIk47Joy2eQfKe36l /j2diSb5Et7+0bZwyrRdLPjjyCfFESIt7/UtAIRFmPIFf3StUE1NFHWGKOXTGnd07cnT qh8eGgmZfJG3TAsOlKkT1/P1qYII5t6w6xPccQAPCwTGeFDQpxgUtVierCKPBWvfrLn/ D+USnR5HHbjuX/yxzFxI/nbOTVIULvhPkXprzNp2iycxe5d+M/IqoL8D556YPaQgvLN8 KMbSxGokLpLNrBiQS/fx9j9uW36HRWnjcigHLKDia8pN0C5Tc0brYD+EB4IzObGvj+XE M55A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64si5957928pft.29.2019.02.24.08.15.59; Sun, 24 Feb 2019 08:16:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728434AbfBXQPj (ORCPT + 99 others); Sun, 24 Feb 2019 11:15:39 -0500 Received: from shell.v3.sk ([90.176.6.54]:50752 "EHLO shell.v3.sk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725860AbfBXQPj (ORCPT ); Sun, 24 Feb 2019 11:15:39 -0500 Received: from localhost (localhost [127.0.0.1]) by zimbra.v3.sk (Postfix) with ESMTP id BC08A100588; Sun, 24 Feb 2019 17:15:35 +0100 (CET) Received: from shell.v3.sk ([127.0.0.1]) by localhost (zimbra.v3.sk [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id bzMlmubDcem7; Sun, 24 Feb 2019 17:15:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zimbra.v3.sk (Postfix) with ESMTP id 760DF1021C6; Sun, 24 Feb 2019 17:15:32 +0100 (CET) X-Virus-Scanned: amavisd-new at zimbra.v3.sk Received: from shell.v3.sk ([127.0.0.1]) by localhost (zimbra.v3.sk [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yP3elijAZ64b; Sun, 24 Feb 2019 17:15:31 +0100 (CET) Received: from nedofet.lan (ip-89-102-31-34.net.upcbroadband.cz [89.102.31.34]) by zimbra.v3.sk (Postfix) with ESMTPSA id 6A1E1100588; Sun, 24 Feb 2019 17:15:31 +0100 (CET) Message-ID: <4e89406842c4821d590dc6518076cfe6f19cc6b9.camel@v3.sk> Subject: Re: [PATCH 4/6] dt-bindings: display: armada: Add display subsystem binding From: Lubomir Rintel To: Rob Herring Cc: Mark Rutland , Russell King , dri-devel , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" Date: Sun, 24 Feb 2019 17:15:30 +0100 In-Reply-To: References: <20190120172534.24617-1-lkundrak@v3.sk> <20190120172534.24617-5-lkundrak@v3.sk> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-02-22 at 14:23 -0600, Rob Herring wrote: > On Wed, Feb 13, 2019 at 4:37 PM Lubomir Rintel wrote: > > On Mon, 2019-01-21 at 09:35 -0600, Rob Herring wrote: > > > On Sun, Jan 20, 2019 at 11:26 AM Lubomir Rintel 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 > > > > --- > > > > .../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. > > > > Before I follow up on this and submit a version without the virtual > > node, I'm wondering: is it okay that the bindings for the LCDC and the > > framebuffer are in the same file, or would it be preferrable if they > > were separate? Both styles seem to be used for the display bindings. > > framebuffer as in the kernel fbdev? Really, that should be the same > binding. It's the same h/w after all. However, there have been cases > where things deviated. So I don't have a good answer. No, not the fbdev device, that one is managed by drmfb and is not expressed in DT. I meant the reserved-memory node that sets aside memory for the framebuffers. See patch "[RFC 03/16] dt-bindings: display: armada: Add framebuffer reserved-mem binding". Perhaps that part should even go to Documentation/devicetree/bindings/reserved-memory/. Lubo