From mboxrd@z Thu Jan 1 00:00:00 1970 From: sboyd@codeaurora.org (Stephen Boyd) Date: Thu, 15 Jun 2017 14:00:20 -0700 Subject: [PATCH 2/2 v4] clk: Add Gemini SoC clock controller In-Reply-To: References: <20170524082044.8473-1-linus.walleij@linaro.org> <20170601070208.GO20170@codeaurora.org> <20170605195812.GH20170@codeaurora.org> <20170612210248.GP20170@codeaurora.org> Message-ID: <20170615210020.GG20170@codeaurora.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 06/15, Linus Walleij wrote: > On Thu, Jun 15, 2017 at 10:55 AM, Geert Uytterhoeven > wrote: > > > If clocks and resets are provided by the same hardware module, you can > > have a single (platform) driver registering both the clock and reset > > controllers. > > Cfr. drivers/clk/renesas/renesas-cpg-mssr.c. > > That is indeed an option. > > So I would say, clk & reset maintainers: would you prefer that I merge the > reset control into the clock driver as well, ask Philipp to drop the pending > reset control patches from his subsystem tree and have you manage the > combined driver and bindings? > > It seems to me as very ugly from a divide & conquer subsystem and file > split point of view. > > I seems elegant from the "make clocks a platform device" point of view. > > I am happy with either approach as long as it works. > > I guess it is up to the taste of the subsystem maintainers, especially > clk. > > If I get some time I might just hack this up and send the patches so > it is on the table as an alternative to the current v5 patch. Certainly it is > better than going back and augmenting the DT bindings. > We have quite a few clock and reset controllers that put their drivers into the clk directory. I don't see any problem with that approach. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project