No description
e1f139ea49
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> |
||
---|---|---|
Documentation | ||
libfdt | ||
pylibfdt | ||
scripts | ||
tests | ||
.gitignore | ||
.travis.yml | ||
checks.c | ||
convert-dtsv0-lexer.l | ||
data.c | ||
dtc-lexer.l | ||
dtc-parser.y | ||
dtc.c | ||
dtc.h | ||
dtdiff | ||
fdtdump.c | ||
fdtget.c | ||
fdtoverlay.c | ||
fdtput.c | ||
flattree.c | ||
fstree.c | ||
GPL | ||
livetree.c | ||
Makefile | ||
Makefile.convert-dtsv0 | ||
Makefile.dtc | ||
Makefile.utils | ||
README | ||
README.license | ||
srcpos.c | ||
srcpos.h | ||
TODO | ||
treesource.c | ||
util.c | ||
util.h |
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