<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/ralink, branch linux-5.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2025-10-29T13:01:17Z</updated>
<entry>
<title>wifi: rt2x00: use explicitly signed or unsigned types</title>
<updated>2025-10-29T13:01:17Z</updated>
<author>
<name>Jason A. Donenfeld</name>
</author>
<published>2022-10-19T15:55:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2da821b0b747150d92d4e2b7e48bac617ac1afd6'/>
<id>urn:sha1:2da821b0b747150d92d4e2b7e48bac617ac1afd6</id>
<content type='text'>
commit 66063033f77e10b985258126a97573f84bb8d3b4 upstream.

On some platforms, `char` is unsigned, but this driver, for the most
part, assumed it was signed. In other places, it uses `char` to mean an
unsigned number, but only in cases when the values are small. And in
still other places, `char` is used as a boolean. Put an end to this
confusion by declaring explicit types, depending on the context.

Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Cc: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Cc: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Cc: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Cc: Kalle Valo &lt;kvalo@kernel.org&gt;
Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/20221019155541.3410813-1-Jason@zx2c4.com
Signed-off-by: Eliav Farber &lt;farbere@amazon.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: restart beacon queue when hardware reset</title>
<updated>2024-02-23T07:42:05Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2023-11-04T08:58:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=69e905beca193125820c201ab3db4fb0e245124e'/>
<id>urn:sha1:69e905beca193125820c201ab3db4fb0e245124e</id>
<content type='text'>
[ Upstream commit a11d965a218f0cd95b13fe44d0bcd8a20ce134a8 ]

When a hardware reset is triggered, all registers are reset, so all
queues are forced to stop in hardware interface. However, mac80211
will not automatically stop the queue. If we don't manually stop the
beacon queue, the queue will be deadlocked and unable to start again.
This patch fixes the issue where Apple devices cannot connect to the
AP after calling ieee80211_restart_hw().

Signed-off-by: Shiji Yang &lt;yangshiji66@outlook.com&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/TYAP286MB031530EB6D98DCE4DF20766CBCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: correctly set BBP register 86 for MT7620</title>
<updated>2022-10-26T11:25:47Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-09-17T20:30:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4851303c853919f27310edec80181fd1c4185b41'/>
<id>urn:sha1:4851303c853919f27310edec80181fd1c4185b41</id>
<content type='text'>
[ Upstream commit c9aada64fe6493461127f1522d7e2f01792d2424 ]

Instead of 0 set the correct value for BBP register 86 for MT7620.

Reported-by: Serge Vasilugin &lt;vasilugin@yandex.ru&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/257267247ee4fa7ebc6a5d0c4948b3f8119c0d77.1663445157.git.daniel@makrotopia.org
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: set SoC wmac clock register</title>
<updated>2022-10-26T11:25:47Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-09-17T20:29:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a01614447954733a020ae15260d19f8e89a1ad1b'/>
<id>urn:sha1:a01614447954733a020ae15260d19f8e89a1ad1b</id>
<content type='text'>
[ Upstream commit cbde6ed406a51092d9e8a2df058f5f8490f27443 ]

Instead of using the default value 33 (pci), set US_CYC_CNT init based
on Programming guide:
If available, set chipset bus clock with fallback to cpu clock/3.

Reported-by: Serge Vasilugin &lt;vasilugin@yandex.ru&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/3e275d259f476f597dab91a9c395015ef3fe3284.1663445157.git.daniel@makrotopia.org
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: set VGC gain for both chains of MT7620</title>
<updated>2022-10-26T11:25:47Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-09-17T20:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5aa0461d11806599cf3b42bea1a3e68656bd0dd2'/>
<id>urn:sha1:5aa0461d11806599cf3b42bea1a3e68656bd0dd2</id>
<content type='text'>
[ Upstream commit 0e09768c085709e10ece3b68f6ac921d3f6a9caa ]

Set bbp66 for all chains of the MT7620.

Reported-by: Serge Vasilugin &lt;vasilugin@yandex.ru&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/29e161397e5c9d9399da0fe87d44458aa2b90a78.1663445157.git.daniel@makrotopia.org
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: set correct TX_SW_CFG1 MAC register for MT7620</title>
<updated>2022-10-26T11:25:47Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-09-17T20:29:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8d9c00979a7e1607b4403378cf016ecc118cbeea'/>
<id>urn:sha1:8d9c00979a7e1607b4403378cf016ecc118cbeea</id>
<content type='text'>
[ Upstream commit eeb50acf15762b61921f9df18663f839f387c054 ]

