tree a0ebcf7dc8d280d5693235ed86899b90a08b9490
parent cdf3d1a98b751d35c390961b73ee78feff145ff7
author Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> 1556284589 +0530
committer Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> 1556286431 +0530
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEZ6VDKoFIy9ikWCeXVZ8R5v6RzvUFAlzDC98ACgkQVZ8R5v6R
 zvUIaQf9F8chlRACFJK11oz7/MjatJgBYta4Qw/NO23yuwNopuDs/SHVQfrLN72E
 xqV+GlCdxNK4RD+YoKctNKGcv7EG0m7CEUV0+0g6K2HehSZthjU3ikMrOxchubAG
 h2YGfiT9chiJBINkAftUrKmXUNIjTYNhL0Kh0SxRuYyCH1233taVD3/L6C/Tp0zN
 rWMSsFL9tSEDa7vsr198/5SGI6nCAwRXlzHdPGebgutbvBQPgydHVYJVtrMnBVkQ
 ICGLTOwtbXiYjzXri7HzK60x4BLRpfaQt1zSo3rwv2niIeT7H+MQiNhkZjmVRt3W
 MAhHp8UL+96OA0/ExTwTkGI9r77yhw==
 =KhcG
 -----END PGP SIGNATURE-----

docs: plat: stm32mp1: Document the usage of DTB_FILE_NAME variable

Since STM32MP1 platform supports different boards, it is necessary
to build for a particular board. With the current instructions, the
user has to modify the DTB_FILE_NAME variable in platform.mk for
building for a particular board, but this can be avoided by passing
the appropriate board DTB name via DTB_FILE_NAME make variable.
Hence document the same in platform doc.

Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Change-Id: I16797e7256c7eb699a7b8846356fe430d0fe0aa1