Lines Matching refs:fuse

229       SEC_FUSE_DUMP - Dump the "fuse prog" commands necessary for writing the
293 have to be crafted by hand. The needed fuse lines can be looked up in [1]; a
300 * Enable trusted boot by burning the corresponding fuse (WARNING: this must be
301   the last fuse line written!)
302 * Lock the unused fuse lines
304 The command to employ is the "fuse prog" command previously enabled by setting
307 For the trusted boot, the fuse prog command has a special syntax, since the
308 ARMADA SoC demands that whole fuse lines (64 bit values) have to be written as
309 a whole. The fuse prog command itself allows lists of 32 bit words to be
311 operations to the fuse line, where the individual 32 bit words are identified
315 (0-2): The first and second words are the values to be written to the fuse
316 line, and the third is a lock flag, which is supposed to lock the fuse line
318 function calls, and the fuse line is only really written and locked (on writing
322 locks the fuse line without setting any value; this is needed to lock the
323 unused fuse lines.
325 As an example, to write the value 0011223344556677 to fuse line 10, we would
328 fuse prog -y 10 0 00112233 44556677 1
330 Here 10 is the fuse line number, 0 is the index of the first word to be
331 written, 00112233 and 44556677 are the values to be written to the fuse line
337 fuse prog -y 11 2 1
339 Here 11 is the fuse number, 2 is the index of the first word to be written
340 (notice that we only write to word 2 here; the third word for fuse line