public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu fixes for v3.8-rc6 (round 2)
Date: Tue, 5 Feb 2013 09:03:53 -0500	[thread overview]
Message-ID: <20130205140353.GT14746@titan.lakedaemon.net> (raw)
In-Reply-To: <1360013837.bfC5F0.15090@triton>

Olof, Arnd, Russell,

On Mon, Feb 04, 2013 at 09:37:17PM +0000, Jason Cooper wrote:
> The following changes since commit de27686b77f1c5c5dddf06d48fd322c52f098d51:
> 
>   arm: mvebu: i2c come back in defconfig
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/users/jcooper/linux.git tags/mvebu_fixes_for_v3.8-rc6-round2
> 
> for you to fetch changes up to b3fa2a0a2e3ac23415efec7ae848efd918b6b444:
> 
>   rtc: rtc-mv: Add support for clk to avoid lockups
> 
> ----------------------------------------------------------------
> mvebu fixes for v3.8-rc6 (round 2)
>     
>     This series of four patches started with Simon Baatz reporting lost MAC
>     addresses when compiling mv643xx_eth as a module.  Accompanying that, he was
>     getting hard lockups on boot when most other drivers were compiled as modules.
>     
>     All of this boiled down to gated clocks.  mv643xx_eth looses it's mac address
>     after it's clock gets gated.  The patch included in this series prevents the
>     ge0 and ge1 clocks from being gated when doing legacy platform init of the
>     driver.
>     
>     There is another patch to accompany the DT conversion of the driver which will
>     allow reading the mac address from the devicetree.  This patch is not included
>     here because the bindings are being added for v3.9.
>     
>     The hard lockups at boot were the result of many SoC IPs using the runit gate
>     clock.  Several drivers (gpio, rtc) were not claiming the clock, and of_serial
>     wouldn't claim the clock if clock-frequency was specified in the DT.
>     
>     clock-frequency was only necessary before we added proper clock support, it is
>     now removed from all kirkwood dts files.
>     
>     Last, proper clock support is added to gpio-mvebu and rtc-mv.
>     
>     With these four fixes all drivers that can be compiled as modules can be
>     without breaking bootup.
> ----------------------------------------------------------------

In light of Russell's recent comment (re i.MX fixes) on Linus' standard
for -rc7, I'd like to clarify the above.

While only one user reported the above problems (Simon Baatz), it was
caused by compiling v3.8-rc5 with the debian kernel config.  This config
builds almost everything it can as a module.

I'd like to do a v2 of this pull request since it was pointed out to me
this morning that I missed a clock-frequency in
kirkwood-ns2-common.dtsi.

Does the above meet the metric Linus has set for -rc7?  I think so, but
I leave that up to you guys.

If so, I'll redo these four patches to explicitly say they fix boot
problems caused when using debians default kernel config.

thx,

Jason.

> Andrew Lunn (2):
>       gpio: mvebu: Add clk support to prevent lockup
>       rtc: rtc-mv: Add support for clk to avoid lockups
> 
> Jason Cooper (1):
>       ARM: kirkwood: of_serial: fix clock gating by removing clock-frequency
> 
> Sebastian Hesselbarth (1):
>       ARM: kirkwood: fix to retain gbe MAC addresses for DT kernels
> 
>  arch/arm/boot/dts/kirkwood-dns320.dts         |  2 --
>  arch/arm/boot/dts/kirkwood-dns325.dts         |  1 -
>  arch/arm/boot/dts/kirkwood-dockstar.dts       |  1 -
>  arch/arm/boot/dts/kirkwood-dreamplug.dts      |  1 -
>  arch/arm/boot/dts/kirkwood-goflexnet.dts      |  1 -
>  arch/arm/boot/dts/kirkwood-ib62x0.dts         |  1 -
>  arch/arm/boot/dts/kirkwood-iconnect.dts       |  1 -
>  arch/arm/boot/dts/kirkwood-iomega_ix2_200.dts |  1 -
>  arch/arm/boot/dts/kirkwood-km_kirkwood.dts    |  1 -
>  arch/arm/boot/dts/kirkwood-lschlv2.dts        |  1 -
>  arch/arm/boot/dts/kirkwood-lsxhl.dts          |  1 -
>  arch/arm/boot/dts/kirkwood-mplcec4.dts        |  1 -
>  arch/arm/boot/dts/kirkwood-nsa310.dts         |  1 -
>  arch/arm/boot/dts/kirkwood-openblocks_a6.dts  |  2 --
>  arch/arm/boot/dts/kirkwood-topkick.dts        |  1 -
>  arch/arm/boot/dts/kirkwood.dtsi               |  5 ++--
>  arch/arm/mach-kirkwood/board-dt.c             | 24 ++++++++++++-------
>  drivers/gpio/gpio-mvebu.c                     |  7 ++++++
>  drivers/rtc/rtc-mv.c                          | 28 ++++++++++++++++++----
>  19 files changed, 49 insertions(+), 32 deletions(-)
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2013-02-05 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 21:37 [GIT PULL] ARM: mvebu fixes for v3.8-rc6 (round 2) Jason Cooper
2013-02-05 14:03 ` Jason Cooper [this message]
2013-02-05 18:57   ` Olof Johansson
2013-02-05 19:09     ` Arnd Bergmann
2013-02-10  0:33       ` Olof Johansson
2013-02-05 19:37     ` Jason Cooper

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=20130205140353.GT14746@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --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