From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755442Ab3GAU4H (ORCPT ); Mon, 1 Jul 2013 16:56:07 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:48353 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755057Ab3GAU4F (ORCPT ); Mon, 1 Jul 2013 16:56:05 -0400 Message-ID: <1372712128.21065.71.camel@cumari.coelho.fi> Subject: Re: [RFC] wlcore: sdio: add wilink clock providers From: Luciano Coelho To: CC: , , , , , <--linux-doc@vger.kernel.org>, , , , Date: Mon, 1 Jul 2013 23:55:28 +0300 In-Reply-To: <20130701204633.GB805@arwen.pp.htv.fi> References: <1372707250-11998-1-git-send-email-coelho@ti.com> <20130701204633.GB805@arwen.pp.htv.fi> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2013-07-01 at 23:46 +0300, Felipe Balbi wrote: > Hi, > > On Mon, Jul 01, 2013 at 10:34:10PM +0300, Luciano Coelho wrote: > > diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi b/arch/arm/boot/dts/omap4-panda-common.dtsi > > index 670c3ce..7f061b8 100644 > > --- a/arch/arm/boot/dts/omap4-panda-common.dtsi > > +++ b/arch/arm/boot/dts/omap4-panda-common.dtsi > > @@ -65,11 +65,19 @@ > > enable-active-high; > > }; > > > > + > > wlan { > > - compatible = "ti,wilink6"; > > - interrupt-parent = <&gpio2>; > > - interrupts = <21 0x4>; /* gpio line 53, high level triggered */ > > - refclock = <2>; /* 38.4 MHz */ > > + compatible = "ti,wilink6"; > > + interrupt-parent = <&gpio2>; > > + interrupts = <21 0x4>; /* gpio line 53, high level triggered */ > > + clocks = <&refclock>; > > + clock-names = "refclock"; > > hmmm, shouldn't you provide both clocks (refclock and tcx0clock) > explicitly here ? No, not needed for Panda. Panda uses WiLink6 and only the refclock needs to be provided. > Also, you should probably make it clear that the WiLink module is fed by > the 32K sync clock just to make sure clock usecounts are correctly > incremented ? Hmmm, yes, that is probably a good idea. At least to make sure everything is initialized properly before the WiLink module is up and running. I'll look into it and eventually add in a separate patch. Thanks for your comments! -- Luca.