bindings/fpga/fpga-region.txt

167 - compatible : should contain "fpga-region"
168 - fpga-mgr : should contain a phandle to an FPGA Manager.  Child FPGA Regions
169 	inherit this property from their ancestor regions.  A fpga-mgr property
180 - fpga-bridges : should contain a list of phandles to FPGA Bridges that must be
183         If the fpga-region is  the child of a fpga-bridge, the list should not
185 - partial-fpga-config : boolean, set if partial reconfiguration is to be done,
187 - external-fpga-config : boolean, set if the FPGA has already been configured
189 - encrypted-fpga-config : boolean, set if the bitstream is encrypted
200 In the example below, when an overlay is applied targeting fpga-region0,
204 fpga-bridges property.  During programming, these bridges are disabled, the
216 	fpga_mgr: fpga-mgr@ff706000 {
217 		compatible = "altr,socfpga-fpga-mgr";
223 	fpga_bridge0: fpga-bridge@ff400000 {
233 		fpga_region0: fpga-region0 {
234 			compatible = "fpga-region";
235 			fpga-mgr = <&fpga_mgr>;
239 	fpga_bridge1: fpga-bridge@ff500000 {
259 			fpga-bridges = <&fpga_bridge1>;
300    fpga-bridges property in the FPGA region or in the device tree overlay.
328 Bridges.  The FPGA Region's "fpga-mgr" property specifies the manager by phandle
331 they are specified in the FPGA Region by the "fpga-bridges" property.  During
333 "fpga-bridges" list and will re-enable them after FPGA programming has
345  * "partial-fpga-config"
355 	fpga_mgr0: fpga-mgr@f8007000 {
365 	fpga_region0: fpga-region0 {
366 		compatible = "fpga-region";
367 		fpga-mgr = <&fpga_mgr0>;
417 			fpga-bridge@4400 {
421 				fpga_region1: fpga-region1 {
422 					compatible = "fpga-region";
429 			fpga-bridge@4420 {
433 				fpga_region2: fpga-region2 {
434 					compatible = "fpga-region";
451 "partial-fpga-config" boolean and the only bridge that is controlled during
465 			partial-fpga-config;