linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: David Lechner <david@lechnology.com>,
	<linux-arm-kernel@lists.infradead.org>
Cc: Kevin Hilman <khilman@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/5] ARM: davinci: convert to common clock framework
Date: Tue, 19 Dec 2017 19:17:13 +0530	[thread overview]
Message-ID: <b8025b62-c7c0-29f8-388d-d84816adf688@ti.com> (raw)
In-Reply-To: <1512785711-15064-5-git-send-email-david@lechnology.com>

Hi David,

On Saturday 09 December 2017 07:45 AM, David Lechner wrote:
> This converts the clocks in mach-davinci to the common clock framework.
> 
> Most of the patch just involves renaming struct clk to struct davinci_clk.
> There is also a struct clk_hw added to provide the bridge between the
> existing clock implementation and the common clock framework.
> 
> The clk_get_parent and clk_set_parent callbacks are dropped because all
> clocks currently (effectivly) have a single parent, in which case the
> common clock framework does not want you to implement these functions
> yourself.
> 
> clk_unregister() is dropped because it is not used anywhere in
> mach-davinci.
> 
> EXPORT_SYMBOL() is removed from functions not used outside of mach-davinci.
> 
> Fixed checkpatch.pl warning about bare use of unsigned in dump_clock().
> 
> Signed-off-by: David Lechner <david@lechnology.com>

The cleanups leading upto this patch look fine, but I am not sure about
this patch itself. Ideally, we should have moved to drivers/clk also.
And shared code with keystone too since the PSC and PLL implementations
of the two architectures are quite similar.

I could think of this as an intermediate step while we get there, but I
am afraid of the churn that would cause. For example, if we reuse
keystone driver, we will be using clk_psc and we can get rid of the
davinci_clk that this patch introduces.

So unless there is big roadblock to moving to drivers/clk, we should
probably do that in one shot.

Thanks,
Sekhar

  reply	other threads:[~2017-12-19 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09  2:15 [PATCH v3 0/5] ARM: davinci: convert to common clock framework David Lechner
2017-12-09  2:15 ` [PATCH v3 1/5] ARM: davinci: move davinci_clk_init() to init_time David Lechner
2017-12-09  2:15 ` [PATCH v3 2/5] ARM: davinci: don't use static clk_lookup David Lechner
2017-12-09  2:15 ` [PATCH v3 3/5] ARM: davinci: make davinci_clk_reset() static David Lechner
2017-12-09  2:15 ` [PATCH v3 4/5] ARM: davinci: convert to common clock framework David Lechner
2017-12-19 13:47   ` Sekhar Nori [this message]
2017-12-19 23:12     ` David Lechner
2017-12-21 12:34       ` Sekhar Nori
2017-12-21 16:52         ` David Lechner
2017-12-26 16:28           ` David Lechner
2017-12-09  2:15 ` [PATCH v3 5/5] ARM: davinci: remove clock debugfs David Lechner

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=b8025b62-c7c0-29f8-388d-d84816adf688@ti.com \
    --to=nsekhar@ti.com \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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).