From patchwork Sun Aug 13 14:18:53 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Shawn Guo X-Patchwork-Id: 9897865 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 3DBD8602CA for ; Sun, 13 Aug 2017 14:20:28 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 413072097A for ; Sun, 13 Aug 2017 14:20:28 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 35737283ED; Sun, 13 Aug 2017 14:20:28 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=2.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C8D442097A for ; Sun, 13 Aug 2017 14:20:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750974AbdHMOU1 (ORCPT ); Sun, 13 Aug 2017 10:20:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:36148 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750907AbdHMOU0 (ORCPT ); Sun, 13 Aug 2017 10:20:26 -0400 Received: from dragon (li411-102.members.linode.com [106.187.91.102]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 27CC323966; Sun, 13 Aug 2017 14:20:23 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 27CC323966 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=shawnguo@kernel.org Date: Sun, 13 Aug 2017 22:18:53 +0800 From: Shawn Guo To: Stephen Boyd Cc: Michael Turquette , Dong Aisheng , linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Shawn Guo Subject: Re: [PATCH] clk: bulk: call of_clk_get() when id is NULL Message-ID: <20170813141851.GD31819@dragon> References: <1502243442-28055-1-git-send-email-shawnguo@kernel.org> <20170809173318.GD2146@codeaurora.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20170809173318.GD2146@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Hi Stephen, On Wed, Aug 09, 2017 at 10:33:18AM -0700, Stephen Boyd wrote: > > diff --git a/drivers/clk/clk-bulk.c b/drivers/clk/clk-bulk.c > > index c834f5abfc49..65cee595a67e 100644 > > --- a/drivers/clk/clk-bulk.c > > +++ b/drivers/clk/clk-bulk.c > > @@ -39,7 +39,10 @@ int __must_check clk_bulk_get(struct device *dev, int num_clks, > > clks[i].clk = NULL; > > > > for (i = 0; i < num_clks; i++) { > > - clks[i].clk = clk_get(dev, clks[i].id); > > + if (clks[i].id) > > + clks[i].clk = clk_get(dev, clks[i].id); > > + else if (dev->of_node) > > + clks[i].clk = of_clk_get(dev->of_node, i); > > This seems a little too magical. The omission of an id in an > array of clks would mean that only that one clk is acquired > through of_clk_get(). We could have a mixture of ids and no ids > for some device, and then do very odd things. > > How about we add a flag to clk_bulk_data that indicates we want > it to use of_clk_get() instead of clk_get() for all of the clks? > Then the id is ignored for the entire function. I have sent v2 to add a flag to clk_bulk_data to address your comments. But I just found it might not be what you want exactly, because the current bulk clk APIs defines clk_bulk_data in a different way from what you are asking here. It seems that you think clk_bulk_data represents all the clocks that bulk APIs manage, but actually it only represents one of the multiple clocks. Callers need to prepare an array of clk_bulk_data to represent multiple clocks. That said, the flag we add to clk_bulk_data only affects one clock instead of all clocks. I feel this is something we can improve. clk_bulk_data can be used to represent all clocks, something like below. In this case, bulk clk APIs do not need to take num_clks as a separate parameter, and callers do not need to maintain multiple clk_bulk_data instances. Since we do not have any in tree users of bulk clk APIs yet, we can make this semantic change quickly. Thoughts? the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/include/linux/clk.h b/include/linux/clk.h index 31fee2e8d4a2..ddc4812758f6 100644 --- a/include/linux/clk.h +++ b/include/linux/clk.h @@ -80,8 +80,10 @@ struct clk_notifier_data { /** * struct clk_bulk_data - Data used for bulk clk operations. * - * @id: clock consumer ID - * @clk: struct clk * to store the associated clock + * @ids: array of clock consumer IDs which should be provided by caller. + * @clks: array of struct clk * to store the associated clocks, which will be + * allocated by clk_bulk_get() and freed by clk_bulk_put(). + * @num_clks: number of clocks that caller wants bulk API to manage. * @flags: bulk clk operation flags * * The CLK APIs provide a series of clk_bulk_() API calls as @@ -93,8 +95,9 @@ struct clk_notifier_data { * clk_bulk_get() API will call of_clk_get() to find clock by index. */ struct clk_bulk_data { - const char *id; - struct clk *clk; + const char **ids; + struct clk **clks; + unsigned int num_clks; unsigned long flags; }; -- To unsubscribe from this list: send the line "unsubscribe linux-clk" in