Lines Matching full:backend
25 * These values may be written to storage (see EFI vars backend), so
52 * @psi: pstore backend driver information
85 * struct pstore_info - backend pstore driver structure
87 * @owner: module which is responsible for this backend driver
88 * @name: name of the backend driver
94 * backend entry, since compressed bytes don't take kindly
98 * @flags: bitfield of frontends the backend can accept writes for
105 * @data: backend-private pointer passed back during callbacks
110 * Notify backend that pstore is starting a full read of backend
113 * @psi: in: pointer to the struct pstore_info for the backend
118 * Notify backend that pstore has finished a full read of backend
122 * @psi: in: pointer to the struct pstore_info for the backend
128 * Read next available backend record. Called after a successful
133 * by the backend and filled. At least @type and @id should
141 * A newly generated record needs to be written to backend storage.
148 * backend is also expected to write @id with something that
157 * Perform a frontend write to a backend record, using a specified
162 * @buf: pointer to userspace contents to write to backend
167 * Delete a record from backend storage. Different backends
169 * passed back to assist in identification of what the backend