linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Walle" <michael@walle.cc>
To: "Michal Simek" <michal.simek@amd.com>,
	"Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd.com>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"pratyush@kernel.org" <pratyush@kernel.org>,
	"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
	"richard@nod.at" <richard@nod.at>,
	"vigneshr@ti.com" <vigneshr@ti.com>,
	"sbinding@opensource.cirrus.com" <sbinding@opensource.cirrus.com>,
	"lee@kernel.org" <lee@kernel.org>,
	"james.schulman@cirrus.com" <james.schulman@cirrus.com>,
	"david.rhodes@cirrus.com" <david.rhodes@cirrus.com>,
	"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
	"perex@perex.cz" <perex@perex.cz>,
	"tiwai@suse.com" <tiwai@suse.com>
Cc: "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"git (AMD-Xilinx)" <git@amd.com>,
	"amitrkcian2002@gmail.com" <amitrkcian2002@gmail.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: [PATCH v11 07/10] mtd: spi-nor: Add stacked memories support in spi-nor
Date: Wed, 31 Jul 2024 11:19:01 +0200	[thread overview]
Message-ID: <D33M26RLVLHF.3Q5YARPBNSBOY@walle.cc> (raw)
In-Reply-To: <e1587f61-f765-4a22-b06e-71387cc49c4d@amd.com>

[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]

Hi Michal,

> >> Based on the inputs/suggestions from Tudor, i am planning to add a new
> >> layer between the SPI-NOR and MTD layers to support stacked and parallel
> >> configurations. This new layer will be part of the spi-nor and located in
> >> mtd/spi-nor/
> > 
> > Will AMD submit to maintain this layer? What happens if the
> > maintainer will leave AMD? TBH, personally, I don't like to
> > maintain such a niche feature.
> > I'd really like to see some use cases and performance reports for
> > this, like actual boards (and no evaluation boards don't count). Why
> > wouldn't someone just use an octal flash?
>
> AMD/Xilinx is not creating products that's why we don't have data on actual 
> boards but I don't really understand why evaluation boards don't count.

Because on an eval board the vendor just puts everything possible on
the board.

> A lot of 
> customers are taking schematics from us and removing parts which they don't need 
> and add their custom part.
>
> But one product for parallel configuration which is publicly saying that it is 
> using it is for example this SOM.
> https://shop.trenz-electronic.de/en/TE0820-05-2AI21MA-MPSoC-Module-with-AMD-Zynq-UltraScale-ZU2CG-1I-2-GByte-DDR4-SDRAM-4-x-5-cm
>
> I am not marketing guy to tell if there is any other which publicly saying we 
> are using this feature but we can only develop/support/maintain support for 
> these configurations on our evaluation boards because that's what we have access 
> to and what we know how it is done.
>
> Also performance numbers from us can be only provided against our evaluation boards.

Which is good enough.

All I'm saying is that you shouldn't put burden on us (the SPI NOR
maintainers) for what seems to me at least as a niche. Thus I was
asking for performance numbers and users. Convince me that I'm
wrong and that is worth our time.

The first round of patches were really invasive regarding the core
code. So if there is a clean layering approach which can be enabled
as a module and you are maintaining it I'm fine with that (even if
the core code needs some changes then like hooks or so, not sure).

-michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

  reply	other threads:[~2024-07-31  9:19 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  9:21 [PATCH v11 00/10] spi: Add support for stacked/parallel memories Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 01/10] mfd: tps6594: Use set/get APIs to access spi->chip_select Amit Kumar Mahapatra
