<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/net/wireless/quantenna, branch dev-4.17</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.17</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.17'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2018-08-03T05:47:58+00:00</updated>
<entry>
<title>qtnfmac: pearl: pcie: fix memory leak in qtnf_fw_work_handler</title>
<updated>2018-08-03T05:47:58+00:00</updated>
<author>
<name>Gustavo A. R. Silva</name>
<email>gustavo@embeddedor.com</email>
</author>
<published>2018-04-05T15:49:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=de152d298fddfa4a3493967bd0e810f0da8d3a43'/>
<id>urn:sha1:de152d298fddfa4a3493967bd0e810f0da8d3a43</id>
<content type='text'>
[ Upstream commit 3763770044640caeb1101cdea40697cc0814403c ]

In case memory resources for fw were succesfully allocated, release
them before jumping to fw_load_fail.

Addresses-Coverity-ID: 1466092 ("Resource leak")
Fixes: c3b2f7ca4186 ("qtnfmac: implement asynchronous firmware loading")
Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Reviewed-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: fix invalid STA state on EAPOL failure</title>
<updated>2018-08-03T05:47:41+00:00</updated>
<author>
<name>Sergey Matyukevich</name>
<email>sergey.matyukevich.os@quantenna.com</email>
</author>
<published>2018-05-29T12:00:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f79fe4592f95b78047009b97eaf966dd6cd1f41a'/>
<id>urn:sha1:f79fe4592f95b78047009b97eaf966dd6cd1f41a</id>
<content type='text'>
[ Upstream commit 480daa9cb62c14bbd1b87a01cd9bc10cc56dbf32 ]

Driver switches vif sta_state into QTNF_STA_CONNECTING when cfg80211
core initiates connect procedure. Further this state is changed either
to QTNF_STA_CONNECTED or to QTNF_STA_DISCONNECTED by BSS_JOIN and
BSS_LEAVE events from firmware. However it is possible that no such
events will be sent by firmware, e.g. if EAPOL timed out.

In this case vif sta_mode will remain in QTNF_STA_CONNECTING state and
all subsequent connection attempts will fail with -EBUSY error code.
Fix this by perfroming STA state transition from QTNF_STA_CONNECTING
to QTNF_STA_DISCONNECTED in cfg80211 disconnect callback.
No need to rely upon firmware events in this case.

Signed-off-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net/wireless: fix spaces and grammar copy/paste in vendor Kconfig help text</title>
<updated>2018-03-13T16:52:25+00:00</updated>
<author>
<name>Randy Dunlap</name>
<email>rdunlap@infradead.org</email>
</author>
<published>2018-03-03T02:03:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a6cf02e6485a80ec0f708e1f72ee95abc3426b84'/>
<id>urn:sha1:a6cf02e6485a80ec0f708e1f72ee95abc3426b84</id>
<content type='text'>
Lots of the wireless driver vendor Kconfig symol help text says
"questions about  cards." (2 spaces between "about" and "cards")

Besides dropping one of those spaces, it also needs some other word
inserted there. Instead of putting each vendor's name there, I chose
to say "these" cards in all of the Kconfig help text.

Cc: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: implement asynchronous firmware loading</title>
<updated>2018-02-27T16:18:43+00:00</updated>
<author>
<name>Sergey Matyukevich</name>
<email>sergey.matyukevich.os@quantenna.com</email>
</author>
<published>2018-02-10T14:04:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c3b2f7ca4186cad3584915eba10d2085c3eed029'/>
<id>urn:sha1:c3b2f7ca4186cad3584915eba10d2085c3eed029</id>
<content type='text'>
In pci probe() function start firmware loading, protocol handshake
and driver core initialization, and not wait for completion.

Signed-off-by: Sergei Maksimenko &lt;smaksimenko@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: enable reloading of qtnfmac kernel modules</title>
<updated>2018-02-27T16:18:43+00:00</updated>
<author>
<name>Sergei Maksimenko</name>
<email>smaksimenko@quantenna.com</email>
</author>
<published>2018-02-10T14:04:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a34d7bcb73f553f1ea65eeff744c66e77b167175'/>
<id>urn:sha1:a34d7bcb73f553f1ea65eeff744c66e77b167175</id>
<content type='text'>
This patch enables rmmod/insmod for qtnfmac kernel modules:
- do not 'pin' pci device in order to disable it on module unload
- implement card reset procedure
- restore PCI bar addresses for restarted wireless card

