1/* 2 * NVEC: NVIDIA compliant embedded controller interface 3 * 4 * Copyright (C) 2011 The AC100 Kernel Team <ac100@lists.launchpad.net> 5 * 6 * Authors: Pierre-Hugues Husson <phhusson@free.fr> 7 * Ilya Petrov <ilya.muromec@gmail.com> 8 * Marc Dietrich <marvin24@gmx.de> 9 * Julian Andres Klode <jak@jak-linux.org> 10 * 11 * This file is subject to the terms and conditions of the GNU General Public 12 * License. See the file "COPYING" in the main directory of this archive 13 * for more details. 14 * 15 */ 16 17#ifndef __LINUX_MFD_NVEC 18#define __LINUX_MFD_NVEC 19 20#include <linux/atomic.h> 21#include <linux/clk.h> 22#include <linux/completion.h> 23#include <linux/list.h> 24#include <linux/mutex.h> 25#include <linux/notifier.h> 26#include <linux/spinlock.h> 27#include <linux/workqueue.h> 28 29/* NVEC_POOL_SIZE - Size of the pool in &struct nvec_msg */ 30#define NVEC_POOL_SIZE 64 31 32/* 33 * NVEC_MSG_SIZE - Maximum size of the data field of &struct nvec_msg. 34 * 35 * A message must store up to a SMBus block operation which consists of 36 * one command byte, one count byte, and up to 32 payload bytes = 34 37 * byte. 38 */ 39#define NVEC_MSG_SIZE 34 40 41/** 42 * enum nvec_event_size - The size of an event message 43 * @NVEC_2BYTES: The message has one command byte and one data byte 44 * @NVEC_3BYTES: The message has one command byte and two data bytes 45 * @NVEC_VAR_SIZE: The message has one command byte, one count byte, and has 46 * up to as many bytes as the number in the count byte. The 47 * maximum is 32 48 * 49 * Events can be fixed or variable sized. This is useless on other message 50 * types, which are always variable sized. 51 */ 52enum nvec_event_size { 53 NVEC_2BYTES, 54 NVEC_3BYTES, 55 NVEC_VAR_SIZE, 56}; 57 58/** 59 * enum nvec_msg_type - The type of a message 60 * @NVEC_SYS: A system request/response 61 * @NVEC_BAT: A battery request/response 62 * @NVEC_KBD: A keyboard request/response 63 * @NVEC_PS2: A mouse request/response 64 * @NVEC_CNTL: A EC control request/response 65 * @NVEC_KB_EVT: An event from the keyboard 66 * @NVEC_PS2_EVT: An event from the mouse 67 * 68 * Events can be fixed or variable sized. This is useless on other message 69 * types, which are always variable sized. 70 */ 71enum nvec_msg_type { 72 NVEC_SYS = 1, 73 NVEC_BAT, 74 NVEC_GPIO, 75 NVEC_SLEEP, 76 NVEC_KBD, 77 NVEC_PS2, 78 NVEC_CNTL, 79 NVEC_OEM0 = 0x0d, 80 NVEC_KB_EVT = 0x80, 81 NVEC_PS2_EVT, 82}; 83 84/** 85 * struct nvec_msg - A buffer for a single message 86 * @node: Messages are part of various lists in a &struct nvec_chip 87 * @data: The data of the message 88 * @size: For TX messages, the number of bytes used in @data 89 * @pos: For RX messages, the current position to write to. For TX messages, 90 * the position to read from. 91 * @used: Used for the message pool to mark a message as free/allocated. 92 * 93 * This structure is used to hold outgoing and incoming messages. Outgoing 94 * messages have a different format than incoming messages, and that is not 95 * documented yet. 96 */ 97struct nvec_msg { 98 struct list_head node; 99 unsigned char data[NVEC_MSG_SIZE]; 100 unsigned short size; 101 unsigned short pos; 102 atomic_t used; 103}; 104 105/** 106 * struct nvec_chip - A single connection to an NVIDIA Embedded controller 107 * @dev: The device 108 * @gpio: The same as for &struct nvec_platform_data 109 * @irq: The IRQ of the I2C device 110 * @i2c_addr: The address of the I2C slave 111 * @base: The base of the memory mapped region of the I2C device 112 * @clk: The clock of the I2C device 113 * @notifier_list: Notifiers to be called on received messages, see 114 * nvec_register_notifier() 115 * @rx_data: Received messages that have to be processed 116 * @tx_data: Messages waiting to be sent to the controller 117 * @nvec_status_notifier: Internal notifier (see nvec_status_notifier()) 118 * @rx_work: A work structure for the RX worker nvec_dispatch() 119 * @tx_work: A work structure for the TX worker nvec_request_master() 120 * @wq: The work queue in which @rx_work and @tx_work are executed 121 * @rx: The message currently being retrieved or %NULL 122 * @msg_pool: A pool of messages for allocation 123 * @tx: The message currently being transferred 124 * @tx_scratch: Used for building pseudo messages 125 * @ec_transfer: A completion that will be completed once a message has been 126 * received (see nvec_rx_completed()) 127 * @tx_lock: Spinlock for modifications on @tx_data 128 * @rx_lock: Spinlock for modifications on @rx_data 129 * @sync_write_mutex: A mutex for nvec_write_sync() 130 * @sync_write: A completion to signal that a synchronous message is complete 131 * @sync_write_pending: The first two bytes of the request (type and subtype) 132 * @last_sync_msg: The last synchronous message. 133 * @state: State of our finite state machine used in nvec_interrupt() 134 */ 135struct nvec_chip { 136 struct device *dev; 137 int gpio; 138 int irq; 139 int i2c_addr; 140 void __iomem *base; 141 struct clk *i2c_clk; 142 struct atomic_notifier_head notifier_list; 143 struct list_head rx_data, tx_data; 144 struct notifier_block nvec_status_notifier; 145 struct work_struct rx_work, tx_work; 146 struct workqueue_struct *wq; 147 struct nvec_msg msg_pool[NVEC_POOL_SIZE]; 148 struct nvec_msg *rx; 149 150 struct nvec_msg *tx; 151 struct nvec_msg tx_scratch; 152 struct completion ec_transfer; 153 154 spinlock_t tx_lock, rx_lock; 155 156 /* sync write stuff */ 157 struct mutex sync_write_mutex; 158 struct completion sync_write; 159 u16 sync_write_pending; 160 struct nvec_msg *last_sync_msg; 161 162 int state; 163}; 164 165extern int nvec_write_async(struct nvec_chip *nvec, const unsigned char *data, 166 short size); 167 168extern struct nvec_msg *nvec_write_sync(struct nvec_chip *nvec, 169 const unsigned char *data, short size); 170 171extern int nvec_register_notifier(struct nvec_chip *nvec, 172 struct notifier_block *nb, 173 unsigned int events); 174 175extern int nvec_unregister_notifier(struct nvec_chip *dev, 176 struct notifier_block *nb); 177 178extern void nvec_msg_free(struct nvec_chip *nvec, struct nvec_msg *msg); 179 180#endif 181