1. 16 3月, 2013 1 次提交
    • T
      mei: ME hardware reset needs to be synchronized · 68f8ea18
      Tomas Winkler 提交于
      This fixes failure during initialization on Lynx Point LP devices.
      
      ME driver needs to release the device from the reset
      only after the FW has completed its flow and indicated
      it by delivering an interrupt to the host.
      
      This is the correct behavior for all the ME devices yet the
      the previous versions are less susceptive to the implementation
      that ignored FW reset completion indication.
      
      We add mei_me_hw_reset_release function which is called
      after reset from the interrupt thread or directly
      from mei_reset during power down.
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      68f8ea18
  2. 07 2月, 2013 4 次提交
  3. 18 1月, 2013 1 次提交
  4. 09 1月, 2013 8 次提交
  5. 08 1月, 2013 5 次提交
  6. 22 11月, 2012 1 次提交
  7. 16 11月, 2012 1 次提交
  8. 11 7月, 2012 1 次提交
  9. 27 6月, 2012 2 次提交
  10. 21 6月, 2012 1 次提交
  11. 10 5月, 2012 1 次提交
  12. 02 5月, 2012 1 次提交
  13. 15 3月, 2012 1 次提交
  14. 14 3月, 2012 1 次提交
  15. 01 3月, 2012 1 次提交
  16. 10 2月, 2012 2 次提交
  17. 14 12月, 2011 1 次提交
  18. 17 9月, 2011 1 次提交
  19. 29 6月, 2011 2 次提交
  20. 18 5月, 2011 1 次提交
    • O
      staging/mei: MEI link layer · 3ce72726
      Oren Weil 提交于
      Implementation of the communication between host and ME.
      connect/disconnect to/from a client, send MEI message,
      read MEI message, flow control handling.
      
      Each MEI message has mei_msg_hdr followed by a payload.
      Driver is oblivious the payload.
      
      ME Address/ID 	- This is the logical address of the ME
      		feature/client of that message.
      Host Address/ID	- This is the logical address of the Host
      		  client of that message
      Length 		- This is the Length of message payload in bytes
      Reserved 	-  reserved for future use.
      Message Complete - This bit is used to indicative that
      		this is the last message of multi message
      		MEI transfer of a client message that is larger
      		then the MEI circular buffer.
      Payload		- Message payload (data) up to 512bytes
      
      The HW data registers are consist two circular buffers,
      one for data from ME and other data from Host application.
      Each buffer has two pointers, read_ptr (H_CBRP)
      and write_ptr (H_CBWP).
      The buffers size is defined by depth value that exists
      in the status registers (H_CBD and ME_CBD_HRA).
      Every read from ME circular buffer cause read_ptr++
      Every write to the Host  circular buffer write_ptr++
      
      Flow control MEI message that ME and MEI Driver use to notify
      each other that a ME feature/client or Host client buffer is ready
      to receive data.
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: NItzhak Tzeel-Krupp <itzhak.tzeel-krupp@intel.com>
      Signed-off-by: NOren Weil <oren.jer.weil@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      3ce72726