From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Subject: Re: [PATCH v5 7/8] dt-binding: mtd: Document gpio-addr-flash Date: Wed, 3 Oct 2018 22:59:21 +0200 Message-ID: <20181003225921.40ab58a7@bbrezillon> References: <20181003193859.23928-1-ricardo.ribalda@gmail.com> <20181003193859.23928-7-ricardo.ribalda@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181003193859.23928-7-ricardo.ribalda@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Ricardo Ribalda Delgado Cc: David Woodhouse , Brian Norris , Marek Vasut , Richard Weinberger , Zhouyang Jia , linux-mtd@lists.infradead.org, open list , devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org On Wed, 3 Oct 2018 21:38:58 +0200 Ricardo Ribalda Delgado wrote: > Add documentation for gpio-addr-flash. This binding allow creating > flash devices that are paged using GPIOs. > > Cc: devicetree@vger.kernel.org > Reviewed-by: Rob Herring > Signed-off-by: Ricardo Ribalda Delgado > --- > .../bindings/mtd/gpio-addr-flash.txt | 54 +++++++++++++++++++ > 1 file changed, 54 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mtd/gpio-addr-flash.txt > > diff --git a/Documentation/devicetree/bindings/mtd/gpio-addr-flash.txt b/Documentation/devicetree/bindings/mtd/gpio-addr-flash.txt > new file mode 100644 > index 000000000000..5006a26e1753 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mtd/gpio-addr-flash.txt > @@ -0,0 +1,54 @@ > +Memory Mapped flash with some address lines addressed using GPIOs > + > +Handle the case where a flash device is mostly addressed using physical > +line and supplemented by GPIOs. This way you can hook up say a 8MiB flash > +to a 2MiB memory range and use the GPIOs to select a particular range. > + > + - compatible : "cfi-gpio-addr-flash" > + - reg : Address range of the mtd chip that is memory mapped, this is, > + on the previous example 2MiB. > + - bank-width : Width (in bytes) of the bank. Equal to the > + device width times the number of interleaved chips. > + - gpios: List of GPIO specifiers that will be used to address the MSBs address > + lines. The order goes from LSB to MSB. I'd recommend naming the GPIO set (addr-gpios or msb-addr-gpios?), just to make things clear. > + - probe-type : (optional) "cfi_probe", "jedec_probe". How the mtd chip > + is going to be probed. If omitted, assumed to be equal to "cfi_probe". > + - #address-cells, #size-cells : Must be present if the device has > + sub-nodes representing partitions (see below). In this case > + both #address-cells and #size-cells must be equal to 1. > + > +The device tree may optionally contain sub-nodes describing partitions of the > +address space. Check partition.txt for more details. > + > +Example: > + > + flash@300000 { > + #address-cells = <1>; > + #size-cells = <1>; > + compatible = "cfi-gpio-addr-flash"; > + bank-width = <2>; > + reg = < 0x00300000 0x00200000 >; > + gpios = <&gpio_0 3 0>, <&gpio_0 4 0>; > + partitions { > + compatible = "fixed-partitions"; > + #address-cells = <1>; > + #size-cells = <1>; > + > + partition@0 { > + reg = < 0x0 0x200000 >; > + label = "Golden Bitstream"; > + }; > + partition@200000 { > + reg = < 0x200000 0x200000 >; > + label = "User Bitstream"; > + }; > + partition@400000 { > + reg = < 0x400000 0x200000 >; > + label = "V4L Controls"; > + }; > + partition@600000 { > + reg = < 0x600000 0x200000 >; > + label = "Production Data"; > + }; > + } > + } ;