1*54fd6939SJiyong ParkDTB binding for FCONF properties 2*54fd6939SJiyong Park================================ 3*54fd6939SJiyong Park 4*54fd6939SJiyong ParkThis document describes the device tree format of |FCONF| properties. These 5*54fd6939SJiyong Parkproperties are not related to a specific platform and can be queried from 6*54fd6939SJiyong Parkcommon code. 7*54fd6939SJiyong Park 8*54fd6939SJiyong ParkDynamic configuration 9*54fd6939SJiyong Park~~~~~~~~~~~~~~~~~~~~~ 10*54fd6939SJiyong Park 11*54fd6939SJiyong ParkThe |FCONF| framework expects a *dtb-registry* node with the following field: 12*54fd6939SJiyong Park 13*54fd6939SJiyong Park- compatible [mandatory] 14*54fd6939SJiyong Park - value type: <string> 15*54fd6939SJiyong Park - Must be the string "fconf,dyn_cfg-dtb_registry". 16*54fd6939SJiyong Park 17*54fd6939SJiyong ParkThen a list of subnodes representing a configuration |DTB|, which can be used 18*54fd6939SJiyong Parkby |FCONF|. Each subnode should be named according to the information it 19*54fd6939SJiyong Parkcontains, and must be formed with the following fields: 20*54fd6939SJiyong Park 21*54fd6939SJiyong Park- load-address [mandatory] 22*54fd6939SJiyong Park - value type: <u64> 23*54fd6939SJiyong Park - Physical loading base address of the configuration. 24*54fd6939SJiyong Park 25*54fd6939SJiyong Park- max-size [mandatory] 26*54fd6939SJiyong Park - value type: <u32> 27*54fd6939SJiyong Park - Maximum size of the configuration. 28*54fd6939SJiyong Park 29*54fd6939SJiyong Park- id [mandatory] 30*54fd6939SJiyong Park - value type: <u32> 31*54fd6939SJiyong Park - Image ID of the configuration. 32*54fd6939SJiyong Park 33