phosphor-mrw-tools/docs/mrw-xml-requirements.md

5 [Serverwiz2](https://www.github.com/open-power/serverwiz). The requirements in
14 contains all FRUs (field replaceable units), along with a few non-FRU entities,
19 - Set the `FRU_NAME` attribute of that target.
24 ## BMC Device Tree
26 The BMC device tree can be generated from the MRW XML. For the full device tree
33 The following sections list the system dependent information that the device
34 tree generator requires. The majority of the information it requires is static
50 All of the BMC chip attributes that are needed for the device tree are pre-built
51 into the XML representation and don't need to be updated when the device is
55 > necessary device tree attributes.
59 The device tree can support either 1 or 2 BMC SPI flash chips. This is
61 spi-master-unit on the BMC that has its `SPI_FUNCTION` attribute set to
89 LEDS will be listed in the device tree when LED parts in the MRW are wired to
91 node in the device tree.
95 Set to the logic value required to activate the LED - either 0 or 1. The default
106 device.
110 When creating a new XML device model, this attribute should be used to specify
111 which device driver the kernel will use to access the device. For example,
117 an I2C device. It specifies which other attributes of the device should be
118 listed as properties in the device tree, as required by the device driver for
119 that device. It can contain up to 4 pairs of names, the first name in the pair
121 name of the property to call it in the device tree. For example,
124 `pagesize` in the device tree.