On Wed, May 08, 2019 at 08:43:37AM -0500, Dinh Nguyen wrote:
> The QSPI module can have an optional reset signals that will hold the
> module in a reset state.
>
> Signed-off-by: Dinh Nguyen <dinguyen@xxxxxxxxxx>
> ---
> v4: no change
> v3: created base on review comments
> v2: did not exist
> v1: did not exist
> ---
> Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
> index 4345c3a6f530..b6264323a03c 100644
> --- a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
> +++ b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
> @@ -35,6 +35,8 @@ custom properties:
> (qspi_n_ss_out).
> - cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
> and first bit transfer.
> +- resets : Must contain an entry for each entry in reset-names.
> + See ../reset/reset.txt for details.
reset-names needs to be documented with the values and order.
>
> Example:
>
> @@ -50,6 +52,8 @@ Example:
> cdns,fifo-depth = <128>;
> cdns,fifo-width = <4>;
> cdns,trigger-address = <0x00000000>;
> + resets = <&rst QSPI_RESET>, <&rst QSPI_OCP_RESET>;
> + reset-names = "qspi", "qspi-ocp";
>
> flash0: n25q00@0 {
> ...
> --
> 2.20.0
>
