mirror of
https://review.coreboot.org/flashrom.git
synced 2025-04-28 07:23:43 +02:00
tests: Add comprehensive comment for chip.c
The following describes the two mechanisms of testing done for flash chip operations. BUG=b:181803212 TEST=ninja test Change-Id: Ie498ec55cce8460fc0b2e1fe27254d3a9f763fac Signed-off-by: Anastasia Klimchuk <aklm@chromium.org> Reviewed-on: https://review.coreboot.org/c/flashrom/+/59238 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Felix Singer <felixsinger@posteo.net> Reviewed-by: Edward O'Callaghan <quasisec@chromium.org>
This commit is contained in:
parent
3f8d1b4f2b
commit
9fb5812896
12
tests/chip.c
12
tests/chip.c
@ -11,6 +11,18 @@
|
||||
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
* GNU General Public License for more details.
|
||||
*
|
||||
* This file contains tests for operations on flash chip.
|
||||
*
|
||||
* Two flash chip test variants are used:
|
||||
*
|
||||
* 1) Mock chip state backed by `g_chip_state`.
|
||||
* Example of test: erase_chip_test_success.
|
||||
*
|
||||
* 2) Mock chip operations backed by `dummyflasher` emulation.
|
||||
* Dummyflasher controls chip state and emulates read/write/unlock/erase.
|
||||
* `g_chip_state` is NOT used for this type of tests.
|
||||
* Example of test: erase_chip_with_dummyflasher_test_success.
|
||||
*/
|
||||
|
||||
#include <include/test.h>
|
||||
|
Loading…
x
Reference in New Issue
Block a user