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 v2 0/4] ARM: imx31: clock initialization fixes
Date: Tue, 25 Oct 2016 13:37:41 -0700	[thread overview]
Message-ID: <20161025203741.GD26139@codeaurora.org> (raw)
In-Reply-To: <20161023122844.GR30578@tiger>

On 10/23, Shawn Guo wrote:
> On Mon, Sep 26, 2016 at 03:03:39AM +0300, Vladimir Zapolskiy wrote:
> > The change is tested on qemu kzm target and mx31lite board, while both
> > targets don't have DTS in upstream, I had to write simple DTS files for
> > them, because the proposed change is for i.MX31 targets with OF support.
> > 
> > i.MX31/OF/clock initialization seems to be broken currently, if
> > the series is not applied I can not get a working clock source during
> > early boot stage on a board with DTB supplied.
> > 
> > Changes from v1 to v2, thanks to Uwe and Stephen for review:
> > * added one more new fix in imx31.dtsi which moves CCM device node
> >   to AIPS2 bus,
> > * included to the series a fix of CCM interrupts in imx31.dtsi,
> >   the change was sent as a separate patch, the change is included
> >   to avoid a patch application dependency,
> > * as suggested by Uwe reworded one of the commits removing "stack
> >   corruption" mentioning, the overwritten value is passed in a register,
> > * as suggested by Uwe squashed clk-imx31.c and imx31-dt.c changes
> >   to avoid a runtime problem if only one of two patches are applied
> > 
> > Vladimir Zapolskiy (4):
> >   ARM: dts: imx31: fix clock control module interrupts description
> >   ARM: dts: imx31: move CCM device node to AIPS2 bus devices
> >   clk: imx31: fix rewritten input argument of mx31_clocks_init()
> >   ARM: clk: imx31: properly init clocks for machines with DT
> > 
> >  .../devicetree/bindings/clock/imx31-clock.txt      |  2 +-
> >  arch/arm/boot/dts/imx31.dtsi                       | 14 +++---
> >  arch/arm/mach-imx/common.h                         |  1 -
> >  arch/arm/mach-imx/imx31-dt.c                       |  6 ---
> >  drivers/clk/imx/clk-imx31.c                        | 52 +++++++++++-----------
> 
> Hi Stephen,
> 
> Can I have you ACK on the clk file, so that we can merge the series from
> arm-soc tree?  Thanks.
> 

Done.

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

  reply	other threads:[~2016-10-25 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  0:03 [PATCH v2 0/4] ARM: imx31: clock initialization fixes Vladimir Zapolskiy
2016-09-26  0:03 ` [PATCH v2 1/4] ARM: dts: imx31: fix clock control module interrupts description Vladimir Zapolskiy
2016-09-26  0:03 ` [PATCH v2 2/4] ARM: dts: imx31: move CCM device node to AIPS2 bus devices Vladimir Zapolskiy
2016-09-26  6:36   ` Uwe Kleine-König
2016-09-26  0:03 ` [PATCH v2 3/4] clk: imx31: fix rewritten input argument of mx31_clocks_init() Vladimir Zapolskiy
2016-09-26  6:23   ` Uwe Kleine-König
2016-10-25 20:36   ` Stephen Boyd
2016-09-26  0:03 ` [PATCH v2 4/4] ARM: clk: imx31: properly init clocks for machines with DT Vladimir Zapolskiy
2016-10-25 20:37   ` Stephen Boyd
2016-10-23 12:28 ` [PATCH v2 0/4] ARM: imx31: clock initialization fixes Shawn Guo
2016-10-25 20:37   ` Stephen Boyd [this message]
2016-11-01  8:50 ` Shawn Guo

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=20161025203741.GD26139@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).