From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Add Mediatek MT8173 subsystem clocks support
Date: Thu, 11 Jun 2015 16:52:12 -0700 [thread overview]
Message-ID: <20150611235212.GI29640@codeaurora.org> (raw)
In-Reply-To: <20150608074858.GK6325@pengutronix.de>
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.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-06-11 23:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 7:12 [PATCH 0/5] Add Mediatek MT8173 subsystem clocks support James Liao
2015-05-21 7:12 ` [PATCH 1/5] clk: mediatek: Fix apmixedsys clock registration James Liao
2015-05-26 7:42 ` Sascha Hauer
2015-06-04 21:07 ` Stephen Boyd
2015-05-21 7:12 ` [PATCH 2/5] clk: mediatek: mt8173: Fix enabling of critical clocks James Liao
2015-05-26 7:46 ` Sascha Hauer
2015-05-26 8:36 ` James Liao
2015-05-21 7:12 ` [PATCH 3/5] dt-bindings: ARM: Mediatek: Document devicetree bindings for clock controllers James Liao
2015-05-26 7:56 ` Sascha Hauer
2015-05-26 8:55 ` James Liao
2015-05-26 11:08 ` Sascha Hauer
2015-05-27 6:12 ` Yong Wu
2015-05-27 7:27 ` Sascha Hauer
2015-05-28 5:14 ` Yong Wu
2015-05-21 7:12 ` [PATCH 4/5] clk: mediatek: Add subsystem clocks of MT8173 James Liao
2015-05-22 4:22 ` Daniel Kurtz
2015-05-22 6:03 ` James Liao
2015-06-12 17:09 ` Matthias Brugger
2015-06-15 2:10 ` James Liao
2015-05-21 7:12 ` [PATCH 5/5] clk: mediatek: Add USB clock support in MT8173 APMIXEDSYS James Liao
2015-05-26 8:05 ` Sascha Hauer
2015-05-26 9:11 ` James Liao
2015-05-26 9:41 ` Sascha Hauer
2015-05-26 9:58 ` James Liao
2015-05-28 13:24 ` [PATCH 0/5] Add Mediatek MT8173 subsystem clocks support Sascha Hauer
2015-05-29 2:47 ` James Liao
2015-05-29 6:23 ` Sascha Hauer
2015-06-04 21:02 ` Stephen Boyd
2015-06-05 1:45 ` James Liao
2015-06-06 0:59 ` Stephen Boyd
2015-06-08 7:27 ` James Liao
2015-06-08 7:48 ` Sascha Hauer
2015-06-11 23:52 ` Stephen Boyd [this message]
2015-06-12 17:05 ` Matthias Brugger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150611235212.GI29640@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).