[char-misc-next 06/27] mei: amthif: don't drop read packets on timeout
From: Alexander Usyskin <alexander.usyskin@intel.com> Since the driver now uses a list for storing read packets instead of single variable a pending
View Article[char-misc-next 07/27] mei: constify struct file pointer
The struct file file pointer is used as an opaque handle to for a connected client, for this part the pointer should be immutable and should be set to
View Article[char-misc-next 08/27] mei: rename variable names 'file_object' to fp
The driver uses three names file, fp, and file_object for struct file type. To improve code clarity and adjust to my taste rename file_object to more
View Article[char-misc-next 09/27] mei: amthif: allow only one request at a time
From: Alexander Usyskin <alexander.usyskin@intel.com> A next amthif write can be executed only after the previous one has completed. Signed-off-by:
View Article[char-misc-next 10/27] mei: amthif: replace amthif_rd_complete_list with...
Now when we have per client rd_completed list we can remove the amthif specific amthif_rd_complete_list. In addition in the function mei_amthif_read d
View Article[char-misc-next 11/27] mei: amthif: drop parameter validation from...
Remove duplicated parameter validation from mei_amthif_write functions, The parameter check is already performed by the caller function mei_write Sig
View Article[char-misc-next 12/27] mei: amthif: use rx_wait queue also for amthif client
From: Alexander Usyskin <alexander.usyskin@intel.com> Switch using cl->rx_wait wait queue also for amthif, there is nothing special about amthif in t
View Article[char-misc-next 13/27] mei: amthif: interrupt reader on link reset
From: Alexander Usyskin <alexander.usyskin@intel.com> In case of link reset all waiting readers should be interrupted. Signed-off-by: Alexander Usys
View Article[char-misc-next 14/27] mei: bus: fix RX event scheduling
In this particular case this more correct and safer to check if the RX event is set in the event mask rather than query waitqueue_active Since the che
View Article[char-misc-next 15/27] mei: bus: fix notification event delivery
Call wake_up cl->ev_wait only in case there is no bus client registered to the event notification. Second, since we don't have exclusive waiter wake_u
View Article[char-misc-next 16/27] mei: bus: check if the device is enabled before data...
From: Alexander Usyskin <alexander.usyskin@intel.com> The bus data transfer interface was missing the check if the device is in enabled state, this m
View Article[char-misc-next 17/27] mei: drop superfluous closing bracket from write traces
From: Alexander Usyskin <alexander.usyskin@intel.com> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com> Signed-off-by: Tomas Winkler <to
View Article[char-misc-next 18/27] mei: wake blocked write on link reset
From: Alexander Usyskin <alexander.usyskin@intel.com> In case of link reset all blocked writes should be interrupted. Note, that currently blocking w
View Article[char-misc-next 19/27] mei: clean write queues and wake waiters on disconnect
From: Alexander Usyskin <alexander.usyskin@intel.com> Clean write and write_waiting queues in disconnect. Requests in those queues are stale and proc
View Article[char-misc-next 20/27] mei: discard replies from unconnected fixed address...
From: Alexander Usyskin <alexander.usyskin@intel.com> A fixed address client in the FW doesn't have a notion of connection and can send message after
View Article[char-misc-next 21/27] mei: fill file pointer in read cb for fixed address...
From: Alexander Usyskin <alexander.usyskin@intel.com> The read callback created from a flow control request for a fixed address client have NULL in t
View Article[char-misc-next 22/27] mei: fixed address clients for the new platforms
From: Alexander Usyskin <alexander.usyskin@intel.com> Enable by default connection to fixed address clients from user-space for skylake and newer pla
View Article[char-misc-next 23/27] mei: hbm: warn about fw-initiated disconnect
From: Alexander Usyskin <alexander.usyskin@intel.com> The FW can initiate client disconnection only because an error condition, hence it make sense t
View Article[char-misc-next 24/27] mei: drop reserved host client ids
From: Alexander Usyskin <alexander.usyskin@intel.com> The reserved host clients can be obsoleted now, a portion of the platforms is shipped without i
View Article[char-misc-next 25/27] mei: bus: run rescan on me_clients list change
From: Alexander Usyskin <alexander.usyskin@intel.com> Since clients can be now added and removed during runtime we need to run bus rescan whenever me
View Article