Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4728762ybv; Mon, 17 Feb 2020 04:52:21 -0800 (PST) X-Google-Smtp-Source: APXvYqxamjHF3Sdj+QsIGe/gxZn+YUAC5cvUSKkW3kWNYeB93kgd9MBpPzG6uhmb2SkSbviBRget X-Received: by 2002:a05:6830:1d5b:: with SMTP id p27mr11454765oth.263.1581943941671; Mon, 17 Feb 2020 04:52:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581943941; cv=none; d=google.com; s=arc-20160816; b=uIERLSTp2gQ6OadPLIjAtqJwusmnfID5bORT4b7dtif962QfsZ9dGku6no/GpjvaYL VECJyjTcbeGX4xPmbfGrfjc+tYO/QulGOq2isAbqdOz6Ud//kM1/vQj1Qk+6IRecZWpo 1rRqE4YTK5Akm+k1Yd66K7fHitwQVOPELKli4f6F/L74yn+PXO5Lph8mEb2Dr32Ng6Uz +Jy5wO09jm0Cw/2lUz16mmPWN7ENFlRb2beewnFc153eMyp5GJPGCgI6WIg3fvRGrVxk 5bwksr8fIW9BBcgue7uy8Y1WO+iVuCHe8EFSkD1uktjol6gK6Yc/MhzTr3Hkf89F7G8G UKWg== 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=E3VkN1ikCKZ9GbsHBrahfc8EY2iLwLFkjGpj5EcTql0=; b=wbm3AKZsS5zdS4sIBYfcEwP5tkxRj7WnZvOUroBnf3Wd4tKgmKduxOxAiyF+T7nc9N 7ZWTmIK1DgbhNEajCNvcgB8p/KsC7tRUXHUTRXrmHlJr8CJ2VUz51k/cTVuCOBzT5GFP T6qJfnVw2RiyZXeEdKzLOP21w27XL2rdptrXZLy/kipSPQ0+2SERIuMjf1GThr+NXg99 0EIjxG25MSvppmvHAHyMJzG2v+d3LDTIfkn98eDlYFCQO2tnpEWYlBtCqB/Sj6S0ywJo gJSAV8GP7Hf1I7+mbCGPiedvJtqVSbsqeYC3BePC+VC2lA4b2TuPHYXapH3e8T27QowL 7ubA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=D4GGp8mF; 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 l11si157714otn.189.2020.02.17.04.52.09; Mon, 17 Feb 2020 04:52:21 -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=D4GGp8mF; 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 S1729236AbgBQMRo (ORCPT + 99 others); Mon, 17 Feb 2020 07:17:44 -0500 Received: from lelv0142.ext.ti.com ([198.47.23.249]:50068 "EHLO lelv0142.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726932AbgBQMRo (ORCPT ); Mon, 17 Feb 2020 07:17:44 -0500 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 01HCHSkP023037; Mon, 17 Feb 2020 06:17:28 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1581941848; bh=E3VkN1ikCKZ9GbsHBrahfc8EY2iLwLFkjGpj5EcTql0=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=D4GGp8mF7bV47mlTNJMdLLIl1wbz/lr0QD3RiX/mG5Xqp87SEnZZ3HVsa4jbOT0TR Gq2ffGcqDH2Fz9bV2fUlQx8D79l5WRdVLibFb3I5N8QITj1whA3yqFhEsTkt7GB+RT GXt/ghJOEHG3cxLpeUWDESHxuXb49eVhc6hKCXXs= Received: from DLEE105.ent.ti.com (dlee105.ent.ti.com [157.170.170.35]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 01HCHSRi121007 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 17 Feb 2020 06:17:28 -0600 Received: from DLEE108.ent.ti.com (157.170.170.38) by DLEE105.ent.ti.com (157.170.170.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Mon, 17 Feb 2020 06:17:28 -0600 Received: from fllv0040.itg.ti.com (10.64.41.20) by DLEE108.ent.ti.com (157.170.170.38) 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; Mon, 17 Feb 2020 06:17:28 -0600 Received: from [172.24.145.136] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 01HCHNV2078195; Mon, 17 Feb 2020 06:17:24 -0600 Subject: Re: [PATCH v9 0/2] spi: cadence-quadpsi: Add support for the Cadence QSPI controller To: Mark Brown , "Ramuthevar, Vadivel MuruganX" CC: Simon Goldschmidt , linux-kernel , , Mark Rutland , Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , , , , , References: <20200214114618.29704-1-vadivel.muruganx.ramuthevar@linux.intel.com> <20200214121145.GF4827@sirena.org.uk> <4712cdc4-34cd-990b-3d53-3d394ae1250b@linux.intel.com> <20200217115213.GA9304@sirena.org.uk> From: Vignesh Raghavendra Message-ID: Date: Mon, 17 Feb 2020 17:48:02 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: <20200217115213.GA9304@sirena.org.uk> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 8bit 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 Hi Vadivel, On 17/02/20 5:22 pm, Mark Brown wrote: > On Mon, Feb 17, 2020 at 05:28:38PM +0800, Ramuthevar, Vadivel MuruganX wrote: >> On 14/2/2020 8:11 PM, Mark Brown wrote: > >>> Given that this is a new driver I'd be very surprised if it broke other >>> users? I can imagine it might not work for them and it would definitely >>> be much better to get their review but it shouldn't be any worse than >>> the current lack of support. > >> *[Vignesh]*? The legacy driver under drivers/mtd/spi-nor will be removed as >> we cannot >> support both SPI NOR and SPI NAND with single driver if its under >> spi-nor. New driver should be functionally equivalent to existing one. >> So I suggest you test this driver on legcay SoCFPGA products. > > You're not actually removing the driver here, you're adding another > driver for the same thing. > I agree with Mark here. I realized that you are using same CONFIG option as the old one to build this driver. This causes new driver to fail to probe as old driver would bind to the node instead (both drivers will be built into the kernel and both drivers have same compatible). So, you should remove the old driver. Could you also include patches removing old driver? New driver and bindings are anyways backward compatible with existing one -- Regards Vignesh