linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 V3] clk: sirf: add CSR atlas7 clk and reset support
Date: Thu, 21 May 2015 14:33:24 -0700	[thread overview]
Message-ID: <20150521213324.GA1885@codeaurora.org> (raw)
In-Reply-To: <CAGsJ_4zwNQvvSwb49nwKzfke1V1nUCW-tDqbP4FxEr0SfmX9zA@mail.gmail.com>

On 05/16, Barry Song wrote:
> 2015-05-16 2:30 GMT+08:00 Stephen Boyd <sboyd@codeaurora.org>:
> > On 05/15, Barry Song wrote:
> >> From: Zhiwu Song <Zhiwu.Song@csr.com>
> >>
> >> the hardware node includes both clock and reset support, so it
> >> is named as "car".
> >> this patch implements Flexible clocks(mux, divider, gate), Selectable
> >> clock(mux, divider, gate), root clock(gate),leaf clock(gate), others.
> >> it also implements the reset controller functionality.
> >>
> >> Signed-off-by: Zhiwu Song <Zhiwu.Song@csr.com>
> >> Signed-off-by: Guo Zeng <Guo.Zeng@csr.com>
> >> Signed-off-by: Barry Song <Baohua.Song@csr.com>
> >> ---
> >

Yes this has already been applied, but replying to the last
comment.

> >> +
> >> +
> >> +CLK_OF_DECLARE(atlas7_clk, "sirf,atlas7-car", atlas7_clk_init);
> >>
> >
> > I'm also curious if we actually need to use CLK_OF_DECLARE here
> > or if could we use a platform device.
> >
> > Even if we need to use CLK_OF_DECLARE because some timer or other
> > early device needs a clock, I wonder if we shouldn't also make
> > these things into real platform drivers that register the other
> > clocks that aren't necessary for the early boot process.
> >
> it seems it is a general question not only for this driver?

Yes it is.

> 
> the main difficulty is maintaining the boot sequence of the platform
> devices and other machine codes which require clocks. it seems it is
> the easiest way to make clk ready earlier than other drivers.
> and i don't think registering these clocks takes much boot time and
> make boot slower at least for atlas7 platform since there is no sleep
> and long delay in the procedure.

It isn't really about making boot time faster, it's about using
the proper linux device model for clock providers. That way when
we want to support things like suspend/resume, deferred probe,
devm_*(), sysfs, etc. we can use the device model instead of
resorting to things like syscore_ops for suspend/resume or
forgoing features entirely.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-05-21 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  7:39 [PATCH 1/2 V3] clk: sirf: add CSR atlas7 clk and reset support Barry Song
2015-05-15  7:39 ` [PATCH 2/2 V3] ARM: dts: atlas7: add fixed frequency clocks in car node Barry Song
2015-05-15 17:00   ` Stephen Boyd
2015-05-15 18:30 ` [PATCH 1/2 V3] clk: sirf: add CSR atlas7 clk and reset support Stephen Boyd
2015-05-16 15:09   ` Barry Song
2015-05-21 21:33     ` Stephen Boyd [this message]
2015-06-10 16:30       ` Barry Song
2015-06-10 21:33         ` Stephen Boyd
2015-06-11 11:46           ` Barry Song

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=20150521213324.GA1885@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).