All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: tony@atomide.com, drzeus-mmc@drzeus.cx,
	ext-adrian.hunter@nokia.com, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OMAP HSMMC: fix MMC3 dma
Date: Sun, 8 Feb 2009 11:10:24 -0800	[thread overview]
Message-ID: <200902081110.25166.david-b@pacbell.net> (raw)
In-Reply-To: <1233052573-6223-1-git-send-email-notasas@gmail.com>

On Tuesday 27 January 2009, Grazvydas Ignotas wrote:
> @@ -1058,6 +1054,25 @@ static int __init omap_mmc_probe(struct platform_device *pdev)
>         OMAP_HSMMC_WRITE(host->base, HCTL,
>                         OMAP_HSMMC_READ(host->base, HCTL) | SDBP);
>  
> +       /* Select DMA lines */
> +       switch (host->id) {
> +       case OMAP_MMC1_DEVID:
> +               host->dma_line_tx = OMAP24XX_DMA_MMC1_TX;
> +               host->dma_line_rx = OMAP24XX_DMA_MMC1_RX;
> +               break;

Actually the cleanest way to do that is through IORESOURCE_DMA
type resources associated with the platform devices ... but
doing it that way requires reworking the MMC platform device
setup logic.  Which I can understand wanting to avoid here.

(I think that rework is worth doing for multiple reasons; this
is just one more.)


> +       case OMAP_MMC2_DEVID:
> +               host->dma_line_tx = OMAP24XX_DMA_MMC2_TX;
> +               host->dma_line_rx = OMAP24XX_DMA_MMC2_RX;
> +               break;
> +       case OMAP_MMC3_DEVID:
> +               host->dma_line_tx = OMAP34XX_DMA_MMC3_TX;
> +               host->dma_line_rx = OMAP34XX_DMA_MMC3_RX;
> +               break;
> +       default:
> +               dev_err(mmc_dev(host->mmc), "Invalid MMC id\n");
> +               goto err_irq;
> +       }
> +
>         /* Request IRQ for MMC operations */
>         ret = request_irq(host->irq, mmc_omap_irq, IRQF_DISABLED,
>                         mmc_hostname(mmc), host);


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: tony@atomide.com, drzeus-mmc@drzeus.cx,
	ext-adrian.hunter@nokia.com, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OMAP HSMMC: fix MMC3 dma
Date: Sun, 8 Feb 2009 11:10:24 -0800	[thread overview]
Message-ID: <200902081110.25166.david-b@pacbell.net> (raw)
In-Reply-To: <1233052573-6223-1-git-send-email-notasas@gmail.com>

On Tuesday 27 January 2009, Grazvydas Ignotas wrote:
> @@ -1058,6 +1054,25 @@ static int __init omap_mmc_probe(struct platform_device *pdev)
>         OMAP_HSMMC_WRITE(host->base, HCTL,
>                         OMAP_HSMMC_READ(host->base, HCTL) | SDBP);
>  
> +       /* Select DMA lines */
> +       switch (host->id) {
> +       case OMAP_MMC1_DEVID:
> +               host->dma_line_tx = OMAP24XX_DMA_MMC1_TX;
> +               host->dma_line_rx = OMAP24XX_DMA_MMC1_RX;
> +               break;

Actually the cleanest way to do that is through IORESOURCE_DMA
type resources associated with the platform devices ... but
doing it that way requires reworking the MMC platform device
setup logic.  Which I can understand wanting to avoid here.

(I think that rework is worth doing for multiple reasons; this
is just one more.)


> +       case OMAP_MMC2_DEVID:
> +               host->dma_line_tx = OMAP24XX_DMA_MMC2_TX;
> +               host->dma_line_rx = OMAP24XX_DMA_MMC2_RX;
> +               break;
> +       case OMAP_MMC3_DEVID:
> +               host->dma_line_tx = OMAP34XX_DMA_MMC3_TX;
> +               host->dma_line_rx = OMAP34XX_DMA_MMC3_RX;
> +               break;
> +       default:
> +               dev_err(mmc_dev(host->mmc), "Invalid MMC id\n");
> +               goto err_irq;
> +       }
> +
>         /* Request IRQ for MMC operations */
>         ret = request_irq(host->irq, mmc_omap_irq, IRQF_DISABLED,
>                         mmc_hostname(mmc), host);



  parent reply	other threads:[~2009-02-08 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 10:36 [PATCH] OMAP HSMMC: fix MMC3 dma Grazvydas Ignotas
2009-01-27 12:02 ` Adrian Hunter
2009-01-27 17:00   ` Grazvydas Ignotas
2009-01-27 17:13     ` Tony Lindgren
2009-01-28  8:35     ` Adrian Hunter
2009-02-08 19:10 ` David Brownell [this message]
2009-02-08 19:10   ` David Brownell

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=200902081110.25166.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=ext-adrian.hunter@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.com \
    --cc=tony@atomide.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.