dtc/tests/overlay_base_manual_symbols...

/*
 * Copyright (c) 2016 NextThing Co
 * Copyright (c) 2016 Free Electrons
 *
 * SPDX-License-Identifier:	GPL-2.0+
 */

/dts-v1/;

/ {
	test: test-node {
		phandle = <&test>; /* Force phandle generation */
		test-int-property = <42>;
		test-str-property = "foo";

		subtest: sub-test-node {
			sub-test-property;
		};
	};
	__symbols__ {
		test = &test;
	};
};
tests: More thorough tests of libfdt overlay application without dtc At the moment we have some rudimentary tests of the fdt_overlay_apply() function which don't rely on overlay generation support in dtc. This is done by avoiding any external references in the sample overlay, in particularly using the 'target-path' syntax instead of 'target' to avoid needing external references in the fragment targets. Thus this test case doesn't exercise libfdt's processing of the __fixups__ node at all. We do test that somewhat in combination with dtc's overlay support. However, in the interests of being able to quickly determine which side a bug is on, it would be nice to exercise this without requiring the dtc support. This adds testcases to do so, by making some examples with manually constructed __symbols__ and __fixups__ nodes. In addition we rename some of the test data files and add some extra check_path tests to make it a bit clearer what's going on here. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> 8 years ago			`/*`
			`* Copyright (c) 2016 NextThing Co`
			`* Copyright (c) 2016 Free Electrons`
			`*`
			`* SPDX-License-Identifier: GPL-2.0+`
			`*/`

			`/dts-v1/;`

			`/ {`
			`test: test-node {`
			`phandle = <&test>; /* Force phandle generation */`
			`test-int-property = <42>;`
			`test-str-property = "foo";`

			`subtest: sub-test-node {`
			`sub-test-property;`
			`};`
			`};`
			`__symbols__ {`
			`test = &test;`
			`};`
			`};`