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 CA0DEC3565B for ; Fri, 21 Feb 2020 18:49:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A260424650 for ; Fri, 21 Feb 2020 18:49:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582310966; bh=Ls0R4Qe/IcctCXvAuXMBeYsY+8SGJkuitM+5W+PueKg=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=m2vGkE1nWYv9E0tM01dP/0T/SUsTdWsVvzvVbbrQSihmnWrQc/78jdNQLgN3fJLEc jX/GEk1dlStdEe1P1F7HnFHKOcTYQZX4cJKLN5c4lC9gLkELBqE47VmdkerKEJCBw9 EgUgqSI5tRvoXBWIS012yD0xafztifQ6fMAtcC2E= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729454AbgBUSt0 (ORCPT ); Fri, 21 Feb 2020 13:49:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:43184 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726150AbgBUSt0 (ORCPT ); Fri, 21 Feb 2020 13:49:26 -0500 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 80902208E4; Fri, 21 Feb 2020 18:49:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582310965; bh=Ls0R4Qe/IcctCXvAuXMBeYsY+8SGJkuitM+5W+PueKg=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=zG1EL/XfqmIsZXNzNzh/uxnJRX8DmMaUbAxsIUMpG6QXlGvZ/472Z//ta/RKq+PPE /+SBlCLPajAxdEoo5f1eSfdMrzrUI4vtiS279H3BQp6xZe5v362h7GLOF0/89QGCEE 4bHxYm4WQ4jA3ag5hfTk7dXJxr/tiYtom38sqncM= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20200221171030.39326-1-tony@atomide.com> References: <20200221171030.39326-1-tony@atomide.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: Fri, 21 Feb 2020 10:49:24 -0800 Message-ID: <158231096467.258574.11716255621346536160@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 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. >=20 > Fixes: 76a1049b84dd ("clk: ti: am43xx: add new clkctrl data for am43xx") > Signed-off-by: Tony Lindgren > --- >=20 > 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. 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?