linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Fixes for 3.8-rc1
Date: Tue, 18 Dec 2012 23:13:56 +0100	[thread overview]
Message-ID: <1355868838-16124-1-git-send-email-andrew@lunn.ch> (raw)

These two patches are fixes needed for Linux 3.8.

The first patch fixes a lockup due to the missing SDIO clock. Since
the clkdev alias is missing, the sdio driver fails to
clk_prepare_enable() the clock. The lateinit call in the clk framework
then disables the clock since nobody owns it. The next access to the
SDIO register space causes the SoC to lockup.

The second patch fixes a null-pointer dereference. The conversion of
Kirkwood to pinctrl/gpio resulted in that using GPIO calls inside the
board-*.c file causes an exception, since the gpio driver has not yet
been loaded. Topkick is using the GPIO to control power to the SATA0
device. So convert the gpio to a fixed regulator, in DT, which gets
loaded after the gpio driver is available.

Andrew Lunn (2):
  ARM: Kirkwood: Fix missing sdio clock
  ARM: Kirkwood: Use fixed-regulator instead of board gpio call

 arch/arm/boot/dts/kirkwood-topkick.dts     |   17 +++++++++++++++++
 arch/arm/mach-kirkwood/board-dt.c          |    4 ++++
 arch/arm/mach-kirkwood/board-usi_topkick.c |    4 ----
 3 files changed, 21 insertions(+), 4 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2012-12-18 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 22:13 Andrew Lunn [this message]
2012-12-18 22:13 ` [PATCH 1/2] ARM: Kirkwood: Fix missing sdio clock Andrew Lunn
2012-12-18 22:13 ` [PATCH 2/2] ARM: Kirkwood: Use fixed-regulator instead of board gpio call Andrew Lunn
2012-12-27 22:57 ` [PATCH 0/2] Fixes for 3.8-rc1 Stefan Peter

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=1355868838-16124-1-git-send-email-andrew@lunn.ch \
    --to=andrew@lunn.ch \
    --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).