2023-12-01  9:57   ` (subset) " Lee Jones
2023-12-01 18:50     ` Mark Brown
2023-12-06 13:45       ` Lee Jones
2023-12-07 13:38       ` [GIT PULL] Immutable branch between MFD and SPI due for the v6.8 merge window Lee Jones
2023-12-07 16:20         ` Mark Brown
2023-11-25  9:21 ` [PATCH v11 02/10] ALSA: hda/cs35l56: Use set/get APIs to access spi->chip_select Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 03/10] spi: Add multi-cs memories support in SPI core Amit Kumar Mahapatra
2024-01-12 19:11   ` Guenter Roeck
2024-01-12 19:16     ` Mark Brown
2024-01-12 20:05       ` Guenter Roeck
2024-01-20 17:05     ` Guenter Roeck
2024-01-21  1:04       ` Mark Brown
2024-01-21 16:58         ` Guenter Roeck
2024-01-21 18:06           ` Michael Walle
2024-01-21 19:29             ` Guenter Roeck
2024-01-21 21:17               ` Mark Brown
2024-01-21 21:15             ` Mark Brown
2024-01-21  9:42     ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-23 15:45       ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-25  9:21 ` [PATCH v11 04/10] mtd: spi-nor: Convert macros with inline functions Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 05/10] mtd: spi-nor: Add APIs to set/get nor->params Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 06/10] mtd: spi-nor: Move write enable inside specific write & erase APIs Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 07/10] mtd: spi-nor: Add stacked memories support in spi-nor Amit Kumar Mahapatra
2023-12-06 14:30   ` Tudor Ambarus
2023-12-06 14:43     ` Tudor Ambarus
2023-12-08 17:06       ` Mahapatra, Amit Kumar
2023-12-11  3:44         ` Tudor Ambarus
2023-12-08 17:05     ` Mahapatra, Amit Kumar
2023-12-11  3:33       ` Tudor Ambarus
2023-12-11  6:56         ` Mahapatra, Amit Kumar
2023-12-11  9:35           ` Tudor Ambarus
2023-12-11 13:37             ` Mahapatra, Amit Kumar
2023-12-12 15:02               ` Tudor Ambarus
2023-12-15  7:55                 ` Mahapatra, Amit Kumar
2023-12-15  8:09                   ` Tudor Ambarus
2023-12-15 10:02                     ` Mahapatra, Amit Kumar
2023-12-15 10:33                       ` Tudor Ambarus
2023-12-15 11:20                         ` Mahapatra, Amit Kumar
2023-12-19  8:26                           ` Tudor Ambarus
2023-12-21  6:54                             ` Mahapatra, Amit Kumar
2024-02-09 11:06                               ` Tudor Ambarus
2024-02-09 16:13                                 ` Tudor Ambarus
2024-03-13 16:03                                   ` Mahapatra, Amit Kumar
2024-07-26 12:35                                     ` Mahapatra, Amit Kumar
     [not found]                                       ` < <IA0PR12MB769944254171C39FF4171B52DCB42@IA0PR12MB7699.namprd12.prod.outlook.com>
2024-07-26 12:55                                         ` Michael Walle
2024-07-31  8:58                                           ` Michal Simek
2024-07-31  9:19                                             ` Michael Walle [this message]
2024-07-31 13:40                                               ` Michal Simek
2024-07-31 14:11                                                 ` Michael Walle
2024-08-01  6:22                                                   ` Michal Simek
2024-08-01  6:37                                                     ` Frager, Neal
2024-08-01  9:28                                                       ` Mahapatra, Amit Kumar
     [not found]                                                       ` < <CH2PR12MB50044242FE253D7B0E3425ABF0B22@CH2PR12MB5004.namprd12.prod.outlook.com>
2024-08-05  8:14                                                         ` Michael Walle
2024-08-05  8:27                                                     ` Michael Walle
2024-08-05 11:00                                                       ` Michal Simek
2024-08-07 13:21                                                         ` Mahapatra, Amit Kumar
2024-08-12  7:29                                                   ` Miquel Raynal
2024-08-12  7:37                                                     ` Michael Walle
2024-08-12  8:39                                                       ` Miquel Raynal
2024-08-12  8:38                                       ` Miquel Raynal
2024-08-12  9:45                                         ` Tudor Ambarus
2024-08-14  7:13                                         ` Mahapatra, Amit Kumar
2024-08-14  8:46                                           ` Miquel Raynal
2024-08-14 12:53                                             ` Mahapatra, Amit Kumar
2024-08-14 14:46                                               ` Miquel Raynal
2024-08-19 10:28                                                 ` Mahapatra, Amit Kumar
2024-03-13 16:03                                 ` Mahapatra, Amit Kumar
2023-12-07 17:24   ` Tudor Ambarus
2023-11-25  9:21 ` [PATCH v11 08/10] spi: spi-zynqmp-gqspi: Add stacked memories support in GQSPI driver Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 09/10] mtd: spi-nor: Add parallel memories support in spi-nor Amit Kumar Mahapatra
2023-11-25  9:21 ` [PATCH v11 10/10] spi: spi-zynqmp-gqspi: Add parallel memories support in GQSPI driver Amit Kumar Mahapatra
2023-12-07 22:35 ` (subset) [PATCH v11 00/10] spi: Add support for stacked/parallel memories Mark Brown
2023-12-12 12:34 ` Michael Walle
2023-12-15  7:28   ` Mahapatra, Amit Kumar
2023-12-18 22:10 ` Richard Weinberger
2023-12-19  8:12   ` Miquel Raynal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D33M26RLVLHF.3Q5YARPBNSBOY@walle.cc \
    --to=michael@walle.cc \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amit.kumar-mahapatra@amd.com \
    --cc=amitrkcian2002@gmail.com \
    --cc=beanhuo@micron.com \
    --cc=broonie@kernel.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor.dooley@microchip.com \
    --cc=david.rhodes@cirrus.com \
    --cc=git@amd.com \
    --cc=james.schulman@cirrus.com \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=pratyush@kernel.org \
    --cc=rf@opensource.cirrus.com \
    --cc=richard@nod.at \
    --cc=sbinding@opensource.cirrus.com \
    --cc=tiwai@suse.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).