f48acbda7b
The Kconfig lint tool checks for cases of the code using BOOL type Kconfig options directly instead of with CONFIG() and will print out warnings about it. It gets confused by these references in comments and strings. To fix it so that it can find the real issues, just update these as we would with real issues. Signed-off-by: Martin Roth <martin@coreboot.org> Change-Id: I5c37f0ee103721c97483d07a368c0b813e3f25c0 Reviewed-on: https://review.coreboot.org/c/coreboot/+/43824 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
31 lines
980 B
C
31 lines
980 B
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
|
|
#ifndef _COMMON_MRC_CACHE_H_
|
|
#define _COMMON_MRC_CACHE_H_
|
|
|
|
#include <stddef.h>
|
|
#include <stdint.h>
|
|
#include <commonlib/region.h>
|
|
|
|
enum {
|
|
MRC_TRAINING_DATA,
|
|
MRC_VARIABLE_DATA,
|
|
};
|
|
|
|
/*
|
|
* It's up to the caller to decide when to retrieve and stash data. There is
|
|
* differentiation on recovery mode CONFIG(HAS_RECOVERY_MRC_CACHE), but that's
|
|
* only for locating where to retrieve and save the data. If a platform doesn't
|
|
* want to update the data then it shouldn't stash the data for saving.
|
|
* Similarly, if the platform doesn't need the data for booting because of a
|
|
* policy don't request the data.
|
|
*/
|
|
|
|
/* Get and stash data for saving provided the type passed in. The functions
|
|
* return < 0 on error, 0 on success. */
|
|
int mrc_cache_get_current(int type, uint32_t version,
|
|
struct region_device *rdev);
|
|
int mrc_cache_stash_data(int type, uint32_t version, const void *data,
|
|
size_t size);
|
|
|
|
#endif /* _COMMON_MRC_CACHE_H_ */
|