From: David Lechner <david@lechnology.com>
To: Sekhar Nori <nsekhar@ti.com>, Mark Brown <broonie@kernel.org>
Cc: khilman@kernel.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: davinci: Allow device tree devices to use DMA
Date: Tue, 6 Dec 2016 20:28:10 -0600 [thread overview]
Message-ID: <588633b2-99c2-528f-35f4-fef898a79961@lechnology.com> (raw)
In-Reply-To: <fd697f3b-dba1-1e5f-c12c-45f71c0c07a1@ti.com>
On 11/21/2016 02:37 AM, Sekhar Nori wrote:
> On Sunday 20 November 2016 10:31 PM, David Lechner wrote:
>
>> On 11/20/2016 06:59 AM, Sekhar Nori wrote:
>
>>> On Saturday 19 November 2016 10:11 AM, David Lechner wrote:
>
>>>> @@ -400,6 +401,9 @@ static int davinci_spi_of_setup(struct spi_device
>>>> *spi)
>>>> if (!of_property_read_u32(np, "ti,spi-wdelay", &prop))
>>>> spicfg->wdelay = (u8)prop;
>>>> spi->controller_data = spicfg;
>>>> + /* Use DMA for device if master supports it */
>>>> + if (dspi->dma_rx)
>>>
>>> This should be
>>>
>>> if (!(IS_ERR(dpsi->dma_rx) || IS_ERR(dspi->dma_tx))
>>
>>
>> There is the following code in davinci_spi_probe():
>>
>> ret = davinci_spi_request_dma(dspi);
>> if (ret == -EPROBE_DEFER) {
>> goto free_clk;
>> } else if (ret) {
>> dev_info(&pdev->dev, "DMA is not supported (%d)\n", ret);
>> dspi->dma_rx = NULL;
>> dspi->dma_tx = NULL;
>> }
>>
>> So, I does not look like it is possible to get anything other than NULL
>> or a valid pointer for dpsi->dma_rx and that checking dpsi->dma_tx is
>> not necessary.
>>
>> So, I think if (dspi->dma_rx) is sufficient. In fact the same check is
>> used during unwinding if the probe function fails.
>
> You are right, I see it now. Setting dma_rx to NULL overriding the error
> value is confusing since dma_request_chan() itself does not use NULL as
> an error value.
>
> I think it is better to fix the existing code to remove the NULL
> overwrite and use IS_ERR() instead. You should probably wait for some
> feedback from the SPI maintainer though.
>
> Thanks,
> Sekhar
>
There don't seem to be any further comments. Using NULL here makes more
sense to me, so I am inclined to leave this patch as-is.
prev parent reply other threads:[~2016-12-07 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 4:41 David Lechner
2016-11-20 12:59 ` Sekhar Nori
2016-11-20 17:01 ` David Lechner
2016-11-21 8:37 ` Sekhar Nori
2016-12-07 2:28 ` David Lechner [this message]
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=588633b2-99c2-528f-35f4-fef898a79961@lechnology.com \
--to=david@lechnology.com \
--cc=broonie@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nsekhar@ti.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
all inboxes | Powered by JetHome®