diff options
| author | Suraj Jitindar Singh <sjitindarsingh@gmail.com> | 2017-05-24 16:37:19 +1000 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2017-05-26 15:55:23 +1000 |
| commit | 3bb3f137d0b92e5f7ec596a07acd5eada0c09cc3 (patch) | |
| tree | c8642720387c4fd46851a5e10404f3c7f4bbb269 /hdata/i2c.c | |
| parent | 3476c6ec24140f538d5555a36afe42c064b13e31 (diff) | |
| download | skiboot-3bb3f137d0b92e5f7ec596a07acd5eada0c09cc3.zip skiboot-3bb3f137d0b92e5f7ec596a07acd5eada0c09cc3.tar.gz skiboot-3bb3f137d0b92e5f7ec596a07acd5eada0c09cc3.tar.bz2 | |
libflash/mbox-flash: Implement MARK_WRITE_ERASED mbox call
Version two of the mbox-flash protocol defines a new command:
MARK_WRITE_ERASED.
This command provides a simple way to mark a region of flash as all 0xff
without the need to go and write all 0xff. This is an optimisation as
there is no need for an erase before a write, it is the responsibility of
the BMC to deal with the flash correctly, however in v1 it was ambiguous
what a client should do if the flash should be erased but not actually
written to. This allows of a optimal path to resolve this problem.
Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com>
Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Acked-by: Cyril Bur <cyril.bur@au1.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'hdata/i2c.c')
0 files changed, 0 insertions, 0 deletions