Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65969C433F5 for ; Tue, 4 Jan 2022 18:20:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236212AbiADSUe (ORCPT ); Tue, 4 Jan 2022 13:20:34 -0500 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:52555 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236208AbiADSUc (ORCPT ); Tue, 4 Jan 2022 13:20:32 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 6F60B58047C; Tue, 4 Jan 2022 13:20:29 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 04 Jan 2022 13:20:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stwcx.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=nzizLnHIDJLE77dWtL0gicrfFax qw30Dc5elZuFF93g=; b=NaBkrqt8rYn8R2HOjWvwZ8OGokiJNs/NYZ021cHzQhG MM4BVbxMYaYSGv8FiTSQF1FZkWenPDu/Wi6nYywU/gGqxppZZ5Ps7w8R5JDfwLsb oFkEZ0JutReD+E3byu180IYKBvU2N5wGlHsUNStxWGyfliIXTCC2rEum4ThGOntn D3gb/hXHhkzaFmMqncOajpS9tdGCB5d8NxsvmaROrj6Seci04C8vhw2QrWuc5sB+ CbjO7r1BTXVhOxDDJpzbpSZ52nF70ClOWgO1HziZt1gUzN6yj7/+pvzm41HKY8Dv h1B0WZlutBicN0XEEOsWqO9zyFQHU+Ry1hTP9OcmjEQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=nzizLn HIDJLE77dWtL0gicrfFaxqw30Dc5elZuFF93g=; b=UUeHByumxn11Uyq3tcYTjY Zk85hhI2yLQNfcA/jemzA86Tzm8+/9HM4r0oGWW1pIEeJ/lfU1XHWVqQTf/VTa2V rM1Iir5vPaPZHtii8CFp2wk+mZEz8YiAjK/I8jzGBMcZw/38WvoyRTnMf2ofDetD aYxdZILKOEoVt1YsdpTXdzUnCVR7A/Y2LHDxOghmLNQsZqgBf26AaY3c6EHORqlw 6cxLlZ77JlWoQ8T6tNVmaiZrBVrmva40XwH5bFdTXOfLb5WRozc5y5XLaTefc9te HQKFi6xblrvuOwbXVhlKytgYuAti0yUMEdpNP7SmCNRNQ71YZ7Q6UFxVLgXypB5Q == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudeffedgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enfghrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefrrghtrhhitghkucghihhllhhirghmshcuoehprghtrhhitghkse hsthiftgigrdighiiiqeenucggtffrrghtthgvrhhnpeegheehfeffgeekveehtdfhgfdu hfegfefgtdehhfektdelffevkefgueffhedtieenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehprghtrhhitghksehsthiftgigrdighiii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 4 Jan 2022 13:20:27 -0500 (EST) Date: Tue, 4 Jan 2022 12:20:26 -0600 From: Patrick Williams To: Miquel Raynal Cc: Pratyush Yadav , Joel Stanley , Tudor Ambarus , Michael Walle , Richard Weinberger , Vignesh Raghavendra , Andrew Jeffery , Potin Lai , linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mtd: aspeed-smc: improve probe resilience Message-ID: References: <20211229143334.297305-1-patrick@stwcx.xyz> <20211229173411.l2bipmi4x3arqjoo@ti.com> <20211231102623.izaqlzjvracbbgmp@ti.com> <20220103171721.46c8e697@xps13> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4uGk4mNj2n7MOyWq" Content-Disposition: inline In-Reply-To: <20220103171721.46c8e697@xps13> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --4uGk4mNj2n7MOyWq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Miquel, On Mon, Jan 03, 2022 at 05:17:21PM +0100, Miquel Raynal wrote: > > I am fine with taking in bug fixes but no longer want to take in any ne= w=20 > > features. My main intention was to nudge you to convert it to SPI MEM= =20 > > regardless of whether this is a bug fix or a new feature, because=20 > > eventually we want to get rid of drivers/mtd/spi-nor/controllers/ and= =20 > > the API that comes along with it. >=20 > I totally agree with Pratyush here, we no longer want to support the > spi-nor controller API so if, as you say, there are boards failing > in the field, it means there are still users and these users must be > warned that at some point we might discontinue the support of these > drivers if it becomes too painful. > Your response here makes it seem like you don't realize the scope of this driver. There are probably, by my estimates, on the order of 10s of millio= ns of deployed systems using this driver in the world. The vast majority of serv= ers in the world use an AST2400, AST2500, or AST2600 chip, which needs this dri= ver in order access its own flash storage device. Both OpenBMC and most of the proprietary alternatives use this driver. The company I work for has a LOT of systems using this code. After I made = this fix, for a new design being developed, it was pointed out to me that our OD= M ran into this problem a few years ago and we've been really bad about upstreami= ng those fixes. For this new system I'm trying to keep us on top of all upstreaming efforts. To me the inability to access your own storage, resulting in a kernel panic= , is a pretty serious issue. Bug or feature I guess is always in the eye of the beholder though. I think this is pretty valuable to get in, from an impact standpoint, and pretty minimal in terms of maintenance efforts on the maintainers part. I had an offline discussion with someone who knew more history on this driv= er. My understanding is that the linux-aspeed team is aware of this being depre= cated but that there was some missing support for interface training that nobody = has gotten around to write? If that is the case this really isn't even a "simp= le" port to a new API at this point. --=20 Patrick Williams --4uGk4mNj2n7MOyWq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEBGD9ii4LE9cNbqJBqwNHzC0AwRkFAmHUj+gACgkQqwNHzC0A wRkIcBAAkolp24FJ1nPPX2egEXt6f48Kvsbrft91uSjMBg4RfefxO0fmpFDGNZFr edf5GnNtwVGM5sXAUKN5MixoKpb/fPN4ivCyBS7GixnoNxwc76pgOfhnGsSKCkrO SoRrdNWyOswuGzi5yBeGSUdcHRaVsTSSl5YdssCLfDvza1KrtVnKXnHJUaI4EB3o JB/zEh2p5C+TnOdR0ADhw6DuvFRb5mGq/XV2AfK4OGBDU/EoWE3m15zWCE5Wdu5d RjE6KooRKsGFR6NDw3yg8B3LZVEjLx/ehe9FZSJLn3jHQEeIXGbiulsrGQAIe7rN K3v04ZK+41Vx2NcavLKH8cCr4mtJ6jQbtQ0ups/EPuY8TLctc8sW27KGol/OJ4WU t6tAba0EfkGxa4GOy73fBZDzfax+Yr86G86xL1q1wiqnLiO2yGyyrrwJNj2KmkO8 uCzI+oStA4EE8lpUgZYHNVmeyc1cU6G1+bnG+0ekVeKcHZqixCGyBfHGNHpmMpkO p7YxULRCnX8GQwry+Ws1Iskk8e0MMVIRKLH7LAT7okT+TWVHsplnGL9binqqLpQ8 KLWR7QAEQBdNXi3XAwv8W6mfeeJ2sdG2WGZLUrabY3be9VwrbMLkCkT+smISoTtb Y0ALpgxI9OZzHfwpXWpkW3ecNdVf9AIARnceoSukBWZdrgmwDBU= =lc+5 -----END PGP SIGNATURE----- --4uGk4mNj2n7MOyWq--