Go to file
Rob Herring c1e7738988 checks: add gpio binding properties check
The GPIO binding is different compared to other phandle plus args
properties in that the property name has a variable, optional prefix.
The format of the property name is [<name>-]gpio{s} where <name> can
be any legal property string. Therefore, custom matching of property
names is needed, but the common check_property_phandle_args() function
can still be used.

It's possible that there are property names matching which are not GPIO
binding specifiers. There's only been one case found in testing which is
"[<vendor>,]nr-gpio{s}". This property has been blacklisted and the same
should be done to any others we find. This check will prevent getting
any more of these, too.

Signed-off-by: Rob Herring <robh@kernel.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2017-09-22 21:14:43 +10:00
Documentation fdtoverlay: A tool that applies overlays 2017-06-15 15:37:07 +08:00
libfdt fdt: Allow stacked overlays phandle references 2017-08-09 17:18:47 +10:00
pylibfdt pylibfdt: Add support for fdt_subnode_offset() 2017-08-21 10:17:57 +10:00
scripts dtc: Add maintainer script for signing and upload to kernel.org 2014-11-12 14:27:02 +11:00
tests checks: add gpio binding properties check 2017-09-22 21:14:43 +10:00
.gitignore .gitignore: Add rule for *.patch 2013-01-27 14:21:44 -06:00
.travis.yml Add Coverity Scan support 2017-04-07 15:55:16 +10:00
GPL dtc: Remove redundant copy of the GPL 2007-06-25 21:43:11 -05:00
Makefile fdtoverlay: A tool that applies overlays 2017-06-15 15:37:07 +08: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
TODO dtc: Update TODO files 2007-12-19 08:20:26 -06:00
checks.c checks: add gpio binding properties check 2017-09-22 21:14:43 +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 dtc: Fix NULL pointer use in dtlabel + dtref case 2017-01-31 09:50:22 +11:00
dtc.c dtc: change default phandles to ePAPR style instead of both 2017-07-13 10:21:42 +10:00
dtc.h checks: add phandle with arg property checks 2017-09-22 21:14:10 +10: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 fdtget: Split out cell list display into a new function 2017-08-21 10:29:48 +10:00
fdtoverlay.c fdtoverlay: A tool that applies overlays 2017-06-15 15:37:07 +08:00
fdtput.c fdtput: Remove star from value_len documentation 2017-03-06 14:19:26 +11:00
flattree.c dtc: Simplify asm_emit_string() implementation 2017-03-06 14:19:26 +11:00
fstree.c Rename boot_info 2016-12-09 16:30:43 +11:00
livetree.c checks: add phandle with arg property checks 2017-09-22 21:14:10 +10:00
srcpos.c dtc: pos parameter to srcpos_string() can't be NULL 2017-02-08 17:39:36 +11:00
srcpos.h Clean up gcc attributes 2017-03-06 12:06:15 +11: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 Clean up gcc attributes 2017-03-06 12:06:15 +11:00

README

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