From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: kernel@avr32linux.org, linux-kernel@vger.kernel.org,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Subject: Re: [PATCH 3/4] atmel-mci: support multiple mmc slots
Date: Tue, 23 Sep 2008 19:53:42 +0200 [thread overview]
Message-ID: <20080923195342.52b1164d@mjolnir.drzeus.cx> (raw)
In-Reply-To: <1222101497-21183-4-git-send-email-haavard.skinnemoen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
On Mon, 22 Sep 2008 18:38:16 +0200
Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
> The Atmel MCI controller can drive multiple cards through separate sets
> of pins, but only one at a time. This patch adds support for
> multiplexing access to the controller so that multiple card slots can be
> used as if they were hooked up to separate mmc controllers.
>
This multiplexing shenanigans seems to be all the rage these days...
>
> static void atmci_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
> {
> - struct atmel_mci *host = mmc_priv(mmc);
> + struct atmel_mci_slot *slot = mmc_priv(mmc);
> + struct atmel_mci *host = slot->host;
>
> if (ios->clock) {
> u32 clkdiv;
You forgot the most important part; how to handle the clock given two
different requests.
(This will also get a bit more painful when/if the core starts
disabling the clock when a card is idle)
> +
> + if (gpio_is_valid(slot->detect_pin)) {
> + int ret;
> +
> + setup_timer(&slot->detect_timer, atmci_detect_change,
> + (unsigned long)slot);
> +
> + ret = request_irq(gpio_to_irq(slot->detect_pin),
> + atmci_detect_interrupt,
> + IRQF_TRIGGER_FALLING | IRQF_TRIGGER_RISING,
> + "mmc-detect", slot);
> + if (ret) {
> + dev_dbg(&mmc->class_dev,
> + "could not request IRQ %d for detect pin\n",
> + gpio_to_irq(slot->detect_pin));
> + gpio_free(slot->detect_pin);
> + slot->detect_pin = -EBUSY;
> + }
> + }
Fall back to polling?
> + /* We need at least one slot to succeed */
> + ret = -1;
> + if (pdata->slot[0].bus_width)
> + ret &= atmci_init_slot(host, &pdata->slot[0],
> + MCI_SDCSEL_SLOT_A);
> + if (pdata->slot[1].bus_width)
> + ret &= atmci_init_slot(host, &pdata->slot[1],
> + MCI_SDCSEL_SLOT_B);
> + if (ret) {
> + ret = -ENODEV;
> + goto err_init_slot;
> }
Memory/resource leak.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-23 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 16:38 [PATCH 0/4] atmel-mci: updates for 2.6.28 Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 1/4] atmel-mci: Implement tasklet as a state machine Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 2/4] atmel-mci: Platform code for supporting multiple mmc slots Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 3/4] atmel-mci: support " Haavard Skinnemoen
2008-09-22 16:38 ` [PATCH 4/4] atmel-mci: Add experimental DMA support Haavard Skinnemoen
2008-09-23 17:53 ` Pierre Ossman [this message]
2008-09-23 18:16 ` [PATCH 3/4] atmel-mci: support multiple mmc slots Haavard Skinnemoen
2008-09-23 19:12 ` Pierre Ossman
2008-09-24 14:35 ` Haavard Skinnemoen
2008-09-25 7:05 ` Pierre Ossman
2008-09-25 13:51 ` Haavard Skinnemoen
2008-10-02 8:31 ` Pierre Ossman
2008-09-23 17:40 ` [PATCH 2/4] atmel-mci: Platform code for supporting " Pierre Ossman
2008-09-23 18:02 ` Haavard Skinnemoen
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=20080923195342.52b1164d@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®