[v2,2/9] dt-bindings: board: Document sifive,fu540-modeselect

Add dt-bindings documentation for sifive,fu540-modeselect board
driver, which usually get runtime boot mode of fu540 boards.

Cc: Simon Glass <sjg at chromium.org>
Signed-off-by: Jagan Teki <jagan at amarulasolutions.com>
---
Changes for v2:
- new patch

 .../board/sifive,fu540-modeselect.txt             | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 doc/device-tree-bindings/board/sifive,fu540-modeselect.txt

Hi Jagan,

On Wed, May 20, 2020 at 3:24 AM Jagan Teki <jagan at amarulasolutions.com> wrote:
>
> Add dt-bindings documentation for sifive,fu540-modeselect board
> driver, which usually get runtime boot mode of fu540 boards.
>
> Cc: Simon Glass <sjg at chromium.org>
> Signed-off-by: Jagan Teki <jagan at amarulasolutions.com>
> ---
> Changes for v2:
> - new patch
>
>  .../board/sifive,fu540-modeselect.txt             | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>  create mode 100644 doc/device-tree-bindings/board/sifive,fu540-modeselect.txt
>
> diff --git a/doc/device-tree-bindings/board/sifive,fu540-modeselect.txt b/doc/device-tree-bindings/board/sifive,fu540-modeselect.txt
> new file mode 100644
> index 0000000000..801c068390
> --- /dev/null
> +++ b/doc/device-tree-bindings/board/sifive,fu540-modeselect.txt
> @@ -0,0 +1,15 @@
> +fu540 board driver
> +
> +This driver provides capabilities to get the current boot device for
> +fu540 associated board.

This is not a board specific setting, but a SoC specific setting. The
MSEL is common for all FU540 based board.

> +
> +Required properties:
> +- compatible:  should be "sifive,fu540-modeselect"
> +- reg:         physical base address and size of fu540 modeselct
> +
> +Example:
> +
> +board: mode at 1000 {
> +       compatible = "sifive,fu540-modeselect";
> +       reg = <0x0 0x1000 0x0 0x1FFF>;

We should only map 4 bytes for mode select.

> +};
> --

Regards,
Bin