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 E8C60C2BB1D for ; Mon, 16 Mar 2020 18:28:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B8A4D20719 for ; Mon, 16 Mar 2020 18:28:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584383317; bh=mSIcRXbQR93F5mXG6L77T9yTvkpVt+N3gWe1Hs4i1r8=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=0z+Z9u2ZDNMBEZlCTO8qBaCKsLFeHXyKePjmVkeAOOy2E4c8m+A1L1l8lNLY1fMTu C5twYhQB06qQskf1CmC4Z69VFWCshwYzt4Y7EE/8DROrtQqNL7duIGClW58262y1WL gOa/rw+1Ul+/FXt7B3Pm+1NP7d68ar4r/JS513OU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732360AbgCPS2h (ORCPT ); Mon, 16 Mar 2020 14:28:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:58030 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732266AbgCPS2h (ORCPT ); Mon, 16 Mar 2020 14:28:37 -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 7DD3620409; Mon, 16 Mar 2020 18:28:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584383316; bh=mSIcRXbQR93F5mXG6L77T9yTvkpVt+N3gWe1Hs4i1r8=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=lMnXH/3ZzggPbtxMb+l9j6nT9+iwx7dhmcjP12rFmgnDWcku1D7JVym6u/ruk6J70 jwq1gEGmYXFAiPz4/ULUZQ0Kzc/KWpFzQbijdEHU8XgLV/+w/p2IIkan0TPhI8/Qvd tzi7CoO0JMQpkvDCy+AJUbuWnk532d8smDISP87g= 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:35 -0700 Message-ID: <158438331569.88485.562432552826260475@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-omap-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-omap@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 Woops, hit send too fast. Thanks! Picked it into clk-fixes.