linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: David Lechner <david@lechnology.com>, nsekhar@ti.com
Cc: ulf.hansson@linaro.org, khilman@kernel.org,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] mmc: davinci: don't use dma platform resources
Date: Wed, 16 Mar 2016 10:46:42 +0200	[thread overview]
Message-ID: <56E91D72.4030606@ti.com> (raw)
In-Reply-To: <56E842EE.7030301@lechnology.com>

On 03/15/16 19:14, David Lechner wrote:
> On 03/15/2016 03:54 AM, Peter Ujfalusi wrote:
>> On 03/15/16 00:54, David Lechner wrote:
>>>
>>>       host->dma_tx =
>>> -        dma_request_slave_channel_compat(mask, edma_filter_fn,
>>> -                &host->txdma, mmc_dev(host->mmc), "tx");
>>> +        dma_request_slave_channel(mmc_dev(host->mmc), "tx");
>>
>> you would need to use dma_request_chan() to be able to rely on the legacy
>> channel mapping.
>> I have staged commits for converting all daVinci and OMAP drivers, I'll attach
>> the patch I have for davinci-mmc for reference.
>> When we convert to use the dma_request_chan() we can handle deferred probing
>> also...
>>
> 
> OK. So I should redo this patch on top of the patch you attached?

Or replace your patch with mine in your series. In my patch I forgot to remove
the 'u32 rxdma, txdma;' from struct mmc_davinci_host...

-- 
Péter

  reply	other threads:[~2016-03-16  8:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 23:50 [PATCH 0/4] davinci_mmc device tree fixes David Lechner
2016-03-09 23:50 ` [PATCH 1/4] mmc: davinci: remove matching string David Lechner
2016-03-14 13:41   ` Sekhar Nori
2016-03-09 23:50 ` [PATCH 2/4] mmc: davinci: fix unwinding in probe David Lechner
2016-03-14 11:52   ` Sekhar Nori
2016-03-09 23:50 ` [PATCH 3/4] mmc: davinci: prepare clock David Lechner
2016-03-14 11:54   ` Sekhar Nori
2016-03-14 17:09     ` David Lechner
2016-03-14 17:13       ` David Lechner
2016-03-15  5:16       ` Sekhar Nori
2016-03-09 23:50 ` [PATCH 4/4] mmc: davinci: suppress waring when using DT David Lechner
2016-03-14 13:41   ` Sekhar Nori
2016-03-14 22:54     ` [PATCH v2 0/5] davinci_mmc fixes David Lechner
2016-03-14 22:54       ` [PATCH v2 1/5] mmc: davinci: remove matching string David Lechner
2016-03-15  9:12         ` Sekhar Nori
2016-03-14 22:54       ` [PATCH v2 2/5] mmc: davinci: fix unwinding in probe David Lechner
2016-03-15  9:10         ` Sekhar Nori
2016-03-14 22:54       ` [PATCH v2 3/5] mmc: davinci: prepare clock David Lechner
2016-03-15  9:13         ` Sekhar Nori
2016-03-14 22:54       ` [PATCH v2 4/5] mmc: davinci: don't use dma platform resources David Lechner
2016-03-15  8:09         ` Sekhar Nori
2016-03-15  8:54         ` Peter Ujfalusi
2016-03-15  8:56           ` Peter Ujfalusi
2016-03-15 17:14           ` David Lechner
2016-03-16  8:46             ` Peter Ujfalusi [this message]
2016-03-14 22:54       ` [PATCH v2 5/5] arm: davinci: remove mmc dma resources David Lechner
2016-03-15  8:23         ` Sekhar Nori
2016-03-15  8:13       ` [PATCH v2 0/5] davinci_mmc fixes Sekhar Nori

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=56E91D72.4030606@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).