Set correct TX_SW_CFG1 MAC register as it is done also in v3 of the
vendor driver[1].

[1]: https://gitlab.com/dm38/padavan-ng/-/blob/master/trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/chips/rt6352.c#L531
Reported-by: Serge Vasilugin &lt;vasilugin@yandex.ru&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
Acked-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/4be38975ce600a34249e12d09a3cb758c6e71071.1663445157.git.daniel@makrotopia.org
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>wifi: rt2x00: don't run Rt5592 IQ calibration on MT7620</title>
<updated>2022-10-26T11:25:47Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2022-09-17T20:28:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=27ed98e8a9b053ef893e7191cbe1a73057928c57'/>
<id>urn:sha1:27ed98e8a9b053ef893e7191cbe1a73057928c57</id>
<content type='text'>
[ Upstream commit d3aad83d05aec0cfd7670cf0028f2ad4b81de92e ]

The function rt2800_iq_calibrate is intended for Rt5592 only.
Don't call it for MT7620 which has it's own calibration functions.

Reported-by: Serge Vasilugin &lt;vasilugin@yandex.ru&gt;
Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;
Link: https://lore.kernel.org/r/31a1c34ddbd296b82f38c18c9ae7339059215fdc.1663445157.git.daniel@makrotopia.org
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>rt2x00: do not mark device gone on EPROTO errors during start</title>
<updated>2021-12-08T08:03:20Z</updated>
<author>
<name>Stanislaw Gruszka</name>
</author>
<published>2021-11-11T14:10:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=de4f5eb02cfea68fcfe6b9dde7e0e1dde14043ea'/>
<id>urn:sha1:de4f5eb02cfea68fcfe6b9dde7e0e1dde14043ea</id>
<content type='text'>
commit ed53ae75693096f1c10b4561edd31a07b631bd72 upstream.

As reported by Exuvo is possible that we have lot's of EPROTO errors
during device start i.e. firmware load. But after that device works
correctly. Hence marking device gone by few EPROTO errors done by
commit e383c70474db ("rt2x00: check number of EPROTO errors") caused
regression - Exuvo device stop working after kernel update. To fix
disable the check during device start.

Link: https://lore.kernel.org/linux-wireless/bff7d309-a816-6a75-51b6-5928ef4f7a8c@exuvo.se/
Reported-and-tested-by: Exuvo &lt;exuvo@exuvo.se&gt;
Fixes: e383c70474db ("rt2x00: check number of EPROTO errors")
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Link: https://lore.kernel.org/r/20211111141003.GA134627@wp.pl
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rt2x00: convert tasklets to use new tasklet_setup() API</title>
<updated>2020-08-27T13:22:13Z</updated>
<author>
<name>Allen Pais</name>
</author>
<published>2020-08-17T09:06:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a0d6ea9b6e1cc4aef606bd8f3f098f7da4eb34d5'/>
<id>urn:sha1:a0d6ea9b6e1cc4aef606bd8f3f098f7da4eb34d5</id>
<content type='text'>
In preparation for unconditionally passing the
struct tasklet_struct pointer to all tasklet
callbacks, switch to using the new tasklet_setup()
and from_tasklet() to pass the tasklet pointer explicitly.

Signed-off-by: Romain Perier &lt;romain.perier@gmail.com&gt;
Signed-off-by: Allen Pais &lt;allen.lkml@gmail.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Link: https://lore.kernel.org/r/20200817090637.26887-15-allen.cryptic@gmail.com
</content>
</entry>
<entry>
<title>rt2x00: Use fallthrough pseudo-keyword</title>
<updated>2020-08-27T13:05:48Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2020-08-21T06:20:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74aad39490a7a63f634750744a7ff49c9eaddb0e'/>
<id>urn:sha1:74aad39490a7a63f634750744a7ff49c9eaddb0e</id>
<content type='text'>
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.

[1] https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through

Signed-off-by: Gustavo A. R. Silva &lt;gustavoars@kernel.org&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
Link: https://lore.kernel.org/r/20200821062052.GA8618@embeddedor
</content>
</entry>
</feed>
