From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: Allwinner A64: Issue on external rtc clock to wifi chip Date: Mon, 14 May 2018 10:27:45 +0200 Message-ID: <20180514082744.ydmfg5mzsbol5onu@flea> References: <20180514075727.uxggyhmbahvhestx@flea> Reply-To: maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ko2m32o4savwftrl" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Jagan Teki Cc: Chen-Yu Tsai , Michael Trimarchi , linux-sunxi , linux-kernel , linux-arm-kernel , devicetree List-Id: devicetree@vger.kernel.org --ko2m32o4savwftrl Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Mon, May 14, 2018 at 01:34:56PM +0530, Jagan Teki wrote: > On Mon, May 14, 2018 at 1:27 PM, Maxime Ripard > wrote: > > Hi, > > > > On Mon, May 14, 2018 at 12:37:49PM +0530, Jagan Teki wrote: > >> Hi Maxime and All, > >> > >> We are trying to bring-up AP6330 Wifi chip for A64 board. We noticed > >> to have an external rtc clock has driven from wifi chip. > >> > >> So the devicetree is configured according to this as below. > >> > >> / { > >> wifi_pwrseq: wifi-pwrseq { > >> compatible = "mmc-pwrseq-simple"; > >> clocks = <&rtc 1>; > >> clock-names = "ext_clock"; > >> reset-gpios = <&r_pio 0 2 GPIO_ACTIVE_LOW>; /* PL2 */ > >> post-power-on-delay-ms = <400>; > >> }; > >> }; > >> > >> &rtc { > >> clock-output-names = "rtc-osc32k", "rtc-osc32k-out"; > >> clocks = <&osc32k>; > >> #clock-cells = <1>; > >> }; > >> > >> &mmc1 { > >> pinctrl-names = "default"; > >> pinctrl-0 = <&mmc1_pins>; > >> vmmc-supply = <®_dcdc1>; > >> vqmmc-supply = <®_eldo1>; > >> mmc-pwrseq = <&wifi_pwrseq>; > >> bus-width = <4>; > >> non-removable; > >> status = "okay"; > >> > >> brcmf: wifi@1 { > >> reg = <1>; > >> compatible = "brcm,bcm4329-fmac"; > >> interrupt-parent = <&r_pio>; > >> interrupts = <0 3 IRQ_TYPE_LEVEL_LOW>; /* WL-WAKE-AP: PL3 */ > >> interrupt-names = "host-wake"; > >> }; > >> }; > >> > >> And observed rtc-osc32k-out clock is never enabled[1] and the value of > >> LOSC_OUT_GATING is 0x0 which eventually not enabling > >> LOSC_OUT_GATING_EN > >> > >> Pls. let us know if we miss anything here? > >> > >> [1] https://paste.ubuntu.com/p/X2By4q8kD2/ > > > > Could you paste your config and the logs from a boot to? > > .config > https://paste.ubuntu.com/p/w9w2KB7RFc/ > > dmesg > https://paste.ubuntu.com/p/mrZGk5bWRR/ This is kind of weird. Have you tested with a 4.17 kernel? We have runtime_pm changes lined up in next, so that might be a regression there, even though we tested it with Quentin at some point. Maxime -- Maxime Ripard, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com --ko2m32o4savwftrl--