<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/misc/mei, branch linux-4.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2015-07-21T17:10:12Z</updated>
<entry>
<title>mei: txe: reduce suspend/resume time</title>
<updated>2015-07-21T17:10:12Z</updated>
<author>
<name>Tomas Winkler</name>
</author>
<published>2015-04-14T07:27:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b9b02403177dd9743a8536ffadcac00c782bc302'/>
<id>urn:sha1:b9b02403177dd9743a8536ffadcac00c782bc302</id>
<content type='text'>
commit fe292283c23329218e384bffc6cb4bfa3fd92277 upstream.

HW has to be in known state before the initialisation
sequence is started. The polling step for settling aliveness
was set to 200ms while in practise this can be done in up to 30msecs.

Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Barak Yoresh &lt;barak.yoresh@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mei: me: wait for power gating exit confirmation</title>
<updated>2015-07-21T17:10:12Z</updated>
<author>
<name>Alexander Usyskin</name>
</author>
<published>2015-06-13T05:51:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8a9c48f2527b57add3210e9c737e4708aed8a952'/>
<id>urn:sha1:8a9c48f2527b57add3210e9c737e4708aed8a952</id>
<content type='text'>
commit 3dc196eae1db548f05e53e5875ff87b8ff79f249 upstream.

Fix the hbm power gating state machine so it will wait till it receives
confirmation interrupt for the PG_ISOLATION_EXIT message.

In process of the suspend flow the devices first have to exit from the
power gating state (runtime pm resume).
If we do not handle the confirmation interrupt after sending
PG_ISOLATION_EXIT message, we may receive it already after the suspend
flow has changed the device state and interrupt will be interpreted as a
spurious event, consequently link reset will be invoked which will
prevent the device from completing the suspend flow

kernel: [6603] mei_reset:136: mei_me 0000:00:16.0: powering down: end of reset
kernel: [476] mei_me_irq_thread_handler:643: mei_me 0000:00:16.0: function called after ISR to handle the interrupt processing.
kernel: mei_me 0000:00:16.0: FW not ready: resetting

Cc: Gabriele Mazzotta &lt;gabriele.mzt@gmail.com&gt;
Link: https://bugzilla.kernel.org/show_bug.cgi?id=86241
Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770397
Tested-by: Gabriele Mazzotta &lt;gabriele.mzt@gmail.com&gt;
Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mei: make device disabled on stop unconditionally</title>
<updated>2015-03-02T03:34:50Z</updated>
<author>
<name>Alexander Usyskin</name>
</author>
<published>2015-02-10T08:36:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6c15a8516b8118eb19a59fd0bd22df41b9101c32'/>
<id>urn:sha1:6c15a8516b8118eb19a59fd0bd22df41b9101c32</id>
<content type='text'>
Set the internal device state to to disabled after hardware reset in stop flow.
This will cover cases when driver was not brought to disabled state because of
an error and in stop flow we wish not to retry the reset.

Cc: &lt;stable@vger.kernel.org&gt; #3.10+
Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: me: release hw from reset only during the reset flow</title>
<updated>2015-02-03T23:48:51Z</updated>
<author>
<name>Alexander Usyskin</name>
</author>
<published>2015-01-25T21:45:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=663b7ee9517eec6deea9a48c7a1392a9a34f7809'/>
<id>urn:sha1:663b7ee9517eec6deea9a48c7a1392a9a34f7809</id>
<content type='text'>
We might enter the interrupt handler with hw_ready already set,
but prior we actually started the reset flow.
To soleve this we move the reset release from the interrupt handler
to the HW start wait function which is part of the reset sequence.

Cc: &lt;stable@vger.kernel.org&gt; #3.10+
Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: mask interrupt set bit on clean reset bit</title>
<updated>2015-02-03T23:48:51Z</updated>
<author>
<name>Alexander Usyskin</name>
</author>
<published>2015-01-25T21:45:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ab1e79b9fd4b01331490bbe2e630a0fc0b25449'/>
<id>urn:sha1:1ab1e79b9fd4b01331490bbe2e630a0fc0b25449</id>
<content type='text'>
We should mask interrupt set bit when writing back
hcsr value in reset bit clean-up.

This is refinement for
mei: clean reset bit before reset
commit b13a65ef190e488e2761d65bdd2e1fe8a3a125f5

Cc: &lt;stable@vger.kernel.org&gt; #3.10+
Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: add reference counting for me clients</title>
<updated>2015-01-25T17:17:56Z</updated>
<author>
<name>Tomas Winkler</name>
</author>
<published>2015-01-10T22:07:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=79563db9ddd37908343103debf20da716ccc5ce4'/>
<id>urn:sha1:79563db9ddd37908343103debf20da716ccc5ce4</id>
<content type='text'>
To support dynamic addition and removal of
me clients we add reference counter.

Update kdoc with locking requirements.

Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge 3.19-rc5 into char-misc-next</title>
<updated>2015-01-18T22:56:57Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2015-01-18T22:56:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3542f6b1836d8940615104e22248bb9b7cf54f5f'/>
<id>urn:sha1:3542f6b1836d8940615104e22248bb9b7cf54f5f</id>
<content type='text'>
We want the 3.19-rc5 fixes in here for our testing.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: use uuid, me_addr tuple addressing also for flow control credits</title>
<updated>2015-01-12T13:04:10Z</updated>
<author>
<name>Tomas Winkler</name>
</author>
<published>2014-12-07T14:40:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2e5df413becf6bd3854d1eb4f96542a53848bb27'/>
<id>urn:sha1:2e5df413becf6bd3854d1eb4f96542a53848bb27</id>
<content type='text'>
Add uuid, me_addr addressing also for flow control credits.
The only exception in cases for single buffer clients for which
the host address in flow credits response is always 0

To in order to deal with add/remove race between fw and driver clients
addressing we need to use [uuid, me_addr] tuple to address the clients

Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: bus: use ssize_t as the return type for send and receive</title>
<updated>2015-01-12T13:04:10Z</updated>
<author>
<name>Tomas Winkler</name>
</author>
<published>2014-11-27T12:07:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39db74ce1aa83626a0a70ed2abf29a17598fff49'/>
<id>urn:sha1:39db74ce1aa83626a0a70ed2abf29a17598fff49</id>
<content type='text'>
Mei bus receive and send function may return either number
of transmitted bytes or errno.  It is better to use ssize_t
type for that purpose that mixing size_t with int.

Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mei: clean reset bit before reset</title>
<updated>2015-01-09T22:53:13Z</updated>
<author>
<name>Alexander Usyskin</name>
</author>
<published>2014-12-24T22:37:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b13a65ef190e488e2761d65bdd2e1fe8a3a125f5'/>
<id>urn:sha1:b13a65ef190e488e2761d65bdd2e1fe8a3a125f5</id>
<content type='text'>
H_RST bit in H_CSR register may be found lit before reset is started,
for example if preceding reset flow hasn't completed.
In that case asserting H_RST will be ignored, therefore we need to clean
H_RST bit to start a successful reset sequence.

Cc: &lt;stable@vger.kernel.org&gt; #3.10+
Signed-off-by: Alexander Usyskin &lt;alexander.usyskin@intel.com&gt;
Signed-off-by: Tomas Winkler &lt;tomas.winkler@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
