All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Zhu Richard-R65037 <r65037@freescale.com>
Cc: "Eric Bénard" <eric@eukrea.com>,
	"Arnaud Patard" <arnaud.patard@rtp-net.org>,
	linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Guo Shawn-R65073" <R65073@freescale.com>
Subject: Re: [PATCH 0/6] SD/MMC driver for MX25/35/51
Date: Mon, 18 Oct 2010 13:36:35 +0200	[thread overview]
Message-ID: <20101018113635.GA15440@pengutronix.de> (raw)
In-Reply-To: <A88EF4D64D8447468743DC1503C0B6CA0D581A@zch01exm22.fsl.freescale.net>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

Hi Richard,

On Mon, Oct 18, 2010 at 04:48:07PM +0800, Zhu Richard-R65037 wrote:

> The debug msg "mmc0: mmc_rescan: trying to init card at 400000 Hz..." are dumped out repeatedly.
> ROOT: There are pr_info codes in the mmc_rescan func.

There was already a patch on this list fixing it.

> The other:
> Encounter the Timeout and CRC error when the sandisk 4G SDHC card are used as the ROOTFS storage media
> When I boot up the BBG board.
> 
> It seems that the "SDHCI_QUIRK_BROKEN_TIMEOUT_VAL" is mandatory required at my side when I did the tests
>  on BBG3.0 board, and the i.MX51 board can support the "MULTI-BLOCK".

Okay, this can be fixed...

> BTW, I still can't fetch out the latest codes out, that means I still can't found the V5 patches, although I run
> the git fetch and git rebase. :(

My branch gets rebased because I can't mainline the driver with all my
incremental improvements. Does just taking the branch and cherry-pick
your additions work? (BTW meanwhile you can also just use mmc-next)

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] SD/MMC driver for MX25/35/51
Date: Mon, 18 Oct 2010 13:36:35 +0200	[thread overview]
Message-ID: <20101018113635.GA15440@pengutronix.de> (raw)
In-Reply-To: <A88EF4D64D8447468743DC1503C0B6CA0D581A@zch01exm22.fsl.freescale.net>

Hi Richard,

On Mon, Oct 18, 2010 at 04:48:07PM +0800, Zhu Richard-R65037 wrote:

> The debug msg "mmc0: mmc_rescan: trying to init card at 400000 Hz..." are dumped out repeatedly.
> ROOT: There are pr_info codes in the mmc_rescan func.

There was already a patch on this list fixing it.

> The other:
> Encounter the Timeout and CRC error when the sandisk 4G SDHC card are used as the ROOTFS storage media
> When I boot up the BBG board.
> 
> It seems that the "SDHCI_QUIRK_BROKEN_TIMEOUT_VAL" is mandatory required at my side when I did the tests
>  on BBG3.0 board, and the i.MX51 board can support the "MULTI-BLOCK".

Okay, this can be fixed...

> BTW, I still can't fetch out the latest codes out, that means I still can't found the V5 patches, although I run
> the git fetch and git rebase. :(

My branch gets rebased because I can't mainline the driver with all my
incremental improvements. Does just taking the branch and cherry-pick
your additions work? (BTW meanwhile you can also just use mmc-next)

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101018/bd8ece60/attachment.sig>

  parent reply	other threads:[~2010-10-18 11:36 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 14:21 [PATCH 0/6] SD/MMC driver for MX25/35/51 Wolfram Sang
2010-10-11 14:21 ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 1/6] mmc: sdhci-pltfm: Add structure for host-specific data Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 2/6] mmc: sdhci-pltfm: move .h-file into apropriate subdir Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 3/6] mmc: sdhci: introduce private get_ro Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 4/6] mmc: sdhci_pltfm: pass more data on custom init-call Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 5/6] mmc: sdhci-of-esdhc: factor out common stuff Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-11 17:10   ` [PATCH v2 " Wolfram Sang
2010-10-11 17:10     ` Wolfram Sang
2010-10-11 18:33     ` Chris Ball
2010-10-11 18:33       ` Chris Ball
2010-10-13 10:22       ` Zhu Richard-R65037
2010-10-13 10:22         ` Zhu Richard-R65037
2010-10-13 10:31         ` Wolfram Sang
2010-10-13 10:31           ` Wolfram Sang
2010-10-11 14:21 ` [PATCH 6/6] mmc: sdhci-pltfm: add pltfm-driver for imx35/51 Wolfram Sang
2010-10-11 14:21   ` Wolfram Sang
2010-10-14  3:07   ` Chris Ball
2010-10-14  3:07     ` Chris Ball
2010-10-11 16:32 ` [PATCH 0/6] SD/MMC driver for MX25/35/51 Chris Ball
2010-10-11 16:32   ` Chris Ball
2010-10-11 16:44   ` Wolfram Sang
2010-10-11 16:44     ` Wolfram Sang
2010-10-11 16:59     ` Chris Ball
2010-10-11 16:59       ` Chris Ball
2010-10-12 22:06 ` Arnaud Patard
2010-10-12 22:06   ` Arnaud Patard (Rtp)
2010-10-13  8:15   ` Eric Bénard
2010-10-13  8:15     ` Eric Bénard
2010-10-13  8:29     ` Wolfram Sang
2010-10-13  8:29       ` Wolfram Sang
2010-10-13  9:28       ` Arnaud Patard
2010-10-13  9:28         ` Arnaud Patard (Rtp)
2010-10-13  9:53         ` Zhu Richard-R65037
2010-10-13  9:53           ` Zhu Richard-R65037
2010-10-13 10:06           ` Wolfram Sang
2010-10-13 10:06             ` Wolfram Sang
2010-10-13 10:09             ` Eric Bénard
2010-10-13 10:09               ` Eric Bénard
2010-10-13 10:13               ` Zhu Richard-R65037
2010-10-13 10:13                 ` Zhu Richard-R65037
2010-10-13 10:20                 ` Wolfram Sang
2010-10-13 10:20                   ` Wolfram Sang
2010-10-15 10:27                   ` Wolfram Sang
2010-10-15 10:27                     ` Wolfram Sang
2010-10-18  3:29                     ` Zhu Richard-R65037
2010-10-18  3:29                       ` Zhu Richard-R65037
2010-10-18  8:48                     ` Zhu Richard-R65037
2010-10-18  8:48                       ` Zhu Richard-R65037
2010-10-18  9:36                       ` Eric Bénard
2010-10-18  9:36                         ` Eric Bénard
2010-10-18  9:44                         ` Zhu Richard-R65037
2010-10-18  9:44                           ` Zhu Richard-R65037
2010-10-18 11:38                         ` Wolfram Sang
2010-10-18 11:38                           ` Wolfram Sang
2010-10-18 11:51                           ` Eric Bénard
2010-10-18 11:51                             ` Eric Bénard
2010-10-18 11:36                       ` Wolfram Sang [this message]
2010-10-18 11:36                         ` Wolfram Sang
2010-10-15 10:25         ` Wolfram Sang
2010-10-15 10:25           ` Wolfram Sang
2010-10-15 21:20           ` Arnaud Patard
2010-10-15 21:20             ` Arnaud Patard (Rtp)

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=20101018113635.GA15440@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=R65073@freescale.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=eric@eukrea.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=r65037@freescale.com \
    /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.