All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM:MXS: Initial support for the Crystalfontz CFA-10036
Date: Thu, 21 Jun 2012 10:46:52 +0200	[thread overview]
Message-ID: <1340268415-5022-1-git-send-email-maxime.ripard@free-electrons.com> (raw)

Hi everyone,

This is an attempt for a initial support for the Crystalfontz CFA
10036 module.

The module basically has a iMX28 SoC, plus a micro-SD slot, 3 pins to
access the DUART, a USB OTG port, a OLED screen using the Solomon
SSD1307 controller over I2C and a 200-pins SODIMM port to plug an
expansion board.

Support for this board and the additional devices will come
eventually.

For now, only the DUART and the MMC controller are used.

On the MMC part though, Something odd is going on.  On the first
patches I made against 3.4, everything was working fine. With 3.5-rc2
though, the MMC never replies to the first CMD52 command sent to
it. The pin muxing hasn't changed and has been checked, the card is
well detected through the card detect pin, the power enable pin is
correctly set to a low level, and so the SD card is correctly
powered. The MMC works fine with the exact same kernel on the
imx28-evk though.

What seems odd to me, is that when booting the board with the 3.4
kernel, at boot, the mxs-mmc driver reports a SSP clock of 288MHz,
while on 3.5, it reports a 480MHz SSP clock. By looking at the clk
driver for the iMX28, there is a comment saying that the 480MHz clock
seems to high for SD controlers, and that it should be 288MHz
instead. Given that the clock part has changed quite a lot from 3.4 to
3.5, I think it might be a good lead, but hardcoding the SSP clock to
288MHz in the mxs-mmc driver instead of using the clk_get_rate
function does not resolve the problem.

Also, this problem is seen with both DT-probing and traditionnal
probing.

Do someone have an idea on what could possibly happen here ?

Thanks,
Maxime

             reply	other threads:[~2012-06-21  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  8:46 Maxime Ripard [this message]
2012-06-21  8:46 ` [PATCH 1/2] Early support for the Crystalfontz CFA10036 module Maxime Ripard
2012-06-21  9:47   ` Marek Vasut
2012-06-21  8:46 ` [PATCH 2/2] ARM: MXS: Add Crystalfontz CFA-10036 DTS Maxime Ripard
2012-06-21  9:49   ` Marek Vasut
2012-06-21 10:12     ` Maxime Ripard
2012-06-21 11:01       ` Marek Vasut
2012-06-21 13:29   ` Shawn Guo
2012-06-21 13:11 ` [PATCH] ARM:MXS: Initial support for the Crystalfontz CFA-10036 Shawn Guo
2012-06-21 14:22   ` Maxime Ripard
2012-06-22  2:12     ` 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=1340268415-5022-1-git-send-email-maxime.ripard@free-electrons.com \
    --to=maxime.ripard@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.