On 8 May 2018 at 20:46, Liming Sun <[email protected]> wrote:
> This commit adds "mellanox,bluefield-dw-mshc" for dwmmc driver
> extension on Mellanox BlueField SoC platform.
>
> Signed-off-by: Liming Sun <[email protected]>
> Reviewed-by: David Woods <[email protected]>
> Reviewed-by: Rob Herring <[email protected]>

Thanks, applied for next!

Kind regards
Uffe

> ---
>  .../devicetree/bindings/mmc/bluefield-dw-mshc.txt  | 29 
> ++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>  create mode 100644 
> Documentation/devicetree/bindings/mmc/bluefield-dw-mshc.txt
>
> diff --git a/Documentation/devicetree/bindings/mmc/bluefield-dw-mshc.txt 
> b/Documentation/devicetree/bindings/mmc/bluefield-dw-mshc.txt
> new file mode 100644
> index 0000000..b0f0999
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/bluefield-dw-mshc.txt
> @@ -0,0 +1,29 @@
> +* Mellanox Bluefield SoC specific extensions to the Synopsys Designware
> +  Mobile Storage Host Controller
> +
> +Read synopsys-dw-mshc.txt for more details
> +
> +The Synopsys designware mobile storage host controller is used to interface
> +a SoC with storage medium such as eMMC or SD/MMC cards. This file documents
> +differences between the core Synopsys dw mshc controller properties described
> +by synopsys-dw-mshc.txt and the properties used by the Mellanox Bluefield SoC
> +specific extensions to the Synopsys Designware Mobile Storage Host 
> Controller.
> +
> +Required Properties:
> +
> +* compatible: should be one of the following.
> +  - "mellanox,bluefield-dw-mshc": for controllers with Mellanox Bluefield SoC
> +    specific extensions.
> +
> +Example:
> +
> +       /* Mellanox Bluefield SoC MMC */
> +       mmc@6008000 {
> +               compatible = "mellanox,bluefield-dw-mshc";
> +               reg = <0x6008000 0x400>;
> +               interrupts = <32>;
> +               fifo-depth = <0x100>;
> +               clock-frequency = <24000000>;
> +               bus-width = <8>;
> +               cap-mmc-highspeed;
> +       };
> --
> 1.8.3.1
>

Reply via email to