From: <Nicolas.Ferre@microchip.com>
To: <peter.ujfalusi@ti.com>, <broonie@kernel.org>,
<radu_nicolae.pirea@upb.ro>, <shawnguo@kernel.org>,
<s.hauer@pengutronix.de>, <linus.walleij@linaro.org>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<andi@etezian.org>, <ldewangan@nvidia.com>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>
Cc: <alexandre.belloni@bootlin.com>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <krzk@kernel.org>,
<linux-spi@vger.kernel.org>, <vkoul@kernel.org>,
<kgene@kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/9] spi: at91-usart: Use dma_request_chan() directly for channel request
Date: Wed, 13 Nov 2019 14:18:51 +0000 [thread overview]
Message-ID: <05f47be4-f58a-d61f-92e1-c4985c4c3680@microchip.com> (raw)
In-Reply-To: <20191113094256.1108-2-peter.ujfalusi@ti.com>
On 13/11/2019 at 10:42, Peter Ujfalusi wrote:
> External E-Mail
>
>
> 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>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> drivers/spi/spi-at91-usart.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi-at91-usart.c b/drivers/spi/spi-at91-usart.c
> index a40bb2ef89dc..88033422a42a 100644
> --- a/drivers/spi/spi-at91-usart.c
> +++ b/drivers/spi/spi-at91-usart.c
> @@ -132,7 +132,7 @@ static int at91_usart_spi_configure_dma(struct spi_controller *ctlr,
> dma_cap_zero(mask);
> dma_cap_set(DMA_SLAVE, mask);
>
> - ctlr->dma_tx = dma_request_slave_channel_reason(dev, "tx");
> + ctlr->dma_tx = dma_request_chan(dev, "tx");
> if (IS_ERR_OR_NULL(ctlr->dma_tx)) {
> if (IS_ERR(ctlr->dma_tx)) {
> err = PTR_ERR(ctlr->dma_tx);
> @@ -145,7 +145,7 @@ static int at91_usart_spi_configure_dma(struct spi_controller *ctlr,
> goto at91_usart_spi_error_clear;
> }
>
> - ctlr->dma_rx = dma_request_slave_channel_reason(dev, "rx");
> + ctlr->dma_rx = dma_request_chan(dev, "rx");
> if (IS_ERR_OR_NULL(ctlr->dma_rx)) {
> if (IS_ERR(ctlr->dma_rx)) {
> err = PTR_ERR(ctlr->dma_rx);
>
--
Nicolas Ferre
next prev parent reply other threads:[~2019-11-13 14:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:42 [PATCH 0/9] spi: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 9:42 ` [PATCH 1/9] spi: at91-usart: " Peter Ujfalusi
2019-11-13 14:18 ` Nicolas.Ferre [this message]
2019-11-15 12:25 ` Applied "spi: at91-usart: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 2/9] spi: atmel: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 14:18 ` Nicolas.Ferre
2019-11-15 12:25 ` Applied "spi: atmel: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 3/9] spi: fsl-lpspi: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-15 12:25 ` Applied "spi: fsl-lpspi: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 4/9] spi: imx: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-15 12:25 ` Applied "spi: imx: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 5/9] spi: pl022: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 17:16 ` Linus Walleij
2019-11-15 12:25 ` Applied "spi: pl022: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 6/9] spi: qup: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-15 12:25 ` Applied "spi: qup: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 7/9] spi: s3c64xx: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 23:40 ` Andi Shyti
2019-11-14 8:09 ` Peter Ujfalusi
2019-11-14 9:12 ` Andi Shyti
2019-11-14 6:27 ` Krzysztof Kozlowski
2019-11-15 12:25 ` Applied "spi: s3c64xx: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 8/9] spi: tegra114: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-14 7:06 ` Jon Hunter
2019-11-15 12:25 ` Applied "spi: tegra114: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-13 9:42 ` [PATCH 9/9] spi: tegra20-slink: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-14 7:06 ` Jon Hunter
2019-11-15 12:25 ` Applied "spi: tegra20-slink: Use dma_request_chan() directly for channel request" to the spi tree Mark Brown
2019-11-14 4:35 ` [PATCH 0/9] spi: Use dma_request_chan() directly for channel request Vinod Koul
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=05f47be4-f58a-d61f-92e1-c4985c4c3680@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=agross@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andi@etezian.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=radu_nicolae.pirea@upb.ro \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@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).