From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4168AC2BB1D for ; Mon, 16 Mar 2020 18:28:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1026D2071C for ; Mon, 16 Mar 2020 18:28:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584383295; bh=3ny6nLBhWMN7Tnbc3yjHh9vkkA88GrNLNX04LRSKado=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=n3UeQRetubMBRuw7ewz//VONxlg1mwNBlMvzTCKbpZoNsaJkHhRyMTqD67F4tFFQC eFpoCSlgaj4rAum9Svs6c8UH5NOpWoSLO/ffFJBniwNoECek2ySgAZgQ536sFrXmm6 H2/ssG2Sr0+S/MzAEM+xByliJ31Yejx38a81D6vs= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732346AbgCPS2O (ORCPT ); Mon, 16 Mar 2020 14:28:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:57654 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732313AbgCPS2O (ORCPT ); Mon, 16 Mar 2020 14:28:14 -0400 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 726BA20409; Mon, 16 Mar 2020 18:28:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584383293; bh=3ny6nLBhWMN7Tnbc3yjHh9vkkA88GrNLNX04LRSKado=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=uLett0y7mrWX7f1IWoybiokeUIYQBKweyEDDsE5m1xWD328QgX0wzEK9bjq18vVTV P1uzQXLRpz9ZWJ7zIro+ccO+YdKzQmbnLh43iC6/bmSs1eNtq+HDJ1pk7XDXmm8ord K+LKAPT7w/nrweTI/VccgeJ4kIiqdeek0hO6ULcA= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <831d632e-78da-07c4-f8c7-14d17ba1ef28@ti.com> References: <20200221171030.39326-1-tony@atomide.com> <158231096467.258574.11716255621346536160@swboyd.mtv.corp.google.com> <831d632e-78da-07c4-f8c7-14d17ba1ef28@ti.com> Subject: Re: [PATCH] clk: ti: am43xx: Fix clock parent for RTC clock From: Stephen Boyd Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-omap@vger.kernel.org To: Michael Turquette , Stephen Boyd , Tero Kristo , Tony Lindgren Date: Mon, 16 Mar 2020 11:28:12 -0700 Message-ID: <158438329273.88485.9465537092249993831@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Tero Kristo (2020-03-16 07:48:30) > On 21/02/2020 20:49, Stephen Boyd wrote: > > Quoting Tony Lindgren (2020-02-21 09:10:30) > >> Currently enabling clkctrl clock on am4 can fail for RTC as the clock > >> parent is wrong for RTC. > >> > >> Fixes: 76a1049b84dd ("clk: ti: am43xx: add new clkctrl data for am43xx= ") > >> Signed-off-by: Tony Lindgren > >> --- > >> > >> It is unclear if we can end up with RTC hung with the current mainline > >> kernel in some cases. Probing RTC with device tree data only seems to > >> trigger this every time. > >=20 > > It's small enough and if it's annoying enough we can probably put it > > into clk-fixes to get it fixed for this release instead of waiting. Can > > Tero ack it? > >=20 >=20 > Sure, >=20 > Acked-by: Tero Kristo > -- > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/= Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki