From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E272CC43381 for ; Wed, 20 Mar 2019 07:39:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AF1A821850 for ; Wed, 20 Mar 2019 07:39:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726303AbfCTHjS (ORCPT ); Wed, 20 Mar 2019 03:39:18 -0400 Received: from mga18.intel.com ([134.134.136.126]:8797 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725942AbfCTHjS (ORCPT ); Wed, 20 Mar 2019 03:39:18 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Mar 2019 00:39:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,248,1549958400"; d="scan'208";a="124177436" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.157]) by orsmga007.jf.intel.com with SMTP; 20 Mar 2019 00:39:13 -0700 Received: by lahna (sSMTP sendmail emulation); Wed, 20 Mar 2019 09:39:12 +0200 Date: Wed, 20 Mar 2019 09:39:12 +0200 From: Mika Westerberg To: Tudor.Ambarus@microchip.com Cc: alexander.sverdlin@nokia.com, linux-mtd@lists.infradead.org, marek.vasut@gmail.com, dwmw2@infradead.org, computersforpeace@gmail.com, bbrezillon@kernel.org, richard@nod.at, bmeng.cn@gmail.com, romain.porte@nokia.com, pascal.fabreges@nokia.com, stable@vger.kernel.org Subject: Re: [PATCH v4] mtd: spi-nor: intel-spi: Avoid crossing 4K address boundary on read/write Message-ID: <20190320073912.GP3622@lahna.fi.intel.com> References: <20190319171749.19052-1-alexander.sverdlin@nokia.com> <3af53f8c-8606-c646-2e77-e6dfc8473f66@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3af53f8c-8606-c646-2e77-e6dfc8473f66@microchip.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.11.3 (2019-02-01) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Mar 20, 2019 at 06:49:19AM +0000, Tudor.Ambarus@microchip.com wrote: > Mika, > > Would you please add your Acked-by again? It's dropped in v4. Sure. > Looks good for me, below is my R-b. > > Thanks! > > On 03/19/2019 07:18 PM, Sverdlin, Alexander (Nokia - DE/Ulm) wrote: > > External E-Mail > > > > > > From: Alexander Sverdlin > > > > 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 > > Tested-by: Pascal Fabreges > > Signed-off-by: Alexander Sverdlin > > Reviewed-by: Tudor Ambarus Acked-by: Mika Westerberg