From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Sverdlin, Alexander (Nokia - DE/Ulm)" <alexander.sverdlin@nokia.com>
Cc: Bin Meng <bmeng.cn@gmail.com>,
"Porte,
Romain \(Nokia - FR/Paris-Saclay\)" <romain.porte@nokia.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Richard Weinberger <richard@nod.at>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Fabreges,
Pascal \(Nokia - FR/Paris-Saclay\)" <pascal.fabreges@nokia.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3] spi-nor: intel-spi: Avoid crossing 4K address boundary on read/write
Date: Wed, 13 Mar 2019 12:56:17 +0200 [thread overview]
Message-ID: <20190313105617.GU2588@lahna.fi.intel.com> (raw)
In-Reply-To: <20190313082120.17913-1-alexander.sverdlin@nokia.com>
On Wed, Mar 13, 2019 at 08:21:46AM +0000, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> It was observed that reads crossing 4K address boundary are failing.
>
> This limitation is mentioned in Intel documents:
>
> Intel(R) 9 Series Chipset Family Platform Controller Hub (PCH) Datasheet:
>
> "5.26.3 Flash Access
> Program Register Access:
> * Program Register Accesses are not allowed to cross a 4 KB boundary..."
>
> Enhanced Serial Peripheral Interface (eSPI)
> Interface Base Specification (for Client and Server Platforms):
>
> "5.1.4 Address
> For other memory transactions, the address may start or end at any byte
> boundary. However, the address and payload length combination must not
> cross the naturally aligned address boundary of the corresponding Maximum
> Payload Size. It must not cross a 4 KB address boundary."
>
> Avoid this by splitting an operation crossing the boundary into two
> operations.
>
> Cc: stable@vger.kernel.org
> Reported-by: Romain Porte <romain.porte@nokia.com>
> Tested-by: Pascal Fabreges <pascal.fabreges@nokia.com>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nokia.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-03-13 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 8:21 [PATCH v3] spi-nor: intel-spi: Avoid crossing 4K address boundary on read/write Sverdlin, Alexander (Nokia - DE/Ulm)
2019-03-13 10:56 ` Mika Westerberg [this message]
2019-03-19 16:29 ` Tudor.Ambarus
2019-03-19 16:50 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2019-03-25 0:38 ` Sasha Levin
2019-03-19 16:52 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2019-03-19 17:18 ` [PATCH v4] mtd: " Sverdlin, Alexander (Nokia - DE/Ulm)
2019-03-20 6:49 ` Tudor.Ambarus
2019-03-20 7:39 ` Mika Westerberg
2019-03-21 16:48 ` Tudor.Ambarus
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=20190313105617.GU2588@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alexander.sverdlin@nokia.com \
--cc=bbrezillon@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=pascal.fabreges@nokia.com \
--cc=richard@nod.at \
--cc=romain.porte@nokia.com \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@microchip.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).