Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7017005imu; Mon, 3 Dec 2018 06:31:41 -0800 (PST) X-Google-Smtp-Source: AFSGD/VMt7wS+BiBEd7emUUQrUw7NMB1zfD/F6CEe35MM0wrT8j2sHzm0WRJ4I7enazkQO7dG9QZ X-Received: by 2002:a62:6d84:: with SMTP id i126mr15785103pfc.109.1543847501118; Mon, 03 Dec 2018 06:31:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543847501; cv=none; d=google.com; s=arc-20160816; b=thjrHWkYcPwuVg1PwxdBfB8e0mNSsB3QUbRG5pbXUMbpuAK5G3xXtQ+q0FClSVbfKB F2c+HLdqALBFfXmBfPkRJY1jUhZRG2YzMGFNG3MmeN/eNpv057YV0z3yEqX6zvNECHb5 YF/kol+xgUL8gPiog8Byk321M2IZCvJZ8YKSnUXPt4qyjMIA5Kl1Ndj1O9HmuLVMQvMI Kx21tc0FDqggcWosVtSsp5+ZjB9FJdfLU1QXj5KJ0mYhltuZ6Q8HAoHLGw4trGj+8SFl w0S9sVQqf1iYal7dAuXIvwG30a/a/7Rusqdvopm9wbJu8evWYfy+/AHiUdnESiQMz9gf IyGA== 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=SI12vGXaDiKH8xmeC9p11YAqRZXKvsUcPDPAoVvql60=; b=g5VpR8o4RCSiiCQEtFnc1lrEZNoIzn473RDwNiXC8YRE/lWjToBny7BqZAxbDdoMFJ r7f9PuJf5TEdgFCXuNKkgcvzZ0lheFj4Xcsh+1lNdsKi6YjUaYLVGv2M/ujJyMeM6BOP YxK7TvNBVnot+1PoKeAOi2sRDqcBa9xSmTP6Q2DUWeQ4CJNBQbRY9tssKRDfK+eUwLoL AR6UAxFwldf3yCjIBKutZZiFOG2Pd5MI0Ii+yufp1JS/TMKLp2vRFSEBL2gzEoQ7ZfXb UNIKEzlkIzHCW3xr56rNkmSRVqWXi5WOvQl0PdMVIiN5VJHu8x6SlUJET+tzXMXy9YGi aSnQ== 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 f7si12970165pga.87.2018.12.03.06.31.25; Mon, 03 Dec 2018 06:31:41 -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; 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 S1726457AbeLCOcD (ORCPT + 99 others); Mon, 3 Dec 2018 09:32:03 -0500 Received: from mail.bootlin.com ([62.4.15.54]:39911 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725917AbeLCOcC (ORCPT ); Mon, 3 Dec 2018 09:32:02 -0500 Received: by mail.bootlin.com (Postfix, from userid 110) id 3171B2071D; Mon, 3 Dec 2018 15:30:47 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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.2 Received: from bbrezillon (aaubervilliers-681-1-63-158.w90-88.abo.wanadoo.fr [90.88.18.158]) by mail.bootlin.com (Postfix) with ESMTPSA id B7DCF20618; Mon, 3 Dec 2018 15:30:46 +0100 (CET) Date: Mon, 3 Dec 2018 15:30:46 +0100 From: Boris Brezillon To: Tomer Maimon Cc: David Woodhouse , computersforpeace@gmail.com, marek.vasut@gmail.com, richard@nod.at, Rob Herring , Mark Rutland , Nancy Yuen , Patrick Venture , Brendan Higgins , Avi Fishman , Joel Stanley , linux-mtd@lists.infradead.org, OpenBMC Maillist , Linux Kernel Mailing List , devicetree Subject: Re: [PATCH v1 0/2] SPI-NOR add NPCM FIU controller driver Message-ID: <20181203153046.0554854f@bbrezillon> In-Reply-To: References: <20181203091456.454030-1-tmaimon77@gmail.com> <20181203102240.79a86a26@bbrezillon> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; 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 Hi Tomer; On Mon, 3 Dec 2018 16:09:19 +0200 Tomer Maimon wrote: > A few comments/input: > > > 1. We have been working on this driver for quite a long time to port it > to the latest Linux conventions, polish the code, run tests and reach high > quality. > Our partners and customers are waiting to get this driver upstream so > they can freely use it. Your patch prefix says "v1", so I'm assuming this is the first public version. I'm sure you spent a lot of time developing this driver internally, but no matter how long it took, it's a first version for us, and since we are moving away from the spi_nor controller interface, I'm not willing to accept new drivers using this interface. If you want more background about the spi_nor controller interface deprecation, you can read [1]. > Since this driver is already in final stages and is in very good shape > we will appreciate if you can review this specific driver/interface and > help us to upstream it. Actually, I'd like to do it the other way around: let you rework the driver to implement the spi-mem interface and review this version. Otherwise I'll be reviewing things I don't intend to merge anyway. > 2. As for the new interface, we are open for any discussion and for > porting the driver as required. > We are unsure what is this specific interface and weather it really fits > a driver for a Flash Interface Controller module (rather than a SPI flash > device). Didn't go through the code in details, but at first glance, it looks like it would fit pretty well. > Is it possible to get a sample driver from another Flash Interface > Controller module that was ported to this new interface ? We recently converted the atmel QSPI driver [2]. Regards, Boris [1]https://bootlin.com/blog/spi-mem-bringing-some-consistency-to-the-spi-memory-ecosystem/ [2]https://patchwork.kernel.org/project/spi-devel-general/list/?series=38347&state=*