Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp578741imm; Thu, 26 Jul 2018 08:28:32 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfkm7p4pKW/BBGIT8mlCheTE3iT24ADwyZQs7VdzBfqasJNc5jMFZQI37HTlIKqGNOlStqI X-Received: by 2002:a62:8b0f:: with SMTP id j15-v6mr2640587pfe.33.1532618911992; Thu, 26 Jul 2018 08:28:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532618911; cv=none; d=google.com; s=arc-20160816; b=bzlHKZYLSUqsYI097qnid62HSwlwgKtR+oCalWGIqU4fY4H4SWgfc3OuwlSiPINysl IRiNb4xrG5/E+Nw6xYamr53WfOoStHdI1piNvqHY8Q93UfJGrg6H6fohdhFEWxHtMrG7 YSdCB6WWG471anpIZCHp1ZtZfo5wAMnAMtqU0N9XAqh43Wn6aYTByusnMPV4W77+lfJN MTxtHTbH4wdZOC+EbARxzyvBQQUmggfiOjRE4w65a1A4lY2vbEHjvS2/w3xkuEYsH45Z uqKGz5qBvKQ6PPFEpk8vd0+ITMigWjzLI2WbxmXG9gYdjfHWa+VJ3Nww6RqmBWXVyAkZ TzzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:user-agent:message-id :references:cc:in-reply-to:from:to:content-transfer-encoding :mime-version:dkim-signature:arc-authentication-results; bh=Xz0Q0wbNL5lfbBU8DxQHewxAs5qAew1qZhdyxmg+pIs=; b=W+qLvn0Qsa3t6AHrlMNExUAD/cNBQR0s7UjPbJ97+9f9tx1g6k5tT/sSIelkGEqAow QhVVp12wWn62mC3O9fUY0XlXjav2beMM1v27+N2GSrexAgNrwnpTGUbjPxEPZUGd079Y EtOm1h25VVCEIaUr4hX19CUpkbQ11ctnZqGjs4K9lwfZUDXBw9euSWdxvnf0tVsWNyk0 BDjEcYtwAyO/c5lJvML1x4Yp49Kn+0w3ObO/mlSmc5QsJrB6GXETeNHDhRbKoLoS6jRY w8/JJEurArG46GJXrC8sd4x130I1SU85gyyRDBXCWk4dq1xTmyFtZnCEs05nFjPCnIxg EiZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vH1MNyE5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r17-v6si1517532pgd.682.2018.07.26.08.28.17; Thu, 26 Jul 2018 08:28:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vH1MNyE5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731758AbeGZQof (ORCPT + 99 others); Thu, 26 Jul 2018 12:44:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:36396 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730781AbeGZQof (ORCPT ); Thu, 26 Jul 2018 12:44:35 -0400 Received: from localhost (unknown [104.132.1.75]) (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 6350520846; Thu, 26 Jul 2018 15:27:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1532618833; bh=7R9YMxSO6WlB/iiFO1ePU+BXvzSZX/1EKmuWBtjw3YM=; h=To:From:In-Reply-To:Cc:References:Subject:Date:From; b=vH1MNyE5Ez443ivzZC8ot159G0fKWYv8f68XaSzbgYBk2Gjh2lJnY/fL7IqjConEr k2Q2N1gDyIdIax4DKqIIX30LkQHquloUEfYOErg35RbkQG9dXaanEaL5Y+m/DhO3/l iqhfSqNqgQgvCXTLoqjUv2nuXcaxCeD5EFwE+G9c= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable To: Rajan Vaja From: Stephen Boyd In-Reply-To: Cc: "linux-clk@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" References: <1531833420-27175-1-git-send-email-rajan.vaja@xilinx.com> <153253683456.48062.11538822357721957211@swboyd.mtv.corp.google.com> Message-ID: <153261883266.48062.5136812490732432669@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: RE: [PATCH] clk: clk-fixed-factor: Clear OF_POPULATED flag in case of failure Date: Thu, 26 Jul 2018 08:27:12 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Rajan Vaja (2018-07-26 06:03:16) > Hi Stephen, > = > > -----Original Message----- > > From: Stephen Boyd [mailto:sboyd@kernel.org] > > Sent: 25 July 2018 10:11 PM > > To: Rajan Vaja ; mturquette@baylibre.com > > Cc: linux-clk@vger.kernel.org; linux-kernel@vger.kernel.org; Rajan Vaja > > > > Subject: Re: [PATCH] clk: clk-fixed-factor: Clear OF_POPULATED flag in = case of > > failure > > = > > Quoting Rajan Vaja (2018-07-17 06:17:00) > > > Fixed factor clock has two initializations at of_clk_init() time > > > and during platform driver probe. Before of_clk_init() call, > > > node is marked as populated and so its probe never gets called. > > > > > > During of_clk_init() fixed factor clock registration may fail if > > > any of its parent clock is not registered. In this case, it doesn't > > > get chance to retry registration from probe. Clear OF_POPULATED > > > flag if fixed factor clock registration fails so that clock > > > registration is attempted again from probe. > > > > > > Signed-off-by: Rajan Vaja > > > --- > > > drivers/clk/clk-fixed-factor.c | 9 ++++++++- > > > 1 file changed, 8 insertions(+), 1 deletion(-) > > > > > > diff --git a/drivers/clk/clk-fixed-factor.c b/drivers/clk/clk-fixed-f= actor.c > > > index d72ef2d..f3ae4ff 100644 > > > --- a/drivers/clk/clk-fixed-factor.c > > > +++ b/drivers/clk/clk-fixed-factor.c > > > @@ -177,8 +177,15 @@ static struct clk *_of_fixed_factor_clk_setup(st= ruct > > device_node *node) > > > > > > clk =3D clk_register_fixed_factor(NULL, clk_name, parent_name= , flags, > > > mult, div); > > > - if (IS_ERR(clk)) > > > + if (IS_ERR(clk)) { > > > + /* > > > + * If parent clock is not registered, registration wo= uld fail. > > > + * Clear OF_POPULATED flag so that clock registration= can be > > > + * attempted again from probe function. > > > + */ > > > + of_node_clear_flag(node, OF_POPULATED); > > > return clk; > > > + } > > = > > BTW, this patch was seriously mangled for me so I had to apply it by > > hand. Please be more careful next time and consider using something like > > git-send-email and git-format-patch to send patches. > [Rajan] I used git-send-email only and sent same way as I used to send ot= her patches. Not sure where was issue. > Sorry for the inconvenience. = > = It must be your Outlook server messing things up. I see Content-Transfer-Encoding: quoted-printable in the headers, which probably caused my MUA to choke and line break things in the wrong place.