On Wed, 01 Sep 2021 11:18:05 +0200, Maxime Ripard wrote:
> The Reserved Memory mechanism is supported by Linux thanks to its device
> tree binding.
> 
> Now that we have the DT validation in place, let's convert the device
> tree bindings for that driver over to a YAML schema.
> 
> Cc: Mailing List <devicetree-s...@vger.kernel.org>
> Signed-off-by: Maxime Ripard <max...@cerno.tech>
> 
> ---
> 
> Changes from v1:
>   - Fixed the license
>   - Added a mention that the file has moved
>   - Added a documentation for memory-region
>   - Split the reserved-memory binding in two: one for the generic part
>     and one for shared-dma-pool
> ---
>  .../reserved-memory/memory-region.yaml        |  40 ++++
>  .../reserved-memory/reserved-memory.txt       | 172 +-----------------
>  .../reserved-memory/reserved-memory.yaml      |  96 ++++++++++
>  .../reserved-memory/shared-dma-pool.yaml      |  87 +++++++++
>  4 files changed, 224 insertions(+), 171 deletions(-)
>  create mode 100644 
> Documentation/devicetree/bindings/reserved-memory/memory-region.yaml
>  create mode 100644 
> Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
>  create mode 100644 
> Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml
> 

I reworked the commit msg and a couple of nits, and applied, thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/linux-sunxi/YTJkshhMXjmYsQl9%40robh.at.kernel.org.

Reply via email to