devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Eric Miao <eric.y.miao@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] Migrate PXA27x platforms to clock framework
Date: Mon, 28 Jul 2014 16:55:47 -0700	[thread overview]
Message-ID: <20140728235547.4906.20868@quantum> (raw)
In-Reply-To: <87k370o61q.fsf@free.fr>

Quoting Robert Jarzmik (2014-07-26 01:52:49)
> Mike Turquette <mturquette@linaro.org> writes:
> 
> > Quoting Robert Jarzmik (2014-07-21 11:23:51)
> >> Robert Jarzmik <robert.jarzmik@free.fr> writes:
> >> 
> >> > This is the second opus of this serie.
> >> 
> >> Ping ?
> >
> > Hi Robert,
> >
> > Overall the series looks good to me. The only problem I see is that
> > somewhere in the use of the PARENTS() macro there is a section mismatch
> > introduced. I spent about 5 minutes looking at it and gave up. This
> > problem introduces 26 section mismatch warnings building
> > colibri_pxa270_defconfig.
> OK Mike, I'll fix this. This is probably because pxa27x_clocks array is not
> __init, and it references parents which are __init. I was lazy letting
> pxa27x_clocks not __init because I reuse the internal fields "hw" and "gate->hw"
> later (hence I didn't leave the __init).
> This is a bit dirty and I'll launder it.
> 
> Moreover, I have one fix which I had fixed wrt boot ordering : the
> postcore_init() must die. The reason behind is that I have no guarantee of
> ordering between clocks init and clocksource init, and clocksource relies on
> clocks.
> 
> The right way will be AFAIK to call the core clocks init :
>  - within the device-tree initialization function : pxa27x_dt_clocks_init()
>  calls pxa27x_clocks_init9)
>  - directly from pxa27x_init() or pxa_timer_init() in non-device tree setup
> 
> > Once those are fixed up then I will be happy to take this series. Do you
> > want me to take all six patches through the clk tree, including the
> > arm/arm stuff?
> I would feel more comfortable if :
>  - you take the 4 first ones (3 clock ones + 1 arm pxa header bit definitions)
>  - Haojian takes the last 2 ones (pxa ones)
> 
> I will check that taking only the first 4 ones doesn't break anything, in case
> there is a merge window hipcup.

Sounds good.

Regards,
Mike

> 
> Cheers.
> 
> -- 
> Robert

  reply	other threads:[~2014-07-28 23:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 15:54 [PATCH v2 0/6] Migrate PXA27x platforms to clock framework Robert Jarzmik
     [not found] ` <1405353263-13424-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-07-14 15:54   ` [PATCH v2 1/6] clk: add pxa clocks infrastructure Robert Jarzmik
2014-07-14 15:54   ` [PATCH v2 2/6] clk: dts: document pxa clock binding Robert Jarzmik
2014-07-14 15:54   ` [PATCH v2 3/6] arm: pxa: add clock pll selection bits Robert Jarzmik
2014-07-14 15:54   ` [PATCH v2 4/6] clk: add pxa27x clock drivers Robert Jarzmik
2014-07-14 15:54   ` [PATCH v2 5/6] dts: add devicetree bindings for pxa27x clocks Robert Jarzmik
2014-07-14 15:54   ` [PATCH v2 6/6] arm: pxa: Transition pxa27x to clk framework Robert Jarzmik
     [not found]     ` <1405353263-13424-7-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2014-12-26  9:56       ` Laurent Pinchart
2014-12-26 16:58         ` Robert Jarzmik
2014-07-21 18:23   ` [PATCH v2 0/6] Migrate PXA27x platforms to clock framework Robert Jarzmik
2014-07-26  0:42     ` Mike Turquette
2014-07-26  8:52       ` Robert Jarzmik
2014-07-28 23:55         ` Mike Turquette [this message]
     [not found]         ` <87k370o61q.fsf-GANU6spQydw@public.gmane.org>
2014-07-29  1:25           ` Haojian Zhuang

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=20140728235547.4906.20868@quantum \
    --to=mturquette@linaro.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robert.jarzmik@free.fr \
    /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).