Lines Matching full:ec
25 * The EC is unresponsive for a time after a reboot command. Add a
41 * Command interface between EC and AP, for LPC, I2C and SPI interfaces.
58 * struct cros_ec_command - Information about a ChromeOS EC command.
62 * @insize: Max number of bytes to accept from the EC.
63 * @result: EC's response to the command (separate from communication failure).
64 * @data: Where to put the incoming data from EC and outgoing data to EC.
76 * struct cros_ec_device - Information about a ChromeOS EC device.
82 * @cmd_readmem: Direct read of the EC memory-mapped region, if supported.
95 * @din: Input buffer (for data from EC). This buffer will always be
101 * @dout: Output buffer (for data to EC). This buffer will always be
111 * @cmd_xfer: Send command to EC and get response.
113 * succeeded, but that doesn't mean the EC was happy with the
114 * command. The caller should check msg.result for the EC's result
116 * @pkt_xfer: Send packet to EC and get response.
121 * @host_sleep_v1: True if this EC supports the sleep v1 command.
128 * @notifier_ready: The notifier_block to let the kernel re-query EC
129 * communication protocol when the EC sends
131 * @ec: The platform_device used by the mfd driver to interface with the
132 * main EC.
134 * PD behind an EC.
137 /* These are used by other drivers that want to talk to the EC */
142 int (*cmd_readmem)(struct cros_ec_device *ec, unsigned int offset,
158 int (*cmd_xfer)(struct cros_ec_device *ec,
160 int (*pkt_xfer)(struct cros_ec_device *ec,
175 struct platform_device *ec; member
180 * struct cros_ec_platform - ChromeOS EC platform information.
181 * @ec_name: Name of EC device (e.g. 'cros-ec', 'cros-pd', ...)
192 * struct cros_ec_dev - ChromeOS EC device entry point.
197 * @has_kb_wake_angle: True if at least 2 accelerometer are connected to the EC.
199 * @features: Features supported by the EC.
230 int cros_ec_check_features(struct cros_ec_dev *ec, int feature);
232 int cros_ec_get_sensor_count(struct cros_ec_dev *ec);