Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp514805ybl; Fri, 6 Dec 2019 01:33:53 -0800 (PST) X-Google-Smtp-Source: APXvYqyeMTZMRjzVctJ5wzPmUR7BniKyfJv6emPNovr2XQan2FIBkHWF44B0iTw9AIh/LjOkRlhE X-Received: by 2002:a54:4788:: with SMTP id o8mr11648793oic.32.1575624833610; Fri, 06 Dec 2019 01:33:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575624833; cv=none; d=google.com; s=arc-20160816; b=nbmaHfKdjn7R1W+K2+7cjSqMav7N4Qs0xek2Y9cqzuOhWbmTDazDgUFMrcvAUu9ArI pgJsTLtfCMbInMZZRYk4QkiB3F5zFjPDbA3QtdTTaXdPjFPq05fEMJvIDgN8aUUC8A2g 8cfRb9nDahwUmYBsnsUViPwTPl5RoI6GXiFRjk19oQ4xH7UrJOJkdOn+U+ir3yZ15Jpi mXcVQCNjqnHxi3aeanKUcAeRGF6famqcEW8iIZcPhgJdYPLP7+Roslm9EYIMCVqXEeef Eu6hncM+tO0svuS3ApQ5+3wrx7KiIY80miK4aW7dQIavrZesjKY+8KwrOKaaCXcPzUGH kR6A== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=NYFG+Lvsr2YM0gqYd5cEG6Mr/SyvVQ86a1Rho1sT43Y=; b=XOW6CI+71Ihgv7TMsixWsUjqqfuhrWHNuWF6OC1N9oMY84rxc8YLIitatRzZaGidnk wyv+nfPupOTAXaaxqsnUnXOdensiXlHtL1ok5JsH+W+yp0e2QRiAFOmkBKebA/hT0SVY I9mHMNBF+2Q/odx8TsHp/YMKVR2X/FBToZs+6MQUHh6HtyCmWepQEfwe6l7p41RJslpK FWVJczlxeFneWnGSot+y6idrdGQ3q5LR+jC8mAH+YaTLo3bd8Xp7MfnVuILb+exsSqbB Zc4e4ym6/uyyVnFkftvepSV6RCTg17DWdV5k+gvc5eK1TX+Hg7iw5c0hbhCl2wIjIrLF gucA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=kjaIvJwF; 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; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o23si6491301oie.146.2019.12.06.01.33.41; Fri, 06 Dec 2019 01:33:53 -0800 (PST) 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; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=kjaIvJwF; 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; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726201AbfLFJco (ORCPT + 99 others); Fri, 6 Dec 2019 04:32:44 -0500 Received: from lelv0143.ext.ti.com ([198.47.23.248]:38190 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726065AbfLFJco (ORCPT ); Fri, 6 Dec 2019 04:32:44 -0500 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id xB69WIgh024250; Fri, 6 Dec 2019 03:32:18 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1575624738; bh=NYFG+Lvsr2YM0gqYd5cEG6Mr/SyvVQ86a1Rho1sT43Y=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=kjaIvJwFBkPjkYkjai2bYYOUWeUZNL+W9jVd167YeEZklvNKhcGY2HFO7hltZPy/v LNCXBYfJCu8uXM+qijXInVazPyhAhLXBABr3FzfgKyI/f+gOBvwKSpuUhGXze8kG02 ZfBiK4/IU90DEYbKez07jYxy3xTxDqqrkI+BqQAA= Received: from DFLE108.ent.ti.com (dfle108.ent.ti.com [10.64.6.29]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id xB69WIS4074328 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 6 Dec 2019 03:32:18 -0600 Received: from DFLE102.ent.ti.com (10.64.6.23) by DFLE108.ent.ti.com (10.64.6.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Fri, 6 Dec 2019 03:32:14 -0600 Received: from lelv0327.itg.ti.com (10.180.67.183) by DFLE102.ent.ti.com (10.64.6.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3 via Frontend Transport; Fri, 6 Dec 2019 03:32:14 -0600 Received: from [10.250.133.44] (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id xB69WBdu086266; Fri, 6 Dec 2019 03:32:12 -0600 Subject: Re: [EXT] [PATCH 1/3] mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two To: Ashish Kumar , Tudor Ambarus CC: Miquel Raynal , Richard Weinberger , "linux-mtd@lists.infradead.org" , "linux-kernel@vger.kernel.org" , John Garry References: <20191205065935.5727-1-vigneshr@ti.com> <20191205065935.5727-2-vigneshr@ti.com> From: Vignesh Raghavendra Message-ID: <8a7709b6-215c-939a-906d-0ed7c3c2dbd8@ti.com> Date: Fri, 6 Dec 2019 15:02:10 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/5/2019 12:54 PM, Ashish Kumar wrote: > Hi Vignesh, [...] >> drivers/mtd/spi-nor/spi-nor.c | 9 +++++---- >> 1 file changed, 5 insertions(+), 4 deletions(-) >> >> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c >> index f4afe123e9dc..01efea022990 100644 >> --- a/drivers/mtd/spi-nor/spi-nor.c >> +++ b/drivers/mtd/spi-nor/spi-nor.c >> @@ -2459,15 +2459,16 @@ static const struct flash_info spi_nor_ids[] = { >> { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K | >> SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, >> { "n25q256ax1", INFO(0x20bb19, 0, 64 * 1024, 512, SECT_4K | >> SPI_NOR_QUAD_READ) }, >> { "n25q512ax3", INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | >> SPI_NOR_QUAD_READ) }, >> + { "mt25qu512a", INFO6(0x20bb20, 0x104400, 64 * 1024, 1024, >> + SECT_4K | USE_FSR | SPI_NOR_DUAL_READ | >> + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }, > It seems you have moved back to my original patch [1], wrt mt25qu512a. > Yes, it seems like n25q and mt25q are not really same... mt25q supports stateless 4 byte addressing opcodes where as n25q does not. Hence we cannot add SPI_NOR_4B_OPCODES to n25q's idcodes. This patch is outcome of from U-Boot discussion here (I believe you were cc'd as well): https://patchwork.ozlabs.org/patch/1160501/ Regards Vignesh > Regards > Ashish >> + { "n25q512a", INFO(0x20bb20, 0, 64 * 1024, 1024, SECT_4K | >> + SPI_NOR_QUAD_READ) }, >> { "n25q00", INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | >> SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, >> { "n25q00a", INFO(0x20bb21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | >> SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, >> { "mt25ql02g", INFO(0x20ba22, 0, 64 * 1024, 4096, >> SECT_4K | USE_FSR | SPI_NOR_QUAD_READ | >> NO_CHIP_ERASE) }, >> - { "mt25qu512a (n25q512a)", INFO(0x20bb20, 0, 64 * 1024, 1024, >> - SECT_4K | USE_FSR | SPI_NOR_DUAL_READ | >> - SPI_NOR_QUAD_READ | >> - SPI_NOR_4B_OPCODES) }, >> { "mt25qu02g", INFO(0x20bb22, 0, 64 * 1024, 4096, SECT_4K | USE_FSR | >> SPI_NOR_QUAD_READ | NO_CHIP_ERASE) }, >> >> /* Micron */ >> -- >> 2.24.0 > [1]: http://patchwork.ozlabs.org/patch/1146197/ >