Lines Matching +full:peci +full:- +full:controller
1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2018-2021 Intel Corporation */
13 * Currently we don't support any PECI command over 32 bytes.
21 * struct peci_controller_ops - PECI controller specific methods
22 * @xfer: PECI transfer function
24 * PECI controllers may have different hardware interfaces - the drivers
25 * implementing PECI controllers can use this structure to abstract away those
26 * differences by exposing a common interface for PECI core.
29 int (*xfer)(struct peci_controller *controller, u8 addr, struct peci_request *req);
33 * struct peci_controller - PECI controller
34 * @dev: device object to register PECI controller to the device model
35 * @ops: pointer to device specific controller operations
37 * @id: PECI controller ID
39 * PECI controllers usually connect to their drivers using non-PECI bus,
41 * Each PECI controller can communicate with one or more PECI devices.
59 * struct peci_device - PECI device
60 * @dev: device object to register PECI device to the device model
61 * @info: PECI device characteristics
62 * @info.x86_vfm: device vendor-family-model
63 * @info.peci_revision: PECI revision supported by the PECI device
64 * @info.socket_id: the socket ID represented by the PECI device
65 * @addr: address used on the PECI bus connected to the parent controller
66 * @deleted: indicates that PECI device was already deleted
68 * A peci_device identifies a single device (i.e. CPU) connected to a PECI bus.
69 * The behaviour exposed to the rest of the system is defined by the PECI driver
89 * struct peci_request - PECI request
90 * @device: PECI device to which the request is sent
98 * A peci_request represents a request issued by PECI originator (TX) and
99 * a response received from PECI responder (RX).