mirror of
https://github.com/torvalds/linux.git
synced 2026-04-18 14:53:58 -04:00
ab040c4223
The Devicetree bindings document does not have to say in the title that it is a "binding", but instead just describe the hardware. For shared (re-usable) schemas, name them all as "common properties". Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Acked-by: Guenter Roeck <linux@roeck-us.net> # watchdog Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> # IIO Acked-by: Miquel Raynal <miquel.raynal@bootlin.com> Acked-by: Ulf Hansson <ulf.hansson@linaro.org> # MMC Acked-by: Stephen Boyd <sboyd@kernel.org> # clk Acked-by: Vinod Koul <vkoul@kernel.org> # dma Acked-by: Mark Brown <broonie@kernel.org> Acked-by: Hans Verkuil <hverkuil-cisco@xs4all.nl> # media Acked-by: Sebastian Reichel <sre@kernel.org> # power Acked-by: Viresh Kumar <viresh.kumar@linaro.org> # opp Link: https://lore.kernel.org/r/20221216163815.522628-2-krzysztof.kozlowski@linaro.org Signed-off-by: Rob Herring <robh@kernel.org>
75 lines
2.2 KiB
YAML
75 lines
2.2 KiB
YAML
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/mtd/nand-chip.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: NAND Chip Common Properties
|
|
|
|
maintainers:
|
|
- Miquel Raynal <miquel.raynal@bootlin.com>
|
|
|
|
allOf:
|
|
- $ref: "mtd.yaml#"
|
|
|
|
description: |
|
|
This file covers the generic description of a NAND chip. It implies that the
|
|
bus interface should not be taken into account: both raw NAND devices and
|
|
SPI-NAND devices are concerned by this description.
|
|
|
|
properties:
|
|
reg:
|
|
description:
|
|
Contains the chip-select IDs.
|
|
|
|
nand-ecc-engine:
|
|
description: |
|
|
A phandle on the hardware ECC engine if any. There are
|
|
basically three possibilities:
|
|
1/ The ECC engine is part of the NAND controller, in this
|
|
case the phandle should reference the parent node.
|
|
2/ The ECC engine is part of the NAND part (on-die), in this
|
|
case the phandle should reference the node itself.
|
|
3/ The ECC engine is external, in this case the phandle should
|
|
reference the specific ECC engine node.
|
|
$ref: /schemas/types.yaml#/definitions/phandle
|
|
|
|
nand-use-soft-ecc-engine:
|
|
description: Use a software ECC engine.
|
|
type: boolean
|
|
|
|
nand-no-ecc-engine:
|
|
description: Do not use any ECC correction.
|
|
type: boolean
|
|
|
|
nand-ecc-algo:
|
|
description:
|
|
Desired ECC algorithm.
|
|
$ref: /schemas/types.yaml#/definitions/string
|
|
enum: [hamming, bch, rs]
|
|
|
|
nand-ecc-strength:
|
|
description:
|
|
Maximum number of bits that can be corrected per ECC step.
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 1
|
|
|
|
nand-ecc-step-size:
|
|
description:
|
|
Number of data bytes covered by a single ECC step.
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 1
|
|
|
|
secure-regions:
|
|
description:
|
|
Regions in the NAND chip which are protected using a secure element
|
|
like Trustzone. This property contains the start address and size of
|
|
the secure regions present.
|
|
$ref: /schemas/types.yaml#/definitions/uint64-matrix
|
|
|
|
required:
|
|
- reg
|
|
|
|
# This file can be referenced by more specific devices (like spi-nands)
|
|
additionalProperties: true
|