From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752633AbcDZR1R (ORCPT <rfc822;w@1wt.eu>);
	Tue, 26 Apr 2016 13:27:17 -0400
Received: from muru.com ([72.249.23.125]:52170 "EHLO muru.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752074AbcDZR1P (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 26 Apr 2016 13:27:15 -0400
Date: Tue, 26 Apr 2016 10:27:11 -0700
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>, Tero Kristo <t-kristo@ti.com>
Cc: =?utf-8?Q?Beno=C3=AEt?= Cousson <bcousson@baylibre.com>,
        Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
        Mark Rutland <mark.rutland@arm.com>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Kumar Gala <galak@codeaurora.org>,
        Russell King <linux@arm.linux.org.uk>, ldewangan@nvidia.com,
        linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org, marek@goldelico.com,
        kernel@pyra-handheld.com, letux-kernel@openphoenux.org
Subject: Re: [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer
Message-ID: <20160426172710.GI5995@atomide.com>
References: <cover.1461003660.git.hns@goldelico.com>
 <a5fb89737594a656318896a8e43814c21ca992eb.1461003660.git.hns@goldelico.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a5fb89737594a656318896a8e43814c21ca992eb.1461003660.git.hns@goldelico.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Tero,

* H. Nikolaus Schaller <hns@goldelico.com> [160418 11:23]:
> OMAP5 has a register to control if the ckobuffer is enabled
> and defines the polarity. ckobuffer is required to drive a twl6040
> with the system clock. Hence, add the pinctrl,single to the
> OMAP5 SoC description so that omap5-board-common can
> set up the ckobuffer as required.

Is this really a mux or should it be a mux clock?

Regards,

Tony

> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
> ---
>  arch/arm/boot/dts/omap5.dtsi | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 120b6b8..1d9050f 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -277,6 +277,16 @@
>  				pinctrl-single,register-width = <16>;
>  				pinctrl-single,function-mask = <0x7fff>;
>  			};
> +
> +			omap5_control_ckobuffer: pinmux@cdb4 {
> +				compatible = "ti,omap5-padconf",
> +					     "pinctrl-single";
> +				reg = <0xcdb4 4>;
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +				pinctrl-single,register-width = <32>;
> +				pinctrl-single,function-mask = <0xf0000000>;
> +			};
>  		};
>  
>  		ocmcram: ocmcram@40300000 {
> -- 
> 2.7.3
>