<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/include/linux/mtd, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-04-22T15:55:58Z</updated>
<entry>
<title>mtd: nand: provide several helpers to do common NAND operations</title>
<updated>2019-04-22T15:55:58Z</updated>
<author>
<name>Boris Brezillon</name>
</author>
<published>2019-03-15T14:14:32Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=9db29b300f7d9a58122a22a0815fe8449a664563'/>
<id>urn:sha1:9db29b300f7d9a58122a22a0815fe8449a664563</id>
<content type='text'>
Linux commit 97d90da8a88 ("mtd: nand: provide several helpers
to do common NAND operations")

This is part of the process of removing direct calls to -&gt;cmdfunc()
outside of the core in order to introduce a better interface to execute
NAND operations.

Here we provide several helpers and make use of them to remove all
direct calls to -&gt;cmdfunc(). This way, we can easily modify those
helpers to make use of the new -&gt;exec_op() interface when available.

Signed-off-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;
[miquel.raynal@free-electrons.com: rebased and fixed some conflicts]
Signed-off-by: Miquel Raynal &lt;miquel.raynal@free-electrons.com&gt;
Acked-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
[Philippe Reynes: adapt code to u-boot and only keep new function]

Signed-off-by: Philippe Reynes &lt;philippe.reynes@softathome.com&gt;
</content>
</entry>
<entry>
<title>mtd: nand: import nand_hw_control_init()</title>
<updated>2019-04-22T15:55:58Z</updated>
<author>
<name>Marc Gonzalez</name>
</author>
<published>2019-03-15T14:14:31Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=5df42b0603d50ea59e1039b31fe74c1309abdd3a'/>
<id>urn:sha1:5df42b0603d50ea59e1039b31fe74c1309abdd3a</id>
<content type='text'>
Linux commit d45bc58dd3b ("mtd: nand: import nand_hw_control_init()")

The code to initialize a struct nand_hw_control is duplicated across
several drivers. Factorize it using an inline function.

Signed-off-by: Marc Gonzalez &lt;marc_gonzalez@sigmadesigns.com&gt;
Signed-off-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;
[Philippe Reynes: adapt code to u-boot and only keep new function]

Signed-off-by: Philippe Reynes &lt;philippe.reynes@softathome.com&gt;
</content>
</entry>
<entry>
<title>mtd: add get/set of_node/flash_node helpers</title>
<updated>2019-04-22T15:55:58Z</updated>
<author>
<name>Brian Norris</name>
</author>
<published>2019-03-15T14:14:30Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=892a8682f71910aa12647c5636ec5304225c9e0f'/>
<id>urn:sha1:892a8682f71910aa12647c5636ec5304225c9e0f</id>
<content type='text'>
Linux commit 28b8b26b308 ("mtd: add get/set of_node/flash_node helpers")

We are going to begin using the mtd-&gt;dev.of_node field for MTD device
nodes, so let's add helpers for it. Also, we'll be making some
conversions on spi_nor (and nand_chip eventually) too, so get that ready
with their own helpers.

Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
Reviewed-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;
[Philippe Reynes: only add function nand_set_flash_node and
nand_get_flash_node because others were already backported]

Signed-off-by: Philippe Reynes &lt;philippe.reynes@softathome.com&gt;
</content>
</entry>
<entry>
<title>mtd: fix mtd_oobavail() incoherent returned value</title>
<updated>2019-04-12T05:28:21Z</updated>
<author>
<name>Miquel Raynal</name>
</author>
<published>2018-11-18T20:11:46Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=a55036b2786919996db6dcffd5f0a86d1077184b'/>
<id>urn:sha1:a55036b2786919996db6dcffd5f0a86d1077184b</id>
<content type='text'>
mtd_oobavail() returns either mtd-&gt;oovabail or mtd-&gt;oobsize. Both
values are unsigned 32-bit entities, so there is no reason to pretend
returning a signed one.

Signed-off-by: Miquel Raynal &lt;miquel.raynal@bootlin.com&gt;
</content>
</entry>
<entry>
<title>mtd: spi: spi-nor-core: Add back U-Boot specific features</title>
<updated>2019-02-07T10:03:21Z</updated>
<author>
<name>Vignesh R</name>
</author>
<published>2019-02-05T05:59:21Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=8c927809ea960596345c33b02294af6e236d4ad4'/>
<id>urn:sha1:8c927809ea960596345c33b02294af6e236d4ad4</id>
<content type='text'>
For legacy reasons, we will have to keep around U-Boot specific
SPI_FLASH_BAR and SPI_TX_BYTE. Add them back to the new framework

Signed-off-by: Vignesh R &lt;vigneshr@ti.com&gt;
Reviewed-by: Jagan Teki &lt;jagan@openedev.com&gt;
Tested-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt; #zynq-microzed
</content>
</entry>
<entry>
<title>mtd: spi: Port SPI NOR framework from Linux</title>
<updated>2019-02-07T10:03:21Z</updated>
<author>
<name>Vignesh R</name>
</author>
<published>2019-02-05T05:59:17Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=7aeedac01534ab343c28abed60f8e0fb9311bbee'/>
<id>urn:sha1:7aeedac01534ab343c28abed60f8e0fb9311bbee</id>
<content type='text'>
Current U-Boot SPI NOR support (sf layer) is quite outdated as it does not
support 4 byte addressing opcodes, SFDP table parsing and different types of
quad mode enable sequences. Many newer flashes no longer support BANK
registers used by sf layer to a access &gt;16MB of flash address space.
So, sync SPI NOR framework from Linux v4.19 that supports all the
above features. Start with basic sync up that brings in basic framework
subsequent commits will bring in more features.

Signed-off-by: Vignesh R &lt;vigneshr@ti.com&gt;
Tested-by: Simon Goldschmidt &lt;simon.k.r.goldschmidt@gmail.com&gt;
Tested-by: Stefan Roese &lt;sr@denx.de&gt;
Tested-by: Horatiu Vultur &lt;horatiu.vultur@microchip.com&gt;
Reviewed-by: Jagan Teki &lt;jagan@openedev.com&gt;
Tested-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt; #zynq-microzed
</content>
</entry>
<entry>
<title>mtd: Don't stop MTD partition creation when it fails on one device</title>
<updated>2018-12-05T19:15:36Z</updated>
<author>
<name>Boris Brezillon</name>
</author>
<published>2018-12-02T09:54:30Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=4a5594fa20d0fa6479f477d2bd67967aca201c2f'/>
<id>urn:sha1:4a5594fa20d0fa6479f477d2bd67967aca201c2f</id>
<content type='text'>
MTD partition creation code is a bit tricky. It tries to figure out
when things have changed (either MTD dev list or mtdparts/mtdids vars)
and when that happens it first deletes all the partitions that had been
previously created and then creates the new ones based on the new
mtdparts/mtdids values.
But before deleting the old partitions, it ensures that none of the
currently registered parts are being used and bails out when that's
not the case. So, we end up in a situation where, if at least one MTD
dev has one of its partitions used by someone (UBI for instance), the
partitions update logic no longer works for other devs.

Rework the code to relax the logic and allow updates of MTD parts on
devices that are not being used (we still refuse to updates parts on
devices who have at least one of their partitions used by someone).

Fixes: 5db66b3aee6f ("cmd: mtd: add 'mtd' command")
Signed-off-by: Boris Brezillon &lt;boris.brezillon@bootlin.com&gt;
Tested-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>mtd: Delete partitions attached to the device when a device is deleted</title>
<updated>2018-12-05T19:15:36Z</updated>
<author>
<name>Boris Brezillon</name>
</author>
<published>2018-12-02T09:54:24Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=a02820fca90ce9ccf243b3fce59c04dabd5671a8'/>
<id>urn:sha1:a02820fca90ce9ccf243b3fce59c04dabd5671a8</id>
<content type='text'>
If we don't do that, partitions might still be exposed while the
underlying device is gone.

Fixes: 2a74930da57f ("mtd: mtdpart: implement proper partition handling")
Signed-off-by: Boris Brezillon &lt;boris.brezillon@bootlin.com&gt;
Tested-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>mtd: Add a function to report when the MTD dev list has been updated</title>
<updated>2018-12-05T19:15:36Z</updated>
<author>
<name>Boris Brezillon</name>
</author>
<published>2018-12-02T09:54:22Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=4c47fd0b6bce62162e11b8a22e2eaf0d8f6673b1'/>
<id>urn:sha1:4c47fd0b6bce62162e11b8a22e2eaf0d8f6673b1</id>
<content type='text'>
We need to parse mtdparts/mtids again everytime a device has been
added/removed from the MTD list, but there's currently no way to know
when such an update has been done.

Add an -&gt;updated field to the idr struct that we set to true every time
a device is added/removed and expose a function returning the value
of this field and resetting it to false.

Signed-off-by: Boris Brezillon &lt;boris.brezillon@bootlin.com&gt;
Tested-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>mtd: nand: spi: Add Gigadevice SPI NAND support</title>
<updated>2018-10-04T12:54:24Z</updated>
<author>
<name>Stefan Roese</name>
</author>
<published>2018-08-16T16:05:08Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=9e5c2a755a6ca5f3931de548f43101d0d18ac003'/>
<id>urn:sha1:9e5c2a755a6ca5f3931de548f43101d0d18ac003</id>
<content type='text'>
This patch adds support for Gigadevices SPI NAND device to the new SPI
NAND infrastructure in U-Boot. Currently only the 128MiB GD5F1GQ4UC
device is supported.

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Cc: Miquel Raynal &lt;miquel.raynal@bootlin.com&gt;
Cc: Boris Brezillon &lt;boris.brezillon@bootlin.com&gt;
Cc: Jagan Teki &lt;jagan@openedev.com&gt;
Reviewed-by: Miquel Raynal &lt;miquel.raynal@bootlin.com&gt;
Acked-by: Jagan Teki &lt;jagan@openedev.com&gt;
</content>
</entry>
</feed>
