Devicetree
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Arun Kumar K <arun.kk@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	kgene.kim@samsung.com, dianders@chromium.org, olofj@google.com,
	t.figa@samsung.com, sachin.kamat@linaro.org,
	tushar.behera@linaro.org, arunkk.samsung@gmail.com
Subject: Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Date: Fri, 02 May 2014 20:52:26 +0200	[thread overview]
Message-ID: <4431329.kolHX05ZMV@wuerfel> (raw)
In-Reply-To: <1399035821-25096-2-git-send-email-arun.kk@samsung.com>

On Friday 02 May 2014 18:33:39 Arun Kumar K wrote:
> From: Alim Akhtar <alim.akhtar@samsung.com>
> 
> Exynos5800 clock structure is mostly similar to 5420 with only
> a small delta changes. So the 5420 clock file is re-used for
> 5800 also. The common clocks for both are seggreagated and few
> clocks which are different for both are separately initialized.
> 
> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
> Signed-off-by: Arun Kumar K <arun.kk@samsung.com>

This isn't about your specific patch, but every time I see a new
exynos variant get supported, it comes with a clock driver patch
that is at least as big as all the other patches combined.

New variants come out all the time now, and we are starting to
accumulate huge amounts of clock definitions both in the source
and the binary. I think we should try to come up with a better
way to represent the clocks. I don't think any other SoC
family is nearly as bad as Exynos, either because they have
much fewer models, or because they abstract their clocks more
and put all the tables into DT.

I'm definitely not saying no to the exynos5800 addition for this,
but I'm starting to get a little annoyed, and I think it would be
good to come up with a new clock binding before we see 64-bit
Exynos variants.

	Arnd

  parent reply	other threads:[~2014-05-02 18:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 13:03 [PATCH 0/3] Add Exynos5800 support Arun Kumar K
2014-05-02 13:03 ` [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks Arun Kumar K
2014-05-02 17:23   ` Tomasz Figa
2014-05-03 12:06     ` Arun Kumar K
2014-05-02 17:51   ` Andrew Bresticker
2014-05-03 12:12     ` Arun Kumar K
2014-05-02 18:52   ` Arnd Bergmann [this message]
2014-05-02 19:35     ` Doug Anderson
2014-05-03  2:12       ` Tomasz Figa
2014-05-02 13:03 ` [PATCH 2/3] ARM: dts: Add Exynos5800 dt file Arun Kumar K
2014-05-02 16:49   ` Olof Johansson
2014-05-02 17:03   ` Tomasz Figa
2014-05-02 13:03 ` [PATCH 3/3] ARM: dts: Add peach-pi board support Arun Kumar K
2014-05-02 17:10   ` Tomasz Figa
2014-05-02 18:31     ` Doug Anderson
2014-05-03  2:00       ` Tomasz Figa
     [not found]         ` <53644DDB.7050503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-05 15:17           ` Doug Anderson
2014-05-05 18:18             ` Tom Rini
2014-05-08 21:55               ` Bjorn Andersson
2014-05-08 22:16                 ` Tom Rini
2014-05-08 22:22                   ` Bjorn Andersson
2014-05-02 13:14 ` [PATCH 0/3] Add Exynos5800 support Kukjin Kim

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=4431329.kolHX05ZMV@wuerfel \
    --to=arnd@arndb.de \
    --cc=arun.kk@samsung.com \
    --cc=arunkk.samsung@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olofj@google.com \
    --cc=sachin.kamat@linaro.org \
    --cc=t.figa@samsung.com \
    --cc=tushar.behera@linaro.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