Hi,
On Sat, Nov 11, 2017 at 10:16:56PM +0100, Ladislav Michl wrote:
> Compatible property is required for OMAP2+ mtd driver. Also
> add R/B pin gpio description and delete unused dma-channel
> property.
>
> Signed-off-by: Ladislav Michl <ladis@xxxxxxxxxxxxxx>
> ---
> Changes:
> -v4: new patch
>
> Documentation/devicetree/bindings/mtd/gpmc-onenand.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mtd/gpmc-onenand.txt b/Documentation/devicetree/bindings/mtd/gpmc-onenand.txt
> index b6e8bfd024f4..9d7b1409deab 100644
> --- a/Documentation/devicetree/bindings/mtd/gpmc-onenand.txt
> +++ b/Documentation/devicetree/bindings/mtd/gpmc-onenand.txt
> @@ -9,13 +9,14 @@ Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt
>
> Required properties:
>
> + - compatible: "ti,omap2-onenand"
I suggest to also add more specific compatible values (i.e.
"ti,omap3-onenand") in case it is needed later. They don't
hurt much and may prevent ugly hacks in the future.
> - reg: The CS line the peripheral is connected to
> - - gpmc,device-width Width of the ONENAND device connected to the GPMC
> + - gpmc,device-width: Width of the ONENAND device connected to the GPMC
> in bytes. Must be 1 or 2.
>
> Optional properties:
>
> - - dma-channel: DMA Channel index
> + - rb-gpios: GPIO specifier for the ready/busy# pin.
>
> For inline partition table parsing (optional):
>
> @@ -35,6 +36,7 @@ Example for an OMAP3430 board:
> #size-cells = <1>;
>
> onenand@0 {
> + compatible = "ti,omap2-onenand";
> reg = <0 0 0>; /* CS0, offset 0 */
> gpmc,device-width = <2>;
>
-- Sebastian
Attachment:
signature.asc
Description: PGP signature
