linux-toradex.git/drivers/misc/mei/Makefile, branch v4.12-rc1

mei: drop amthif internal client

2017-04-08T15:38:25+00:00

AMTHIF has special support in the mei drive, it handles multiplexing
multiple user space connection above single me client connection.
Since there is no additional addressing information there is a strict
requirement on the traffic order on each connection and on the "read
after write" order within the connection. This creates a lot of
complexity mostly because the other client types do not necessarily fall
under the same restriction.    After carefully studying the use of the
AMTHIF client, we came to conclusion that the multiplexing is not really
utilized by any application and we may safely remove that support and
significantly simplify the driver.

Signed-off-by: Alexander Usyskin 
Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: wd: drop the watchdog code from the core mei driver

2016-02-07T06:11:06+00:00

Instead of integrating the iAMT watchdog in the mei core driver
we will create a watchdog device on the mei client bus and
create a driver for it.

This patch removes the watchdog code from the mei core driver.

Signed-off-by: Alexander Usyskin 
Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: bus: rename nfc.c to bus-fixup.c

2015-08-04T00:20:26+00:00

The bus-fixup.c will be a place for fixups and quirks
for all types of me client devices.
As for now it contians only the fixup for setting
the nfc device name on the me client bus.

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: me: add io register tracing

2015-03-02T03:36:59+00:00

To make debugging a bit easier we add me register
access tracing
/tracing/events/mei/mei_reg_{read,write}

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: txe: add Kbuild for TXE device

2014-02-07T23:08:46+00:00

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: nfc: Initial nfc implementation

2013-04-11T01:56:53+00:00

NFC ME device is exported through the MEI bus to be consumed by the
NFC subsystem.

NFC is represented by two mei clients: An info one and the actual
NFC one. In order to properly build the ME id we first need to retrieve
the firmware information from the info client and then disconnect from it.

Signed-off-by: Samuel Ortiz 
Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: add debugfs hooks

2013-04-05T22:49:17+00:00

debugfs exposes device state and list of me clients and their
properties

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: bus: Initial MEI Client bus type implementation

2013-03-29T15:35:47+00:00

mei client bus will present some of the mei clients
as devices for other standard subsystems

Implement the probe, remove, match, device addtion routines, along with
the sysfs and uevent ones. mei_cl_device_id is also added to
mod_devicetable.h
A mei-cleint-bus.txt document describing the rationale and the API usage
is also added while ABI/testing/sysfs-bus-mei describeis the modalias ABI.

Signed-off-by: Samuel Ortiz 
Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: move mei-me to separate module

2013-03-29T15:32:21+00:00

mei layer provides host bus message layer, client management,
and os interface

mei-me - provides access to ME hardware through
the pci bus

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman

mei: separate compilation of the ME hardware specifics

2013-02-06T19:23:47+00:00

We add struct mei_hw_ops to virtualize access to hw specific
configurations. This allows us to separate the compilation
of the ME interface from the ME hardware specifics

Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman