Lines Matching full:ec
29 * The EC is unresponsive for a time after a reboot command. Add a
45 * Command interface between EC and AP, for LPC, I2C and SPI interfaces.
62 * struct cros_ec_command - Information about a ChromeOS EC command.
66 * @insize: Max number of bytes to accept from the EC.
67 * @result: EC's response to the command (separate from communication failure).
68 * @data: Where to put the incoming data from EC and outgoing data to EC.
80 * struct cros_ec_device - Information about a ChromeOS EC device.
84 * @cmd_readmem: Direct read of the EC memory-mapped region, if supported.
97 * @din: Input buffer (for data from EC). This buffer will always be
103 * @dout: Output buffer (for data to EC). This buffer will always be
113 * @cmd_xfer: Send command to EC and get response.
115 * succeeded, but that doesn't mean the EC was happy with the
116 * command. The caller should check msg.result for the EC's result
118 * @pkt_xfer: Send packet to EC and get response.
123 * @host_sleep_v1: True if this EC supports the sleep v1 command.
130 * @notifier_ready: The notifier_block to let the kernel re-query EC
131 * communication protocol when the EC sends
133 * @ec: The platform_device used by the mfd driver to interface with the
134 * main EC.
136 * PD behind an EC.
139 /* These are used by other drivers that want to talk to the EC */
143 int (*cmd_readmem)(struct cros_ec_device *ec, unsigned int offset,
159 int (*cmd_xfer)(struct cros_ec_device *ec,
161 int (*pkt_xfer)(struct cros_ec_device *ec,
177 struct platform_device *ec; member
182 * struct cros_ec_platform - ChromeOS EC platform information.
183 * @ec_name: Name of EC device (e.g. 'cros-ec', 'cros-pd', ...)
194 * struct cros_ec_dev - ChromeOS EC device entry point.
199 * @has_kb_wake_angle: True if at least 2 accelerometer are connected to the EC.
201 * @features: Features supported by the EC.
235 bool cros_ec_check_features(struct cros_ec_dev *ec, int feature);
237 int cros_ec_get_sensor_count(struct cros_ec_dev *ec);