From patchwork Thu Nov 13 13:20:26 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Kever Yang X-Patchwork-Id: 410411 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 7133D1400B6 for ; Fri, 14 Nov 2014 00:21:45 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933253AbaKMNVf (ORCPT ); Thu, 13 Nov 2014 08:21:35 -0500 Received: from mail-pd0-f173.google.com ([209.85.192.173]:33115 "EHLO mail-pd0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932637AbaKMNVd (ORCPT ); Thu, 13 Nov 2014 08:21:33 -0500 Received: by mail-pd0-f173.google.com with SMTP id v10so14497247pde.4 for ; Thu, 13 Nov 2014 05:21:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references; bh=0tM3cP+VoVadjHstgcTmwpBBTKtL2E3D4gOyh3aV4Dw=; b=S5jD/Fea+PHFkSVadOl9G8poCXwXb2RFGB4AdGxhdLboE+gqPguznUbqG91ju/Xo1V 0H5gJxB6p/wHJI2IzIXqBp6k65lf5cWK8qaolKXQhvXsZ5HTNIuWXCrCIDB6PrB3u9UK 9RMVAfv9BdnKUN0B6ekuRS3GZlNZc16ilh+ZsX37Fh7ugTF2Di6ImN3HeSjSpNFSYWk2 CgBX4zfpTZrWf6tW0aO9EFvS3V36tehQaNeb5WlBNbrcw5BVgV7/i8YWGtJwFGxzIMDg /tepFSPUWjK4ZSTAHpbawBIh/Da63j+aZ8JJmcBb4IEoN1mLcG4jTJ0XfdRH4SSoSFqB NtGw== X-Received: by 10.68.167.99 with SMTP id zn3mr2740049pbb.30.1415884893423; Thu, 13 Nov 2014 05:21:33 -0800 (PST) Received: from localhost.localdomain ([173.44.135.206]) by mx.google.com with ESMTPSA id r3sm24912122pds.57.2014.11.13.05.21.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 13 Nov 2014 05:21:32 -0800 (PST) From: Kever Yang To: Mike Turquette , Heiko Stuebner Cc: dianders@chromium.org, sonnyrao@chromium.org, addy.ke@rock-chips.com, cf@rock-chips.com, dkl@rock-chips.com, huangtao@rock-chips.com, linux-rockchip@lists.infradead.org, Kever Yang , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Simon Horman , Laurent Pinchart , Sylwester Nawrocki , Gerhard Sittig , Geert Uytterhoeven , Ben Dooks , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH 2/2] dt-bindings: clk: add document for assigned-clock-force-rates usage Date: Thu, 13 Nov 2014 21:20:26 +0800 Message-Id: <1415884826-7877-3-git-send-email-kever.yang@rock-chips.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1415884826-7877-1-git-send-email-kever.yang@rock-chips.com> References: <1415884826-7877-1-git-send-email-kever.yang@rock-chips.com> Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org This patch adds document for how to use the opetion property assigned-clock-force-rates. We may use this property to force update a clock setting. Signed-off-by: Kever Yang --- Documentation/devicetree/bindings/clock/clock-bindings.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clock/clock-bindings.txt b/Documentation/devicetree/bindings/clock/clock-bindings.txt index 06fc6d5..fb5d3a5 100644 --- a/Documentation/devicetree/bindings/clock/clock-bindings.txt +++ b/Documentation/devicetree/bindings/clock/clock-bindings.txt @@ -154,11 +154,14 @@ set to 0, or can be omitted if it is not followed by any non-zero entry. assigned-clocks = <&clkcon 0>, <&pll 2>; assigned-clock-parents = <&pll 2>; + assigned-clock-force-rates = <500000>, <0>; assigned-clock-rates = <0>, <460800>; }; -In this example the <&pll 2> clock is set as parent of clock <&clkcon 0> and -the <&pll 2> clock is assigned a frequency value of 460800 Hz. +In this example the <&pll 2> clock is set as parent of clock <&clkcon 0>, +the <&clkcon 0> clock is assigned a frequency value of 500000 Hz and make +sure the we get into assigned-clock-rates even if there is no rate change, +and the <&pll 2> clock is assigned a frequency value of 460800 Hz. Configuring a clock's parent and rate through the device node that consumes the clock can be done only for clocks that have a single user. Specifying