From: Michael Walle <michael@walle.cc> To: Tudor Ambarus <tudor.ambarus@microchip.com> Cc: sr@denx.de, vigneshr@ti.com, jaimeliao@mxic.com.tw, richard@nod.at, esben@geanix.com, linux@rasmusvillemoes.dk, knaerzche@gmail.com, nicolas.ferre@microchip.com, linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, macromorgan@hotmail.com, miquel.raynal@bootlin.com, heiko.thiery@gmail.com, zhengxunli@mxic.com.tw, p.yadav@ti.com, mail@david-bauer.net, code@reto-schneider.ch Subject: Re: [PATCH v4 6/6] mtd: spi-nor: manuf-id-collisions: Add support for xt25f128b Date: Tue, 01 Mar 2022 23:23:24 +0100 [thread overview] Message-ID: <1a05176e6e2457c1b86035522c3f691b@walle.cc> (raw) In-Reply-To: <20220228134505.203270-7-tudor.ambarus@microchip.com> Am 2022-02-28 14:45, schrieb Tudor Ambarus: > Flash does not support continuation codes and may collide with a flash > of other manufacturer, Intersil being an example. Add support for > xt25f128b. > > Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com> > --- > 0000000 4653 5044 0100 ff01 0000 0901 0030 ff00 > 0000010 000b 0301 0060 ff00 ffff ffff ffff ffff > 0000020 ffff ffff ffff ffff ffff ffff ffff ffff > 0000030 20e5 fff1 ffff 07ff eb44 6b08 3b08 bb42 > 0000040 ffee ffff ffff ff00 ffff ff00 200c 520f > 0000050 d810 ff00 ffff ffff ffff ffff ffff ffff > 0000060 3600 2700 f99f 6477 e8d9 ffff You don't have this flash no? because the md5sum is missing. > > drivers/mtd/spi-nor/manuf-id-collisions.c | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/drivers/mtd/spi-nor/manuf-id-collisions.c > b/drivers/mtd/spi-nor/manuf-id-collisions.c > index 75c5ad6480ee..0447e245f4b1 100644 > --- a/drivers/mtd/spi-nor/manuf-id-collisions.c > +++ b/drivers/mtd/spi-nor/manuf-id-collisions.c > @@ -17,6 +17,15 @@ static const struct spi_nor_fixups boya_nor_fixups = > { > .late_init = boya_nor_late_init, > }; > > +static void xtx_nor_late_init(struct spi_nor *nor) > +{ > + nor->manufacturer_name = "xtx"; > +} > + > +static const struct spi_nor_fixups xtx_nor_fixups = { > + .late_init = xtx_nor_late_init, > +}; > + > static const struct flash_info id_collision_parts[] = { > /* Boya */ > { "by25q128as", INFO(0x684018, 0, 64 * 1024, 256) > @@ -24,6 +33,11 @@ static const struct flash_info id_collision_parts[] > = { > NO_SFDP_FLAGS(SPI_NOR_SKIP_SFDP | SECT_4K | SPI_NOR_DUAL_READ | > SPI_NOR_QUAD_READ) > .fixups = &boya_nor_fixups }, > + > + /* XTX (XTX Technology Limited) */ > + { "xt25f128b", INFO(0x0b4018, 0, 64 * 1024, 256) > + PARSE_SFDP > + .fixups = &xtx_nor_fixups }, I'd suggest to order the entries by the id to make it easier to spot collisions. -michael ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc> To: Tudor Ambarus <tudor.ambarus@microchip.com> Cc: sr@denx.de, vigneshr@ti.com, jaimeliao@mxic.com.tw, richard@nod.at, esben@geanix.com, linux@rasmusvillemoes.dk, knaerzche@gmail.com, linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, macromorgan@hotmail.com, miquel.raynal@bootlin.com, heiko.thiery@gmail.com, zhengxunli@mxic.com.tw, figgyc@figgyc.uk, p.yadav@ti.com, mail@david-bauer.net, code@reto-schneider.ch Subject: Re: [PATCH v4 6/6] mtd: spi-nor: manuf-id-collisions: Add support for xt25f128b Date: Tue, 01 Mar 2022 23:23:24 +0100 [thread overview] Message-ID: <1a05176e6e2457c1b86035522c3f691b@walle.cc> (raw) In-Reply-To: <20220228134505.203270-7-tudor.ambarus@microchip.com> Am 2022-02-28 14:45, schrieb Tudor Ambarus: > Flash does not support continuation codes and may collide with a flash > of other manufacturer, Intersil being an example. Add support for > xt25f128b. > > Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com> > --- > 0000000 4653 5044 0100 ff01 0000 0901 0030 ff00 > 0000010 000b 0301 0060 ff00 ffff ffff ffff ffff > 0000020 ffff ffff ffff ffff ffff ffff ffff ffff > 0000030 20e5 fff1 ffff 07ff eb44 6b08 3b08 bb42 > 0000040 ffee ffff ffff ff00 ffff ff00 200c 520f > 0000050 d810 ff00 ffff ffff ffff ffff ffff ffff > 0000060 3600 2700 f99f 6477 e8d9 ffff You don't have this flash no? because the md5sum is missing. > > drivers/mtd/spi-nor/manuf-id-collisions.c | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/drivers/mtd/spi-nor/manuf-id-collisions.c > b/drivers/mtd/spi-nor/manuf-id-collisions.c > index 75c5ad6480ee..0447e245f4b1 100644 > --- a/drivers/mtd/spi-nor/manuf-id-collisions.c > +++ b/drivers/mtd/spi-nor/manuf-id-collisions.c > @@ -17,6 +17,15 @@ static const struct spi_nor_fixups boya_nor_fixups = > { > .late_init = boya_nor_late_init, > }; > > +static void xtx_nor_late_init(struct spi_nor *nor) > +{ > + nor->manufacturer_name = "xtx"; > +} > + > +static const struct spi_nor_fixups xtx_nor_fixups = { > + .late_init = xtx_nor_late_init, > +}; > + > static const struct flash_info id_collision_parts[] = { > /* Boya */ > { "by25q128as", INFO(0x684018, 0, 64 * 1024, 256) > @@ -24,6 +33,11 @@ static const struct flash_info id_collision_parts[] > = { > NO_SFDP_FLAGS(SPI_NOR_SKIP_SFDP | SECT_4K | SPI_NOR_DUAL_READ | > SPI_NOR_QUAD_READ) > .fixups = &boya_nor_fixups }, > + > + /* XTX (XTX Technology Limited) */ > + { "xt25f128b", INFO(0x0b4018, 0, 64 * 1024, 256) > + PARSE_SFDP > + .fixups = &xtx_nor_fixups }, I'd suggest to order the entries by the id to make it easier to spot collisions. -michael _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-01 22:24 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 13:44 [PATCH v4 0/6] mtd: spi-nor: Handle ID collisions Tudor Ambarus 2022-02-28 13:44 ` Tudor Ambarus 2022-02-28 13:45 ` [PATCH v4 1/6] mtd: spi-nor: core: Report correct name in case of " Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 21:38 ` Michael Walle 2022-03-01 21:38 ` Michael Walle 2022-04-05 19:41 ` Pratyush Yadav 2022-04-05 19:41 ` Pratyush Yadav 2022-02-28 13:45 ` [PATCH v4 2/6] mtd: spi-nor: core: Handle ID collisions between SFDP & non-SFDP flashes Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 21:52 ` Michael Walle 2022-03-01 21:52 ` Michael Walle 2022-03-03 14:41 ` Tudor.Ambarus 2022-03-03 14:41 ` Tudor.Ambarus 2022-03-03 14:51 ` Michael Walle 2022-03-03 14:51 ` Michael Walle 2022-03-03 15:25 ` Tudor.Ambarus 2022-03-03 15:25 ` Tudor.Ambarus 2022-03-03 15:42 ` Michael Walle 2022-03-03 15:42 ` Michael Walle 2022-03-03 16:03 ` Tudor.Ambarus 2022-03-03 16:03 ` Tudor.Ambarus 2022-03-03 16:39 ` Michael Walle 2022-03-03 16:39 ` Michael Walle 2022-02-28 13:45 ` [PATCH v4 3/6] mtd: spi-nor: macronix: Handle ID collision b/w MX25L3233F and MX25L3205D Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 21:57 ` Michael Walle 2022-03-01 21:57 ` Michael Walle 2022-03-03 15:28 ` Tudor.Ambarus 2022-03-03 15:28 ` Tudor.Ambarus 2022-03-03 15:33 ` Michael Walle 2022-03-03 15:33 ` Michael Walle [not found] ` <CAEyMn7aN+wJnYkTJU_nWA9bPzF1sezA9_=E5YG5rnPBLMAmabA@mail.gmail.com> 2022-03-03 16:45 ` Michael Walle 2022-03-03 16:45 ` Michael Walle 2022-03-04 0:36 ` Tudor.Ambarus 2022-03-04 0:36 ` Tudor.Ambarus 2022-03-04 14:36 ` Michael Walle 2022-03-04 14:36 ` Michael Walle 2022-04-05 19:50 ` Pratyush Yadav 2022-04-05 19:50 ` Pratyush Yadav 2022-02-28 13:45 ` [PATCH v4 4/6] mtd: spi-nor: macronix: Handle ID collision b/w MX25L12805D and MX25L12835F Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 7:55 ` Heiko Thiery 2022-03-01 7:55 ` Heiko Thiery 2022-03-01 8:52 ` Tudor.Ambarus 2022-03-01 8:52 ` Tudor.Ambarus 2022-03-01 9:31 ` Heiko Thiery 2022-03-01 9:31 ` Heiko Thiery 2022-02-28 13:45 ` [PATCH v4 5/6] mtd: spi-nor: Introduce Manufacturer ID collisions driver Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 22:19 ` Michael Walle 2022-03-01 22:19 ` Michael Walle 2022-03-03 16:12 ` Tudor.Ambarus 2022-03-03 16:12 ` Tudor.Ambarus 2022-03-03 21:38 ` Michael Walle 2022-03-03 21:38 ` Michael Walle 2022-03-04 7:07 ` Tudor.Ambarus 2022-03-04 7:07 ` Tudor.Ambarus 2022-03-04 14:10 ` Michael Walle 2022-03-04 14:10 ` Michael Walle 2022-03-04 21:20 ` George Brooke 2022-03-04 21:20 ` George Brooke 2022-03-07 7:07 ` Tudor.Ambarus 2022-03-07 7:07 ` Tudor.Ambarus 2022-02-28 13:45 ` [PATCH v4 6/6] mtd: spi-nor: manuf-id-collisions: Add support for xt25f128b Tudor Ambarus 2022-02-28 13:45 ` Tudor Ambarus 2022-03-01 22:23 ` Michael Walle [this message] 2022-03-01 22:23 ` Michael Walle 2022-03-03 21:04 ` Chris Morgan 2022-03-03 21:04 ` Chris Morgan 2022-03-03 23:50 ` Tudor.Ambarus 2022-03-03 23:50 ` Tudor.Ambarus 2022-03-04 2:23 ` Chris Morgan 2022-03-04 2:23 ` Chris Morgan 2022-02-28 13:55 ` [PATCH v4 0/6] mtd: spi-nor: Handle ID collisions Michael Walle 2022-02-28 13:55 ` Michael Walle 2022-02-28 15:39 ` [PATCH] mtd: spi-nor: Move XMC to manufacturer ID collisions driver Tudor Ambarus 2022-02-28 15:39 ` Tudor Ambarus 2022-03-01 6:47 ` [PATCH v2] " Tudor Ambarus 2022-03-01 6:47 ` Tudor Ambarus
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=1a05176e6e2457c1b86035522c3f691b@walle.cc \ --to=michael@walle.cc \ --cc=code@reto-schneider.ch \ --cc=esben@geanix.com \ --cc=heiko.thiery@gmail.com \ --cc=jaimeliao@mxic.com.tw \ --cc=knaerzche@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linux@rasmusvillemoes.dk \ --cc=macromorgan@hotmail.com \ --cc=mail@david-bauer.net \ --cc=miquel.raynal@bootlin.com \ --cc=nicolas.ferre@microchip.com \ --cc=p.yadav@ti.com \ --cc=richard@nod.at \ --cc=sr@denx.de \ --cc=tudor.ambarus@microchip.com \ --cc=vigneshr@ti.com \ --cc=zhengxunli@mxic.com.tw \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.