From: Purna Chandra Mandal <purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>,
Joshua Henderson
<digitalpeer-icZdIMMiY0PM6KjX8ROVJw@public.gmane.org>,
Ulf Hansson <ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v4 2/2] spi: spi-pic32: Add PIC32 SPI master driver
Date: Thu, 31 Mar 2016 16:39:38 +0530 [thread overview]
Message-ID: <56FD0572.1030309@microchip.com> (raw)
In-Reply-To: <20160330154839.GZ2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 03/30/2016 09:18 PM, Mark Brown wrote:
> On Wed, Mar 30, 2016 at 04:19:16PM +0530, Purna Chandra Mandal wrote:
>> On 03/29/2016 09:55 PM, Mark Brown wrote:
>>> On Tue, Mar 29, 2016 at 05:32:41PM +0530, Purna Chandra Mandal wrote:
>>>> MMC_SPI will have to terminate on-going MMC transactions and it is
>>>> done by calling setup(). It is assumed that setup() will always leave
>>>> the chip-select deactivated.
>>> No, this is just completely broken - that's quite simply not what
>>> setup() does. See spi-summary. There is *no* code in the core that
>>> terminates ongoing transfers as a result of calling setup(), if that's
>>> happening it's a result of triggering error handling.
>> Description of spi_setup() in spi.c clearly mentions that "When this
>> function returns, the spi device is deselected" and this is only
>> possible if (at least) chip-select is deactivated.
> This doesn't say anything about any ongoing operations! Trying to do a
> setup() with active transfers on the device is just not sensible, it is
> intended to be used on an idle device. I would not expect it to work
> reliably on an active device.
agreed.
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Purna Chandra Mandal <purna.mandal@microchip.com>
To: Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Joshua Henderson <digitalpeer@digitalpeer.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v4 2/2] spi: spi-pic32: Add PIC32 SPI master driver
Date: Thu, 31 Mar 2016 16:39:38 +0530 [thread overview]
Message-ID: <56FD0572.1030309@microchip.com> (raw)
In-Reply-To: <20160330154839.GZ2350@sirena.org.uk>
On 03/30/2016 09:18 PM, Mark Brown wrote:
> On Wed, Mar 30, 2016 at 04:19:16PM +0530, Purna Chandra Mandal wrote:
>> On 03/29/2016 09:55 PM, Mark Brown wrote:
>>> On Tue, Mar 29, 2016 at 05:32:41PM +0530, Purna Chandra Mandal wrote:
>>>> MMC_SPI will have to terminate on-going MMC transactions and it is
>>>> done by calling setup(). It is assumed that setup() will always leave
>>>> the chip-select deactivated.
>>> No, this is just completely broken - that's quite simply not what
>>> setup() does. See spi-summary. There is *no* code in the core that
>>> terminates ongoing transfers as a result of calling setup(), if that's
>>> happening it's a result of triggering error handling.
>> Description of spi_setup() in spi.c clearly mentions that "When this
>> function returns, the spi device is deselected" and this is only
>> possible if (at least) chip-select is deactivated.
> This doesn't say anything about any ongoing operations! Trying to do a
> setup() with active transfers on the device is just not sensible, it is
> intended to be used on an idle device. I would not expect it to work
> reliably on an active device.
agreed.
next prev parent reply other threads:[~2016-03-31 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 13:42 [PATCH v4 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal
2016-03-23 13:42 ` Purna Chandra Mandal
2016-03-23 13:42 ` Purna Chandra Mandal
2016-03-23 13:42 ` Purna Chandra Mandal
2016-03-23 13:42 ` [PATCH v4 2/2] spi: spi-pic32: Add PIC32 SPI master driver Purna Chandra Mandal
[not found] ` <1458740576-9168-2-git-send-email-purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-03-28 19:26 ` Mark Brown
2016-03-28 19:26 ` Mark Brown
[not found] ` <20160328192629.GG2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-29 12:02 ` Purna Chandra Mandal
2016-03-29 12:02 ` Purna Chandra Mandal
[not found] ` <56FA6EE1.3000405-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-03-29 16:25 ` Mark Brown
2016-03-29 16:25 ` Mark Brown
[not found] ` <20160329162501.GP2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-30 10:49 ` Purna Chandra Mandal
2016-03-30 10:49 ` Purna Chandra Mandal
[not found] ` <56FBAF2C.9090401-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-03-30 15:48 ` Mark Brown
2016-03-30 15:48 ` Mark Brown
[not found] ` <20160330154839.GZ2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-31 11:09 ` Purna Chandra Mandal [this message]
2016-03-31 11:09 ` Purna Chandra Mandal
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=56FD0572.1030309@microchip.com \
--to=purna.mandal-uwl1gki3jzl3ogb3hspcza@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=digitalpeer-icZdIMMiY0PM6KjX8ROVJw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
--cc=ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.