public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joey Oravec <joravec@drewtech.com>
To: Rob Emanuele <poorarm@shoreis.com>
Cc: nicolas.ferre@atmel.com, linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New AT91 MCI Driver that supports both MCI slots used at the 	same time
Date: Fri, 29 May 2009 11:27:55 -0400	[thread overview]
Message-ID: <4A1FFEFB.6050104@drewtech.com> (raw)
In-Reply-To: <c8284b5b0905281440hd2e4993re3d0d8c590713fa0@mail.gmail.com>

Rob Emanuele wrote:
> This patch creates a new AT91 Multimedia Card Interface (MCI) driver
> that supports using both MCI slots at the same time.  I'm looking for
> others to test this patch on other boards within the same family of
> chips.
>
> This driver is a port the Atmel AVR32 MCI driver which uses similar silicon.
>   
I made all necessary adjustments to test this on my at91sam9261. 
Unfortunately it didn't want to initialize my card so I wasn't able to 
try some of the failures that I experience with the existing driver. I 
sent you a private email with the logs.

> +config MMC_AT91GEN2
> +	tristate "Atmel AT91 Multimedia Card Interface support 2nd gen"
> +	depends on ARCH_AT91
> +	help
>   
On linux-arm-kernel I've detailed a lot of problems involving 
WRITE_MULTIPLE_BLOCK using the at91 mmc/sd controller. In the end you 
might need to exclude certain processors or else have a gigantic 
warning. You can talk to me offline for details on my testing.

> +struct at91_mmc_slot_pdata {
> +        unsigned int            bus_width;
> +        int                     detect_pin;
> +        int                     wp_pin;
> +        int                     vcc_pin;
> +};
>   
Notice in 2.6.29 that at91_mci and most other structures call it 
"det_pin" rather than "detect_pin"

> +	if (host->need_reset) {
> +		at91_mci_write(host, AT91_MCI_CR, AT91_MCI_SWRST);
> +		at91_mci_write(host, AT91_MCI_CR, AT91_MCI_MCIEN);
> +		at91_mci_write(host, AT91_MCI_MR, host->mode_reg);
> +		host->need_reset = false;
> +	}
>   
In my experience some at91s need a reset after every single command, 
otherwise bad things happen. I think the need_reset logic is too 
conservative in this driver.

> +		/*
> +		 * WRPROOF and RDPROOF prevent overruns/underruns by
> +		 * stopping the clock when the FIFO is full/empty.
> +		 * This state is not expected to last for long.
> +		 */
> +		host->mode_reg = (AT91_MCI_CLKDIV & clkdiv) | AT91_MCI_WRPROOF
> +					| AT91_MCI_RDPROOF;
>   
These registers are not in all at91 chips especially the at91sam9261.

> +	if (pdata->slot[0].bus_width) {
> +		ret = at91mci_init_slot(host, &pdata->slot[0],
> +				AT91_MCI_SDCSEL & 0x0, 0);
> +		if (!ret)
> +			nr_slots++;
> +	}
> +	if (pdata->slot[1].bus_width) {
> +		ret = at91mci_init_slot(host, &pdata->slot[1],
> +				AT91_MCI_SDCSEL & 0x1, 1);
> +		if (!ret)
> +			nr_slots++;
> +	}
> +
> +	if (!nr_slots)
> +		goto err_init_slot;
>   
The original pdata had "wire4" which worked (but defaulted to 1-wire) as 
default uninitialized. With this new variable it's easy to register 
mmc_slot_pdata with bus_width set to zero. The difference bit me when 
testing and at least deserves a printk if not a change.

-joey

  reply	other threads:[~2009-05-29 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 21:40 [PATCH] New AT91 MCI Driver that supports both MCI slots used at the same time Rob Emanuele
2009-05-29 15:27 ` Joey Oravec [this message]
2009-06-02 16:53   ` Rob Emanuele
2009-06-03 15:10     ` Nicolas Ferre
2009-06-03 15:45       ` Joey Oravec
2009-06-03 19:02         ` [PATCH][Updated] " Rob Emanuele
2009-06-08 10:47           ` Haavard Skinnemoen
2009-06-08 16:58             ` Rob Emanuele
2009-06-08 18:59               ` Rob Emanuele
2009-06-02  8:49 ` [PATCH] " Nicolas Ferre
2009-06-02 16:31   ` Rob Emanuele

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=4A1FFEFB.6050104@drewtech.com \
    --to=joravec@drewtech.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=poorarm@shoreis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox