From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 17 Apr 2014 13:23:57 +0200 (CEST) Received: from mail-out.m-online.net ([212.18.0.9]:53424 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S6834698AbaDQLXzXdGk5 (ORCPT ); Thu, 17 Apr 2014 13:23:55 +0200 Received: from frontend1.mail.m-online.net (unknown [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id 3g8dNj0nGZz4KK4F; Thu, 17 Apr 2014 13:23:48 +0200 (CEST) X-Auth-Info: yvl9lennTYmo+vFVGEajPQ7NwMAdHkSsvBu09lrL1oQ= Received: from chi.localnet (unknown [195.140.253.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-auth.mnet-online.de (Postfix) with ESMTPSA id 3g8dNh5lbBzbbl2; Thu, 17 Apr 2014 13:23:48 +0200 (CEST) From: Marek Vasut To: Brian Norris Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Date: Thu, 17 Apr 2014 13:07:44 +0200 User-Agent: KMail/1.13.7 (Linux/3.13-trunk-amd64; KDE/4.11.3; x86_64; ; ) Cc: Linux Kernel , linux-mtd@lists.infradead.org, Russell King , Shawn Guo , Sascha Hauer , Stephen Warren , Thierry Reding , Olof Johansson , linux-arm-kernel@lists.infradead.org, linux-tegra@vger.kernel.org, Steven Miao , adi-buildroot-devel@lists.sourceforge.net, Ralf Baechle , linux-mips@linux-mips.org, Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org References: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201404171307.44214.marex@denx.de> Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 39850 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: marex@denx.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote: > Hi all, > > We are introducing a new SPI-NOR library/framework for MTD, to support > various types of SPI-NOR flash controllers which require (or benefit from) > intimate knowledge of the flash interface, rather than just the relatively > dumb SPI interface. This library borrows much of the m25p80 driver for its > abstraction and moves this code into a spi-nor module. > > This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which > should be added to the defconfigs. I'm not sure what is the best process > for doing this. Should each $ARCH maintainer just take their respective > patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet? > Or should maintainers plan on merging the relevant SPI-NOR code into their > trees during the development cycle? Or some third option? Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't need the adjustment to defconfigs at all I think. Best regards, Marek Vasut From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut To: Brian Norris Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Date: Thu, 17 Apr 2014 13:07:44 +0200 References: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201404171307.44214.marex@denx.de> Cc: linux-mips@linux-mips.org, Russell King , Stephen Warren , linux-sh@vger.kernel.org, Benjamin Herrenschmidt , Steven Miao , Linux Kernel , Ralf Baechle , adi-buildroot-devel@lists.sourceforge.net, linux-tegra@vger.kernel.org, Thierry Reding , linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Sascha Hauer , Olof Johansson , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, Shawn Guo List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote: > Hi all, > > We are introducing a new SPI-NOR library/framework for MTD, to support > various types of SPI-NOR flash controllers which require (or benefit from) > intimate knowledge of the flash interface, rather than just the relatively > dumb SPI interface. This library borrows much of the m25p80 driver for its > abstraction and moves this code into a spi-nor module. > > This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which > should be added to the defconfigs. I'm not sure what is the best process > for doing this. Should each $ARCH maintainer just take their respective > patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet? > Or should maintainers plan on merging the relevant SPI-NOR code into their > trees during the development cycle? Or some third option? Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't need the adjustment to defconfigs at all I think. Best regards, Marek Vasut From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 17 Apr 2014 11:07:44 +0000 Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Message-Id: <201404171307.44214.marex@denx.de> List-Id: References: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-arm-kernel@lists.infradead.org On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote: > Hi all, > > We are introducing a new SPI-NOR library/framework for MTD, to support > various types of SPI-NOR flash controllers which require (or benefit from) > intimate knowledge of the flash interface, rather than just the relatively > dumb SPI interface. This library borrows much of the m25p80 driver for its > abstraction and moves this code into a spi-nor module. > > This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which > should be added to the defconfigs. I'm not sure what is the best process > for doing this. Should each $ARCH maintainer just take their respective > patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet? > Or should maintainers plan on merging the relevant SPI-NOR code into their > trees during the development cycle? Or some third option? Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't need the adjustment to defconfigs at all I think. Best regards, Marek Vasut From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 5EE69140099 for ; Thu, 17 Apr 2014 21:30:26 +1000 (EST) From: Marek Vasut To: Brian Norris Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Date: Thu, 17 Apr 2014 13:07:44 +0200 References: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Message-Id: <201404171307.44214.marex@denx.de> Cc: linux-mips@linux-mips.org, Russell King , Stephen Warren , linux-sh@vger.kernel.org, Steven Miao , Linux Kernel , Ralf Baechle , adi-buildroot-devel@lists.sourceforge.net, linux-tegra@vger.kernel.org, Thierry Reding , linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Sascha Hauer , Olof Johansson , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, Shawn Guo List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote: > Hi all, > > We are introducing a new SPI-NOR library/framework for MTD, to support > various types of SPI-NOR flash controllers which require (or benefit from) > intimate knowledge of the flash interface, rather than just the relatively > dumb SPI interface. This library borrows much of the m25p80 driver for its > abstraction and moves this code into a spi-nor module. > > This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which > should be added to the defconfigs. I'm not sure what is the best process > for doing this. Should each $ARCH maintainer just take their respective > patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet? > Or should maintainers plan on merging the relevant SPI-NOR code into their > trees during the development cycle? Or some third option? Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't need the adjustment to defconfigs at all I think. Best regards, Marek Vasut From mboxrd@z Thu Jan 1 00:00:00 1970 From: marex@denx.de (Marek Vasut) Date: Thu, 17 Apr 2014 13:07:44 +0200 Subject: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> References: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com> Message-ID: <201404171307.44214.marex@denx.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote: > Hi all, > > We are introducing a new SPI-NOR library/framework for MTD, to support > various types of SPI-NOR flash controllers which require (or benefit from) > intimate knowledge of the flash interface, rather than just the relatively > dumb SPI interface. This library borrows much of the m25p80 driver for its > abstraction and moves this code into a spi-nor module. > > This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which > should be added to the defconfigs. I'm not sure what is the best process > for doing this. Should each $ARCH maintainer just take their respective > patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet? > Or should maintainers plan on merging the relevant SPI-NOR code into their > trees during the development cycle? Or some third option? Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't need the adjustment to defconfigs at all I think. Best regards, Marek Vasut