From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
Michal Suchanek <hramrach@gmail.com>,
martin@sperl.org
Subject: Re: RfC: Handle SPI controller limitations like maximum message length
Date: Fri, 20 Nov 2015 20:37:23 +0100 [thread overview]
Message-ID: <564F7673.40205@gmail.com> (raw)
In-Reply-To: <20151120191842.GE1929@sirena.org.uk>
Am 20.11.2015 um 20:18 schrieb Mark Brown:
> On Fri, Nov 20, 2015 at 07:59:37PM +0100, Heiner Kallweit wrote:
>
>> OK, I interpret this as:
>> Controller drivers shall return 0 only if the complete message was
>> transferred successfully.
>
> Yes.
>
>> If a controller driver returns an error it has the option to set
>> actual_length to what was transferred successfully.
>
> It should always do this.
>
>> This means we can't use patch 4 from Michal because it bails out as soon
>> as the underlying SPI transfer returns an error.
>
> I haven't seen that patch.
>
Sorry, this was addressed to Brian. It's about a mtd spi-nor patch.
http://lists.infradead.org/pipermail/linux-mtd/2015-August/061062.html
Most likely neither you nor linux-spi was on cc.
(Oh, it was patch 7 of the series, not 4.)
WARNING: multiple messages have this Message-ID (diff)
From: Heiner Kallweit <hkallweit1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Brian Norris
<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michal Suchanek
<hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
martin-d5rIkyn9cnPYtjvyW6yDsg@public.gmane.org
Subject: Re: RfC: Handle SPI controller limitations like maximum message length
Date: Fri, 20 Nov 2015 20:37:23 +0100 [thread overview]
Message-ID: <564F7673.40205@gmail.com> (raw)
In-Reply-To: <20151120191842.GE1929-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Am 20.11.2015 um 20:18 schrieb Mark Brown:
> On Fri, Nov 20, 2015 at 07:59:37PM +0100, Heiner Kallweit wrote:
>
>> OK, I interpret this as:
>> Controller drivers shall return 0 only if the complete message was
>> transferred successfully.
>
> Yes.
>
>> If a controller driver returns an error it has the option to set
>> actual_length to what was transferred successfully.
>
> It should always do this.
>
>> This means we can't use patch 4 from Michal because it bails out as soon
>> as the underlying SPI transfer returns an error.
>
> I haven't seen that patch.
>
Sorry, this was addressed to Brian. It's about a mtd spi-nor patch.
http://lists.infradead.org/pipermail/linux-mtd/2015-August/061062.html
Most likely neither you nor linux-spi was on cc.
(Oh, it was patch 7 of the series, not 4.)
--
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
next prev parent reply other threads:[~2015-11-20 19:38 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 21:19 RfC: Handle SPI controller limitations like maximum message length Heiner Kallweit
2015-11-18 21:19 ` Heiner Kallweit
2015-11-18 21:57 ` Mark Brown
2015-11-18 21:57 ` Mark Brown
2015-11-18 22:50 ` Heiner Kallweit
2015-11-18 22:50 ` Heiner Kallweit
2015-11-19 11:40 ` Mark Brown
2015-11-19 11:40 ` Mark Brown
2015-11-19 15:00 ` Martin Sperl
2015-11-19 15:00 ` Martin Sperl
2015-11-19 17:15 ` Mark Brown
2015-11-19 17:15 ` Mark Brown
2015-11-20 0:07 ` Brian Norris
2015-11-20 0:07 ` Brian Norris
2015-11-20 11:06 ` Mark Brown
2015-11-20 11:06 ` Mark Brown
2015-11-20 11:16 ` Martin Sperl
2015-11-20 11:16 ` Martin Sperl
2015-11-20 10:18 ` Martin Sperl
2015-11-20 10:18 ` Martin Sperl
2015-11-20 12:05 ` Mark Brown
2015-11-20 12:05 ` Mark Brown
2015-11-20 12:56 ` Martin Sperl
2015-11-20 12:56 ` Martin Sperl
2015-11-21 13:49 ` Mark Brown
2015-11-21 13:49 ` Mark Brown
2015-11-21 14:10 ` Heiner Kallweit
2015-11-21 14:10 ` Heiner Kallweit
2015-11-21 15:57 ` Michal Suchanek
2015-11-21 15:57 ` Michal Suchanek
2015-11-21 22:59 ` [PATCH 0/3] spi: mtd: Handle HW message length restrictions Heiner Kallweit
2015-11-21 22:59 ` Heiner Kallweit
2015-11-21 23:01 ` [PATCH 1/3] spi: core: add max_msg_size to spi_master Heiner Kallweit
2015-11-21 23:01 ` Heiner Kallweit
2015-11-22 13:16 ` Mark Brown
2015-11-22 13:16 ` Mark Brown
2015-11-22 16:15 ` Heiner Kallweit
2015-11-22 16:15 ` Heiner Kallweit
2015-11-23 11:38 ` Mark Brown
2015-11-23 11:38 ` Mark Brown
2015-11-27 19:26 ` Heiner Kallweit
2015-11-27 19:26 ` Heiner Kallweit
2015-11-30 16:42 ` Mark Brown
2015-11-30 16:42 ` Mark Brown
2015-11-30 20:15 ` Heiner Kallweit
2015-11-30 20:15 ` Heiner Kallweit
2015-11-21 23:08 ` [PATCH 2/3] mtd: m25p80: handle HW message size restrictions Heiner Kallweit
2015-11-21 23:08 ` Heiner Kallweit
2015-11-22 12:51 ` Michal Suchanek
2015-11-22 12:51 ` Michal Suchanek
2015-11-21 23:11 ` [PATCH 3/3] spi: fsl-espi: make use of max_msg_size in spi_master to handle HW restrictions Heiner Kallweit
2015-11-21 23:11 ` Heiner Kallweit
2015-11-30 20:24 ` [PATCH v2 1/2] spi: core: add max_msg_size to spi_master Heiner Kallweit
2015-11-30 20:24 ` Heiner Kallweit
2015-11-30 20:25 ` [PATCH resubmit 2/2] spi: fsl-espi: make use of max_msg_size in spi_master to handle HW restrictions Heiner Kallweit
2015-11-30 20:25 ` Heiner Kallweit
2015-12-01 14:19 ` Mark Brown
2015-12-01 14:19 ` Mark Brown
2015-12-01 18:53 ` Heiner Kallweit
2015-12-01 18:53 ` Heiner Kallweit
2015-11-22 13:19 ` RfC: Handle SPI controller limitations like maximum message length Mark Brown
2015-11-22 13:19 ` Mark Brown
2015-11-20 0:02 ` Brian Norris
2015-11-20 0:02 ` Brian Norris
2015-11-20 6:59 ` Heiner Kallweit
2015-11-20 6:59 ` Heiner Kallweit
2015-11-20 10:06 ` Heiner Kallweit
2015-11-20 10:06 ` Heiner Kallweit
2015-11-20 12:35 ` Mark Brown
2015-11-20 12:35 ` Mark Brown
2015-11-20 18:59 ` Heiner Kallweit
2015-11-20 18:59 ` Heiner Kallweit
2015-11-20 19:05 ` Michal Suchanek
2015-11-20 19:05 ` Michal Suchanek
2015-11-20 19:21 ` Mark Brown
2015-11-20 19:21 ` Mark Brown
2015-11-20 19:44 ` Michal Suchanek
2015-11-20 19:44 ` Michal Suchanek
2015-11-20 23:22 ` Brian Norris
2015-11-20 23:22 ` Brian Norris
2015-11-21 22:53 ` Heiner Kallweit
2015-11-21 22:53 ` Heiner Kallweit
2015-11-20 19:18 ` Mark Brown
2015-11-20 19:18 ` Mark Brown
2015-11-20 19:37 ` Heiner Kallweit [this message]
2015-11-20 19:37 ` Heiner Kallweit
2015-11-20 12:31 ` Mark Brown
2015-11-20 12:31 ` Mark Brown
2015-11-20 12:56 ` Michal Suchanek
2015-11-20 12:56 ` Michal Suchanek
2015-11-20 23:07 ` Brian Norris
2015-11-20 23:07 ` Brian Norris
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=564F7673.40205@gmail.com \
--to=hkallweit1@gmail.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=hramrach@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=martin@sperl.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.