Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755820AbbFLRFp (ORCPT ); Fri, 12 Jun 2015 13:05:45 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:33301 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754098AbbFLRFm (ORCPT ); Fri, 12 Jun 2015 13:05:42 -0400 From: Matthias Brugger To: Stephen Boyd Cc: Sascha Hauer , James Liao , Mike Turquette , srv_heupstream@mediatek.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Henry Chen , Ricky Liang , Rob Herring , linux-mediatek@lists.infradead.org, Sascha Hauer , Yingjoe Chen , Eddie Huang , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/5] Add Mediatek MT8173 subsystem clocks support Date: Fri, 12 Jun 2015 19:05:34 +0200 Message-ID: <31179881.mpd5ayrmF7@ubix> User-Agent: KMail/4.13.3 (Linux/3.13.0-54-generic; KDE/4.13.3; x86_64; ; ) In-Reply-To: <20150611235212.GI29640@codeaurora.org> References: <1432192376-6712-1-git-send-email-jamesjj.liao@mediatek.com> <20150608074858.GK6325@pengutronix.de> <20150611235212.GI29640@codeaurora.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1630 Lines: 33 On Thursday, June 11, 2015 04:52:12 PM Stephen Boyd wrote: > On 06/08, Sascha Hauer wrote: > > On Fri, Jun 05, 2015 at 05:59:12PM -0700, Stephen Boyd wrote: > > > And similar things could be done for the reset driver. > > > > The problem I see with this approach is that we scatter the code for a > > otherwise simple driver over a bunch of directories. We would have > > > > drivers/clk/mediatek/vencsys.c > > drivers/reset/mediatek/vencsys.c > > drivers/soc/mediatek/vencsys.c > > > > The same must be added for vdecsys, imgsys and vencltsys. That will make > > 12 drivers and three maintainers for 12 registers. I think this will be > > a pain to maintain, hence my suggestion to put the vencsys code into a > > single file and not split this up into more subsystem specific files. > > I probably don't have enough information here, but why is it a > pain to maintain? It seems more like a pain to setup the first > time and then little to no pain to maintain because we clearly > split functionality based on subsystem. No merge conflicts, clear > division of functionality, etc. But again, I don't think it > matters much either way given that reset and clk drivers are > combined sometimes and don't always reside in drivers/clk or > drivers/reset either. Actually I would prefer to have the clock and resets in drivers/clk, just as we already did for Mediatek up to now. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/