Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752151AbbGWHBH (ORCPT ); Thu, 23 Jul 2015 03:01:07 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:58631 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750969AbbGWHA6 convert rfc822-to-8bit (ORCPT ); Thu, 23 Jul 2015 03:00:58 -0400 X-Auth-Info: U3Da1p3TgGzycoQVk1TZmL2IpG7iZLTpRX/al/5W0B4= From: Marek Vasut To: Cyrille Pitchen Subject: Re: [PATCH v2 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change Date: Thu, 23 Jul 2015 09:00:50 +0200 User-Agent: KMail/1.13.7 (Linux/3.14-2-amd64; KDE/4.13.1; x86_64; ; ) Cc: nicolas.ferre@atmel.com, broonie@kernel.org, linux-spi@vger.kernel.org, dwmw2@infradead.org, computersforpeace@gmail.com, zajec5@gmail.com, beanhuo@micron.com, juhosg@openwrt.org, shijie.huang@intel.com, ben@decadent.org.uk, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linux-mtd@lists.infradead.org References: <201507221541.46135.marex@denx.de> <55AFC3F0.5050002@atmel.com> In-Reply-To: <55AFC3F0.5050002@atmel.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Message-Id: <201507230900.50570.marex@denx.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2180 Lines: 54 On Wednesday, July 22, 2015 at 06:25:20 PM, Cyrille Pitchen wrote: > Hi Marek, > > Le 22/07/2015 15:41, Marek Vasut a ?crit : > > On Wednesday, July 22, 2015 at 03:17:06 PM, Cyrille Pitchen wrote: > >> Once the Quad SPI mode has been enabled on a Micron flash memory, this > >> device expects ALL the following commands to use the SPI 4-4-4 protocol. > >> The (Q)SPI controller needs to be notified about the protocol change so > >> it can adapt and keep on dialoging with the Micron memory. > >> > >> Signed-off-by: Cyrille Pitchen > >> --- > >> > >> drivers/mtd/spi-nor/spi-nor.c | 17 +++++++++++++++++ > >> include/linux/mtd/spi-nor.h | 13 +++++++++++++ > >> 2 files changed, 30 insertions(+) > >> > >> diff --git a/drivers/mtd/spi-nor/spi-nor.c > >> b/drivers/mtd/spi-nor/spi-nor.c index d78831b4422b..93627d4e6be8 100644 > >> --- a/drivers/mtd/spi-nor/spi-nor.c > >> +++ b/drivers/mtd/spi-nor/spi-nor.c > >> @@ -163,6 +163,18 @@ static inline int write_disable(struct spi_nor > >> *nor) > >> > >> return nor->write_reg(nor, SPINOR_OP_WRDI, NULL, 0, 0); > >> > >> } > >> > >> +/* > >> + * Notify the (Q)SPI controller about the new protocol to be used. > > > > Hi! > > > > Can you please just reword this a little, so that it is absolutelly clear > > even to the less bright of us (like me) that this is a notification > > coming from the upper layers (ie. the spi-nor framework) toward the > > hardware ? > > Sure, no problem! what about the following? > > /* > * Let the spi-nor framework notify lower layers, especially the driver of > the * (Q)SPI controller, about the new protocol to be used. Indeed, once > the * spi-nor framework has sent manufacturer specific commands to a > memory to * enable its Quad SPI mode, it should immediately after tell the > QSPI * controller to use the very same Quad SPI protocol as expected by > the memory. */ Sure, excellent, thanks ! :-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/