Signed-off-by: Sergei Maksimenko &lt;smaksimenko@quantenna.com&gt;
Signed-off-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: fix releasing Tx/Rx data buffers</title>
<updated>2018-02-27T16:18:42+00:00</updated>
<author>
<name>Sergey Matyukevich</name>
<email>sergey.matyukevich.os@quantenna.com</email>
</author>
<published>2018-02-10T14:04:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1d5e3b90ab0160375d15dd8f322c1bfdb8a83e1e'/>
<id>urn:sha1:1d5e3b90ab0160375d15dd8f322c1bfdb8a83e1e</id>
<content type='text'>
Add missing PCI unmap for Tx buffers and release all buffers explicitly.
Managed release using devm_add_action is not suitable for qtnfmac Tx/Rx
data buffers. The reason is in ordering and dependencies: buffers
should be released after transmission is stopped but before PCI
device resources and DMA allocations are released.

Signed-off-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: remove redundant 'unlikely' checks</title>
<updated>2018-01-24T16:01:02+00:00</updated>
<author>
<name>Sergey Matyukevich</name>
<email>sergey.matyukevich.os@quantenna.com</email>
</author>
<published>2018-01-22T12:46:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c93fe71c91d0ae9eb6a82e887cd076c51d647d5f'/>
<id>urn:sha1:c93fe71c91d0ae9eb6a82e887cd076c51d647d5f</id>
<content type='text'>
Signed-off-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: do not use bus mutex for events processing</title>
<updated>2018-01-24T16:00:55+00:00</updated>
<author>
<name>Igor Mitsyanko</name>
<email>igor.mitsyanko.os@quantenna.com</email>
</author>
<published>2018-01-22T12:46:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=237d29f6ce46a37908e5c1e0b29520ae8ee7c8f0'/>
<id>urn:sha1:237d29f6ce46a37908e5c1e0b29520ae8ee7c8f0</id>
<content type='text'>
Events processing requires locking of bus mutex, which is also used by
cfg80211 layer before calling several of cfg80211 callbacks. Since all
cfg80211 callbacks in qtnfmac driver also lock bus mutex, this
potentially may lead to a deadlock.

Do not use bus lock for event processing. Use RTNL lock instead to
serialize events and commands processing threads.

Signed-off-by: Igor Mitsyanko &lt;igor.mitsyanko.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: do not use mutexes in timer context</title>
<updated>2018-01-24T16:00:54+00:00</updated>
<author>
<name>Igor Mitsyanko</name>
<email>igor.mitsyanko.os@quantenna.com</email>
</author>
<published>2018-01-22T12:46:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f2cddd5469b0e2284fa92f7013f6dc99debb3968'/>
<id>urn:sha1:f2cddd5469b0e2284fa92f7013f6dc99debb3968</id>
<content type='text'>
The function qtnf_scan_done makes use of mutexes which is wrong
since it may be called from timer context. Move scan timeout
handler from timer to deferred work.

Signed-off-by: Igor Mitsyanko &lt;igor.mitsyanko.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>qtnfmac: fix STA disconnect procedure</title>
<updated>2018-01-24T16:00:50+00:00</updated>
<author>
<name>Sergey Matyukevich</name>
<email>sergey.matyukevich.os@quantenna.com</email>
</author>
<published>2018-01-22T12:46:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=39845020b39eea4a1e5db9ea4818a967b567e2e2'/>
<id>urn:sha1:39845020b39eea4a1e5db9ea4818a967b567e2e2</id>
<content type='text'>
STA does not reconnect to the same AP after disconnect. The reason is
that STA is marked as disconnected in cfg80211 disconnect callback.
This is too early since in this case qtnfmac event handler skips
cfg80211_disconnected call when processing disconnect event from
the card. As a result, wdev is left in an inconsistent state.

Signed-off-by: Sergey Matyukevich &lt;sergey.matyukevich.os@quantenna.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
</feed>
