Lines Matching full:backend
25 * These values may be written to storage (see EFI vars backend), so
54 * @psi: pstore backend driver information
87 * struct pstore_info - backend pstore driver structure
89 * @owner: module which is responsible for this backend driver
90 * @name: name of the backend driver
96 * backend entry, since compressed bytes don't take kindly
100 * @flags: bitfield of frontends the backend can accept writes for
107 * @data: backend-private pointer passed back during callbacks
112 * Notify backend that pstore is starting a full read of backend
115 * @psi: in: pointer to the struct pstore_info for the backend
120 * Notify backend that pstore has finished a full read of backend
124 * @psi: in: pointer to the struct pstore_info for the backend
130 * Read next available backend record. Called after a successful
135 * by the backend and filled. At least @type and @id should
143 * A newly generated record needs to be written to backend storage.
150 * backend is also expected to write @id with something that
159 * Perform a frontend write to a backend record, using a specified
164 * @buf: pointer to userspace contents to write to backend
169 * Delete a record from backend storage. Different backends
171 * passed back to assist in identification of what the backend