Page History

...

Device trees for PHYTEC products consist of a board 'dts' file, a master SOM 'dtsi' file, a carrier board 'dtsi' file, SOM variant 'dtsi' filesboard dts file which represents the combination of a PHYTEC SOM and PHYTEC carrier board, and expansion boards and other connectable hardware. The board dts file includes other dtsi: the SOM dtsi file, the carrier board dtsi file, the SOM variant dtsi file, and expansion board 'dtsi' files. 

Board DTS file: Includes all 'dtsi' files that are to be built for this board target, and does not individually handle any nodes.

SOM DTSI file: Includes the processor 'dtsi' and contains and enables nodes for all buses/devices located on the SOM (e.g. eMMC flash).

...

files. These dtsi files may be split into common dtsi files to avoid code duplication. The SOM dtsi represents all of the devices that are located on the SOM, such as eMMC flash, through device tree definitions in the file or in other dtsi files that it includes, such as the processor dtsi file. Devices whose signals are routed through the SOM but whose hardware is located on the carrier board, such as SD/MMC, are defined

...

in the carrier board

...

SOM Variant DTSI files: The SOM variant 'dtsi' files represent the differences between a SOM variant and the fully-featured SOM, or different memory configurations (e.g. disables QSPI NOR if not populated).

...

dtsi file or in other dtsi files that it includes. We recommend that you enable or disable the devices defined in these files in the am57xx-phycore-rdk.dts file.

&i2c_eeprom: eeprom@50 {
	status = "disabled";
	compatible = "at,24c32";
	reg = <0x50>;
	pagesize = <32>;
};

The kernel source directory has very good documentation and examples on what bindings are supported for specific peripherals: Documentation/devicetree/bindings/.