From patchwork Mon Dec 2 15:52:59 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerhard Sittig X-Patchwork-Id: 295950 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 A55DF2C009F for ; Tue, 3 Dec 2013 02:53:14 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752087Ab3LBPxN (ORCPT ); Mon, 2 Dec 2013 10:53:13 -0500 Received: from mail-out.m-online.net ([212.18.0.9]:38187 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751781Ab3LBPxN (ORCPT ); Mon, 2 Dec 2013 10:53:13 -0500 Received: from frontend1.mail.m-online.net (unknown [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id 3dY9pH4CKmz4KK5w; Mon, 2 Dec 2013 16:53:11 +0100 (CET) Received: from localhost (dynscan1.mnet-online.de [192.168.6.68]) by mail.m-online.net (Postfix) with ESMTP id 3dY9pH3ppMzbbgF; Mon, 2 Dec 2013 16:53:11 +0100 (CET) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.180]) by localhost (dynscan1.mail.m-online.net [192.168.6.68]) (amavisd-new, port 10024) with ESMTP id ydoBH712jei3; Mon, 2 Dec 2013 16:53:08 +0100 (CET) X-Auth-Info: +SGhESrll6KotYca/CZ9aKzl6q+GxDJEGd+Zu/xjSnk= Received: from localhost (kons-4d03d241.pool.mediaWays.net [77.3.210.65]) by mail.mnet-online.de (Postfix) with ESMTPA; Mon, 2 Dec 2013 16:53:08 +0100 (CET) From: Gerhard Sittig To: devicetree@vger.kernel.org Cc: Gerhard Sittig , Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell Subject: [PATCH v1 1/1] dts: bindings: trivial clock bindings doc fixes Date: Mon, 2 Dec 2013 16:52:59 +0100 Message-Id: <1385999579-3184-1-git-send-email-gsi@denx.de> X-Mailer: git-send-email 1.7.10.4 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org fix a typo in the "clock specifiers" discussion, clarify that clock specifiers (the integer cells part that goes with the phandle) may be empty Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Stephen Warren Cc: Ian Campbell Cc: devicetree@vger.kernel.org Signed-off-by: Gerhard Sittig Acked-by: Mark Rutland --- this may sound like nit picking, but from an earlier explanation by Mark Rutland I learned that a reference always consists of a phandle and a specifier, that the specifier is the sequence of integer cells that accompany the phandle, and that the phandle "by intuition might be expected to" be part of the specifier but specificly is not (and shall not, to keep the existing documentation consistent) since I was fixing the typo, and had the above information, I could not resist but had to add the "may be zero cells" detail in bypassing found no other issue in this file -- don't worry, won't emit an endless stream of tiny trivial changes, this one is all there is :) Documentation/devicetree/bindings/clock/clock-bindings.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/clock/clock-bindings.txt b/Documentation/devicetree/bindings/clock/clock-bindings.txt index eb65d417f8c4..7c52c29d99fa 100644 --- a/Documentation/devicetree/bindings/clock/clock-bindings.txt +++ b/Documentation/devicetree/bindings/clock/clock-bindings.txt @@ -5,7 +5,7 @@ Sources of clock signal can be represented by any node in the device tree. Those nodes are designated as clock providers. Clock consumer nodes use a phandle and clock specifier pair to connect clock provider outputs to clock inputs. Similar to the gpio specifiers, a clock -specifier is an array of one more more cells identifying the clock +specifier is an array of zero, one or more cells identifying the clock output on a device. The length of a clock specifier is defined by the value of a #clock-cells property in the clock provider node.