Searched hist:"488 f19adf040329cbc0f9d3bea4829ccd0ebb57b" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/Documentation/devicetree/bindings/mtd/ |
| H A D | intel,lgm-ebunand.yaml | diff 488f19adf040329cbc0f9d3bea4829ccd0ebb57b Mon Nov 14 03:03:03 CST 2022 Miquel Raynal <miquel.raynal@bootlin.com> dt-bindings: mtd: nand: Standardize the child node name
In almost all the schema mentioning a NAND chip child node, the name of
the subnode contains a single index number.
In practice there are currently no controller supporting more than 8 cs
so even the [a-f] numbers are not needed. But let's be safe and limit
the number of touched files by just allow a single number everywhere, so
in practice up to 16 CS at most. This value can anyway be limited in
each schema.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/linux-mtd/20221114090315.848208-6-miquel.raynal@bootlin.com
|
| H A D | allwinner,sun4i-a10-nand.yaml | diff 488f19adf040329cbc0f9d3bea4829ccd0ebb57b Mon Nov 14 03:03:03 CST 2022 Miquel Raynal <miquel.raynal@bootlin.com> dt-bindings: mtd: nand: Standardize the child node name
In almost all the schema mentioning a NAND chip child node, the name of
the subnode contains a single index number.
In practice there are currently no controller supporting more than 8 cs
so even the [a-f] numbers are not needed. But let's be safe and limit
the number of touched files by just allow a single number everywhere, so
in practice up to 16 CS at most. This value can anyway be limited in
each schema.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/linux-mtd/20221114090315.848208-6-miquel.raynal@bootlin.com
|