linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	<ludovic.desroches@microchip.com>,  <agross@kernel.org>,
	<wsa+renesas@sang-engineering.com>, <ldewangan@nvidia.com>
Cc: alexandre.belloni@bootlin.com, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, vkoul@kernel.org,
	thierry.reding@gmail.com, linux-i2c@vger.kernel.org,
	linux-tegra@vger.kernel.org, digetx@gmail.com,
	bjorn.andersson@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] i2c: tegra: Use dma_request_chan() directly for channel request
Date: Thu, 14 Nov 2019 07:05:47 +0000	[thread overview]
Message-ID: <f30dcd10-69ea-3bf7-99b2-8d12fc5e4cc0@nvidia.com> (raw)
In-Reply-To: <20191113092235.30440-5-peter.ujfalusi@ti.com>


On 13/11/2019 09:22, Peter Ujfalusi wrote:
> dma_request_slave_channel_reason() is:
> #define dma_request_slave_channel_reason(dev, name) \
> 	dma_request_chan(dev, name)
> 
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
>  drivers/i2c/busses/i2c-tegra.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index c1683f9338b4..a98bf31d0e5c 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -413,7 +413,7 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)
>  		return 0;
>  	}
>  
> -	chan = dma_request_slave_channel_reason(i2c_dev->dev, "rx");
> +	chan = dma_request_chan(i2c_dev->dev, "rx");
>  	if (IS_ERR(chan)) {
>  		err = PTR_ERR(chan);
>  		goto err_out;
> @@ -421,7 +421,7 @@ static int tegra_i2c_init_dma(struct tegra_i2c_dev *i2c_dev)
>  
>  	i2c_dev->rx_dma_chan = chan;
>  
> -	chan = dma_request_slave_channel_reason(i2c_dev->dev, "tx");
> +	chan = dma_request_chan(i2c_dev->dev, "tx");
>  	if (IS_ERR(chan)) {
>  		err = PTR_ERR(chan);
>  		goto err_out;
> 
Acked-by: Jon Hunter <jonathanh@nvidia.com>

Cheers!
Jon


-- 
nvpublic

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-11-14  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  9:22 [PATCH 0/4] i2c: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13  9:22 ` [PATCH 1/4] i2c: at91: " Peter Ujfalusi
2019-11-13 13:35   ` Ludovic.Desroches
2019-11-13  9:22 ` [PATCH 2/4] i2c: qup: " Peter Ujfalusi
2019-11-13  9:22 ` [PATCH 3/4] i2c: sh_mobile: " Peter Ujfalusi
2019-11-13  9:22 ` [PATCH 4/4] i2c: tegra: " Peter Ujfalusi
2019-11-14  7:05   ` Jon Hunter [this message]
2019-11-14  4:34 ` [PATCH 0/4] i2c: " Vinod Koul
2019-11-14 20:43 ` Wolfram Sang

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=f30dcd10-69ea-3bf7-99b2-8d12fc5e4cc0@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=agross@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=digetx@gmail.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=thierry.reding@gmail.com \
    --cc=vkoul@kernel.org \
    --cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).