linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, <mchehab@kernel.org>,
	<rashanmu@gmail.com>, <geert@linux-m68k.org>
Cc: <vkoul@kernel.org>, <linux-media@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2] media: rcar_drif: Use dma_request_chan() instead dma_request_slave_channel()
Date: Wed, 26 Feb 2020 11:22:08 +0200	[thread overview]
Message-ID: <047fb0e6-9d43-1d9b-0e3a-2da58613c640@ti.com> (raw)
In-Reply-To: <d1c3aec0-7b8f-5f78-e055-8dd87bee801b@xs4all.nl>

Hi Hans,

On 2/25/20 2:07 PM, Hans Verkuil wrote:
> Hi Peter,
> 
> On 1/20/20 1:47 PM, Peter Ujfalusi wrote:
>> dma_request_slave_channel() is a wrapper on top of dma_request_chan()
>> eating up the error code.
>>
>> By using dma_request_chan() directly the driver can support deferred
>> probing against DMA.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> 
> Unfortunately the v1 version of this patch got merged, so can you make a
> new patch against the current media_tree master to bring it up to date
> with this v3?

Sure, I'll send an update patch in couple of minutes.

> My apologies for this.

No issue

Regards,
- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2020-02-26  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 12:47 [PATCH v2] media: rcar_drif: Use dma_request_chan() instead dma_request_slave_channel() Peter Ujfalusi
2020-01-20 12:49 ` Peter Ujfalusi
2020-02-25 12:07 ` Hans Verkuil
2020-02-26  9:22   ` Peter Ujfalusi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-20 12:36 Peter Ujfalusi

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=047fb0e6-9d43-1d9b-0e3a-2da58613c640@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=geert@linux-m68k.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rashanmu@gmail.com \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).