Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Thu, 14 Apr 2022 11:00:14 -0500
From:   Rob Herring <robh@kernel.org>
To:     Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc:     richard@nod.at, joern@lazybastard.org,
        linux-mtd@lists.infradead.org, frowand.list@gmail.com,
        vigneshr@ti.com, krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
        robh+dt@kernel.org, kernel@axis.com, miquel.raynal@bootlin.com,
        devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: reserved-memory: Support MTD/block
 device
Message-ID: <YlhFDi0uE/3Pdxjt@robh.at.kernel.org>
References: <20220412135302.1682890-1-vincent.whitchurch@axis.com>
 <20220412135302.1682890-3-vincent.whitchurch@axis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220412135302.1682890-3-vincent.whitchurch@axis.com>
Precedence: bulk

On Tue, 12 Apr 2022 15:53:00 +0200, Vincent Whitchurch wrote:
> Add bindings to allow MTD/block devices to be used in reserved-memory
> regions using the "phram" (MTD in PHysical RAM) driver.
> 
> This allows things like partitioning to be specified via the existing
> devicetree bindings.
> 
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> 
> Notes:
>     v3:
>     - Reword description.
> 
>     v2:
>     - Add note on what "phram" means.
>     - Use /schemas/mtd/mtd.yaml instead of relative pathUse /schemas/mtd/mtd.yaml instead of relative path.
> 
>  .../bindings/reserved-memory/phram.yaml       | 47 +++++++++++++++++++
>  1 file changed, 47 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/reserved-memory/phram.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>