Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp753387imm; Thu, 4 Oct 2018 02:46:42 -0700 (PDT) X-Google-Smtp-Source: ACcGV613H7zGW2pK2y25ty4Uuehal4osgUp+Ejf+vpxEyroyTekGbmED4nWCDHmjmTsUS5K8kkch X-Received: by 2002:a62:178f:: with SMTP id 137-v6mr5746593pfx.215.1538646402279; Thu, 04 Oct 2018 02:46:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538646402; cv=none; d=google.com; s=arc-20160816; b=Bvuk/wYFhyuocSRfljB81tVkzT5vj/zxCFcEz7qdF/XEZuGnLBjFMxX087LiKbRhOp gc98jFu0zcwSgLx+gn/JT0CAlQVtG5CtaSM4sC9sV3d82ip0HB5MsKmI6Dsh3Yiww9WX w+fhsBLQheg0KZ9zYoxSLSfvF2+0rUuOKUugiICNPlqLCgBgPxstJVdQOci59zqdn2pc irGzPrCLhKsQ27oZlWkIMdSgYc5PG8JIEU8yR6OK7tzpy1A8Bvr6bNp/Sgkoi5yr0aH5 r6iRO5lmt223GypSSNt3SH87JrYtW99mApE8zkxPs5+6U+PkfThNRNGGKcsoCGnFdDgk rt4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=uRKAfrWxTVkKmMdnuxesk4GaQQkR5m6Ey7qlzqO7c08=; b=H6xiv57PKMWUEREgQhRktGOC7GtUq6SbKApvEI+Km/WETuZ/1R95wNo3z640nCFseB 3W177haupZdhpHKCZiudgPZhH7GHg5ZpEp+QGGMLBt4telenOby+GKQNeJ8X7w3B2U76 OdZH4KO0BMomcecjtt0rwQYquQI6KjMo/ANQRyQ55J2j1UJNtySYlmPoiw4jr00knwHj XFfGbrCr8swOr0tVXTBA4SVHEeoZHj5lMrh83lA9Avae/ct9X2+naMKTvi2N73Dm5tqb GYZW+68j1lOTJzhbw/oWAdROBCsny5B2sOWNUNI4cryqfGXFeJ4S3PhjJz2lYB5e3FZ4 N0Lg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w15-v6si4386149pgc.366.2018.10.04.02.46.26; Thu, 04 Oct 2018 02:46:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727755AbeJDQif (ORCPT + 99 others); Thu, 4 Oct 2018 12:38:35 -0400 Received: from mail.bootlin.com ([62.4.15.54]:59757 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727046AbeJDQif (ORCPT ); Thu, 4 Oct 2018 12:38:35 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 905CC20802; Thu, 4 Oct 2018 11:46:05 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 Received: from bbrezillon (AAubervilliers-681-1-28-153.w90-88.abo.wanadoo.fr [90.88.148.153]) by mail.bootlin.com (Postfix) with ESMTPSA id 410F8206A7; Thu, 4 Oct 2018 11:45:35 +0200 (CEST) Date: Thu, 4 Oct 2018 11:45:35 +0200 From: Boris Brezillon To: Vignesh R Cc: Marek Vasut , Rob Herring , Brian Norris , Yogesh Gaur , Linux ARM Mailing List , , , Subject: Re: [PATCH 1/3] mtd: spi-nor: Add Octal mode support for mt35xu512aba Message-ID: <20181004114535.3a5dba05@bbrezillon> In-Reply-To: <20181003165603.2579-2-vigneshr@ti.com> References: <20181003165603.2579-1-vigneshr@ti.com> <20181003165603.2579-2-vigneshr@ti.com> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Oct 2018 22:26:01 +0530 Vignesh R wrote: > Micron's mt35xu512aba flash is an Octal flash that has x8 IO lines. It > supports read/write over 8 IO lines simulatenously. Add support for > Octal read mode for Micron mt35xu512aba. > Unfortunately, this flash is only complaint to SFDP JESD216B and does not > seem to support newer JESD216C standard that provides auto detection of > Octal mode capabilities and opcodes. Therefore, this capability is > manually added using new SPI_NOR_OCTAL_READ flag. > > Signed-off-by: Vignesh R > --- > drivers/mtd/spi-nor/spi-nor.c | 11 ++++++++++- > include/linux/mtd/spi-nor.h | 2 ++ > 2 files changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c > index aff5e6ff0b2c..4926e805a8cb 100644 > --- a/drivers/mtd/spi-nor/spi-nor.c > +++ b/drivers/mtd/spi-nor/spi-nor.c > @@ -90,6 +90,7 @@ struct flash_info { > #define NO_CHIP_ERASE BIT(12) /* Chip does not support chip erase */ > #define SPI_NOR_SKIP_SFDP BIT(13) /* Skip parsing of SFDP tables */ > #define USE_CLSR BIT(14) /* use CLSR command */ > +#define SPI_NOR_OCTAL_READ BIT(15) /* Flash supports Octal Read */ Hm, we'll need to clarify what OCTAL means. I see at least 3 different modes using 8 IO lines (1-1-8, 1-8-8 and 8-8-8) and all of them could be qualified as "octal" modes. So how about renaming this macro SPI_NOR_1_1_8_READ. Also, I fear we'll soon run out of bits in ->flags if we keep adding one flag per mode which is why I proposed a solution to let flash chips tweak the flash parameters as they wish [1][2]. I'm not saying we should do it now, but we should definitely plan for something like that. [1]https://github.com/bbrezillon/linux/commit/9c672e4c85a91f1b0803c9c6e4b8f3aae5d79ffb [2]https://github.com/bbrezillon/linux/commit/3a5515c8821314c06a3d84f9861aefe476bb711e