diff options
| author | Tom Rini <trini@konsulko.com> | 2018-08-31 11:59:11 -0400 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2018-09-25 21:49:18 -0400 |
| commit | 15416c86b494cd861d9f60d5a1940cfbf3bcc7f1 (patch) | |
| tree | 27fd182c699d5ae82526f6860e1a86ba6ff236ea /drivers/mmc | |
| parent | 484a878273539949c1dd97ad0e4c97c35acac87a (diff) | |
| download | u-boot-15416c86b494cd861d9f60d5a1940cfbf3bcc7f1.tar.gz u-boot-15416c86b494cd861d9f60d5a1940cfbf3bcc7f1.tar.xz u-boot-15416c86b494cd861d9f60d5a1940cfbf3bcc7f1.zip | |
dm: Update README.txt to clarify device tree usage
In the section about Device Trees add a paragraph at the end that
clarifies how we decide of a tree is valid or not. We say that all
bindings must either be in the specification (link provided) or in our
device-tree-bindings directory. We say that most of these come from the
Linux Kernel and as such some design decisions are made for us already,
but that in most cases we wish to retain compatibility.
Cc: Simon Glass <sjg@chromium.org>
Cc: Bin Meng <bmeng.cn@gmail.com>
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions