Lines Matching full:backend
25 * These values may be written to storage (see EFI vars backend), so
52 * @psi: pstore backend driver information
60 * @priv: pointer for backend specific use, will be
89 * struct pstore_info - backend pstore driver structure
91 * @owner: module which is responsible for this backend driver
92 * @name: name of the backend driver
98 * backend entry, since compressed bytes don't take kindly
102 * @flags: bitfield of frontends the backend can accept writes for
109 * @data: backend-private pointer passed back during callbacks
114 * Notify backend that pstore is starting a full read of backend
117 * @psi: in: pointer to the struct pstore_info for the backend
122 * Notify backend that pstore has finished a full read of backend
126 * @psi: in: pointer to the struct pstore_info for the backend
132 * Read next available backend record. Called after a successful
137 * by the backend and filled. At least @type and @id should
145 * A newly generated record needs to be written to backend storage.
152 * backend is also expected to write @id with something that
161 * Perform a frontend write to a backend record, using a specified
166 * @buf: pointer to userspace contents to write to backend
171 * Delete a record from backend storage. Different backends
173 * passed back to assist in identification of what the backend