From patchwork Tue Nov 18 11:10:50 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Hans de Goede X-Patchwork-Id: 411974 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 090DB140174 for ; Tue, 18 Nov 2014 22:11:40 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753747AbaKRLLi (ORCPT ); Tue, 18 Nov 2014 06:11:38 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39841 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753683AbaKRLLg (ORCPT ); Tue, 18 Nov 2014 06:11:36 -0500 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAIBAvMD031596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 18 Nov 2014 06:10:58 -0500 Received: from shalem.localdomain.com (vpn1-7-183.ams2.redhat.com [10.36.7.183]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sAIBAqS5019988; Tue, 18 Nov 2014 06:10:55 -0500 From: Hans de Goede To: Tomi Valkeinen , Grant Likely , Ian Campbell Cc: Rob Herring , Maxime Ripard , David Herrmann , Geert Uytterhoeven , linux-fbdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree , linux-sunxi@googlegroups.com, Hans de Goede Subject: [PATCH v3 1/2] dt-bindings: simplefb: Drop the advice about using a specific path for nodes Date: Tue, 18 Nov 2014 12:10:50 +0100 Message-Id: <1416309051-26784-2-git-send-email-hdegoede@redhat.com> In-Reply-To: <1416309051-26784-1-git-send-email-hdegoede@redhat.com> References: <1416309051-26784-1-git-send-email-hdegoede@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org This goes contrary to how devicetree usually works, so drop it. Instead if the firmware needs to be able to find a specific node it should use a platform specific compatible + properties for this. Signed-off-by: Hans de Goede Acked-by: Grant Likely --- Documentation/devicetree/bindings/video/simple-framebuffer.txt | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/video/simple-framebuffer.txt b/Documentation/devicetree/bindings/video/simple-framebuffer.txt index f8fb7e6..4474ef6 100644 --- a/Documentation/devicetree/bindings/video/simple-framebuffer.txt +++ b/Documentation/devicetree/bindings/video/simple-framebuffer.txt @@ -31,12 +31,10 @@ enable them. This way if e.g. later on support for more display clocks get added, the simplefb nodes will already contain this info and the firmware does not need to be updated. -If pre-filled framebuffer nodes are used, they should be named -"framebuffer#-", e.g. "framebuffer0-hdmi". The output should be -included in the name since different outputs typically require different -clocks and the clocks are part of the pre-populated nodes. The firmware must -rename the nodes to the standard "framebuffer@
" name using the -runtime chosen address when enabling the nodes. +If pre-filled framebuffer nodes are used, the firmware may need extra +information to find the right node. In that case an extra platform specific +compatible and platform specific properties should be used and documented, +see e.g. simple-framebuffer-sunxi.txt . Required properties: - compatible: "simple-framebuffer"