[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJsYDVKYsz7c2yVe7TmPu_7kvBDXTih4+cceLsay2YJm21YntA@mail.gmail.com>
Date: Sun, 3 Apr 2022 23:45:44 +0800
From: Chuanhong Guo <gch981213@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: linux-spi@...ts.infradead.org, Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Roger Quadros <rogerq@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Cai Huoqing <cai.huoqing@...ux.dev>,
Florian Fainelli <f.fainelli@...il.com>,
Colin Ian King <colin.king@...el.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Paul Cercueil <paul@...pouillou.net>,
Pratyush Yadav <p.yadav@...com>, Yu Kuai <yukuai3@...wei.com>,
"open list:SPI SUBSYSTEM" <linux-spi@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:NAND FLASH SUBSYSTEM" <linux-mtd@...ts.infradead.org>
Subject: Re: [PATCH 3/4] dt-bindings: spi: add binding doc for spi-mtk-snfi
Hi!
On Sun, Apr 3, 2022 at 11:37 PM Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org> wrote:
> [...]
> > + compatible:
> > + enum:
> > + - mediatek,mt7622-snand
> > + - mediatek,mt7629-snand
>
> One blank line, please.
I'll fix this in the next version.
>
> > + reg:
> > + items:
> > + - description: core registers
> > +
> > + interrupts:
> > + items:
> > + - description: NFI interrupt
> > +
> > + clocks:
> > + items:
> > + - description: clock used for the controller
> > + - description: clock used for the SPI bus
> > +
> > + clock-names:
> > + items:
> > + - const: nfi_clk
> > + - const: pad_clk
> > +
> > + ecc-engine:
>
> The nand-chip.yaml defines a nand-ecc-engine, so how about using that
> one? I know mtk-nand.txt uses ecc-engine, but for new schema better to
> use properties from existing YAML.
The ecc-engine code is shared between mtk_nand.c and this driver, and
the property name is defined in the shared part. I left it as-is so that
existing dt for mtk_nand doesn't break.
--
Regards,
Chuanhong Guo
Powered by blists - more mailing lists