1*c66ec88fSEmmanuel Vadot* Uploaded QE firmware 2*c66ec88fSEmmanuel Vadot 3*c66ec88fSEmmanuel Vadot If a new firmware has been uploaded to the QE (usually by the 4*c66ec88fSEmmanuel Vadot boot loader), then a 'firmware' child node should be added to the QE 5*c66ec88fSEmmanuel Vadot node. This node provides information on the uploaded firmware that 6*c66ec88fSEmmanuel Vadot device drivers may need. 7*c66ec88fSEmmanuel Vadot 8*c66ec88fSEmmanuel Vadot Required properties: 9*c66ec88fSEmmanuel Vadot - id: The string name of the firmware. This is taken from the 'id' 10*c66ec88fSEmmanuel Vadot member of the qe_firmware structure of the uploaded firmware. 11*c66ec88fSEmmanuel Vadot Device drivers can search this string to determine if the 12*c66ec88fSEmmanuel Vadot firmware they want is already present. 13*c66ec88fSEmmanuel Vadot - extended-modes: The Extended Modes bitfield, taken from the 14*c66ec88fSEmmanuel Vadot firmware binary. It is a 64-bit number represented 15*c66ec88fSEmmanuel Vadot as an array of two 32-bit numbers. 16*c66ec88fSEmmanuel Vadot - virtual-traps: The virtual traps, taken from the firmware binary. 17*c66ec88fSEmmanuel Vadot It is an array of 8 32-bit numbers. 18*c66ec88fSEmmanuel Vadot 19*c66ec88fSEmmanuel VadotExample: 20*c66ec88fSEmmanuel Vadot firmware { 21*c66ec88fSEmmanuel Vadot id = "Soft-UART"; 22*c66ec88fSEmmanuel Vadot extended-modes = <0 0>; 23*c66ec88fSEmmanuel Vadot virtual-traps = <0 0 0 0 0 0 0 0>; 24*c66ec88fSEmmanuel Vadot }; 25