No description
Find a file
Rob Herring e1f139ea49 checks: drop warning for missing PCI bridge bus-range
Having a 'bus-range' property for PCI bridges should not be required,
so remove the warning when missing. There was some confusion with the
Linux kernel printing a message that no property is present and the OS
assigned the bus number. This message was intended to be informational
rather than a warning.

When the firmware doesn't enumerate the PCI bus and leaves it up to the
OS to do, then it is perfectly fine for the OS to assign bus numbers
and bus-range is not necessary.

There are a few cases where bus-range is needed or useful as Arnd
Bergmann summarized:

- Traditionally Linux avoided using multiple PCI domains, but instead
  configured separate PCI host bridges to have non-overlapping
  bus ranges so we can present them to user space as a single
  domain, and run the kernel without CONFIG_PCI_DOMAINS.
  Specifying the bus ranges this way would and give stable bus
  numbers across boots when the probe order is not fixed.

- On certain ARM64 systems, we must only use the first
  128 bus numbers based on the way the IOMMU identifies
  the device with truncated bus/dev/fn number. There are probably
  others like this, with various limitations.

- To leave some room for hotplugged devices, each slot on
  a host bridge can in theory get a range of bus numbers
  that are available when assigning bus numbers at boot time

Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2018-04-22 14:13:28 +10:00
Documentation fdtoverlay: A tool that applies overlays 2017-06-15 15:37:07 +08:00
libfdt Add limited read-only support for older (V2 and V3) device tree to libfdt. 2018-01-27 18:43:21 +11:00
pylibfdt pylibfdt: Use Python2 explicitly 2017-09-27 18:10:02 +10:00
scripts dtc: Add maintainer script for signing and upload to kernel.org 2014-11-12 14:27:02 +11:00
tests tests: Update valgrind suppressions for sw_tree1 2018-03-09 14:01:51 +11:00
.gitignore Add fdtoverlay to .gitignore 2017-09-27 20:00:10 +10:00
.travis.yml .travis.yml: Run valgrind checks via Travis 2018-03-09 14:28:02 +11:00
checks.c checks: drop warning for missing PCI bridge bus-range 2018-04-22 14:13:28 +10:00
convert-dtsv0-lexer.l Fix assorted sparse warnings 2017-03-06 12:08:53 +11:00
data.c Fix assorted sparse warnings 2017-03-06 12:08:53 +11:00
dtc-lexer.l Clean up gcc attributes 2017-03-06 12:06:15 +11:00
dtc-parser.y Correct overlay syntactic sugar for generating target-path fragments 2018-03-06 14:53:27 +11:00
dtc.c livetree: avoid assertion of orphan phandles with overlays 2017-10-27 16:25:54 +02:00
dtc.h Fix ambiguous grammar for devicetree rule 2017-11-21 15:07:14 +11:00
dtdiff dtc: Add code to make diffing trees easier 2010-11-13 15:47:29 -06:00
fdtdump.c fdtdump: Discourage use of fdtdump 2017-04-18 13:05:08 +10:00
fdtget.c Add limited read-only support for older (V2 and V3) device tree to libfdt. 2018-01-27 18:43:21 +11:00
fdtoverlay.c fdtoverlay: Switch from using alloca to malloc 2018-01-03 14:15:16 +11:00
fdtput.c Remove leading underscores from identifiers 2017-10-26 09:25:14 +02:00
flattree.c Add strstarts() helper function 2017-11-11 19:36:14 +11:00
fstree.c Rename boot_info 2016-12-09 16:30:43 +11:00
GPL dtc: Remove redundant copy of the GPL 2007-06-25 21:43:11 -05:00
livetree.c Correct overlay syntactic sugar for generating target-path fragments 2018-03-06 14:53:27 +11:00
Makefile Avoid installing pylibfdt when dependencies are missing 2018-01-08 17:55:05 +11:00
Makefile.convert-dtsv0 Implement and use an xstrdup() function 2008-10-03 11:12:33 -05:00
Makefile.dtc Implement and use an xstrdup() function 2008-10-03 11:12:33 -05:00
Makefile.utils fdtoverlay: A tool that applies overlays 2017-06-15 15:37:07 +08:00
README README: Add a note about test_tree1.dts 2017-08-21 10:18:25 +10:00
README.license dtc/libfdt: Add README clarifying licensing 2008-01-04 08:37:36 -06:00
srcpos.c srcpos: drop special handling of tab 2018-01-23 17:05:00 +11:00
srcpos.h Remove leading underscores from identifiers 2017-10-26 09:25:14 +02:00
TODO dtc: Update TODO files 2007-12-19 08:20:26 -06:00
treesource.c Fix assorted sparse warnings 2017-03-06 12:08:53 +11:00
util.c Fix assorted sparse warnings 2017-03-06 12:08:53 +11:00
util.h Remove leading underscores from identifiers 2017-10-26 09:25:14 +02:00

The source tree contains the Device Tree Compiler (dtc) toolchain for
working with device tree source and binary files and also libfdt, a
utility library for reading and manipulating the binary format.

DTC and LIBFDT are maintained by:

David Gibson <david@gibson.dropbear.id.au>
Jon Loeliger <jdl@jdl.com>


Python library
--------------

A Python library is also available. To build this you will need to install
swig and Python development files. On Debian distributions:

   sudo apt-get install swig python-dev

The library provides an Fdt class which you can use like this:

$ PYTHONPATH=../pylibfdt python
>>> import libfdt
>>> fdt = libfdt.Fdt(open('test_tree1.dtb').read())
>>> node = fdt.path_offset('/subnode@1')
>>> print node
124
>>> prop_offset = fdt.first_property_offset(node)
>>> prop = fdt.get_property_by_offset(prop_offset)
>>> print '%s=%r' % (prop.name, prop.value)
compatible=bytearray(b'subnode1\x00')
>>> print '%s=%s' % (prop.name, prop.value)
compatible=subnode1
>>> node2 = fdt.path_offset('/')
>>> print fdt.getprop(node2, 'compatible')
test_tree1

You will find tests in tests/pylibfdt_tests.py showing how to use each
method. Help is available using the Python help command, e.g.:

    $ cd pylibfdt
    $ python -c "import libfdt; help(libfdt)"

If you add new features, please check code coverage:

    $ sudo apt-get install python-pip python-pytest
    $ sudo pip install coverage
    $ cd tests
    $ coverage run pylibfdt_tests.py
    $ coverage html
    # Open 'htmlcov/index.html' in your browser


To install the library via the normal setup.py method, use:

    ./pylibfdt/setup.py [--prefix=/path/to/install_dir]

If --prefix is not provided, the default prefix is used, typically '/usr'
or '/usr/local'. See Python's distutils documentation for details. You can
also install via the Makefile if you like, but the above is more common.

To install both libfdt and pylibfdt you can use:

    make install [SETUP_PREFIX=/path/to/install_dir] \
            [PREFIX=/path/to/install_dir]

To disable building the python library, even if swig and Python are available,
use:

    make NO_PYTHON=1


More work remains to support all of libfdt, including access to numeric
values.


Tests
-----

Test files are kept in the tests/ directory. Use 'make check' to build and run
all tests.

If you want to adjust a test file, be aware that tree_tree1.dts is compiled
and checked against a binary tree from assembler macros in trees.S. So
if you change that file you must change tree.S also.


Mailing list
------------
The following list is for discussion about dtc and libfdt implementation
mailto:devicetree-compiler@vger.kernel.org

Core device tree bindings are discussed on the devicetree-spec list:
mailto:devicetree-spec@vger.kernel.org