- Jan 10, 2024
-
-
Martin Kaistra authored
Until now, the driver only assigned a dedicated macid for connections made in AP mode, in STA mode the return value of rtl8xxxu_get_macid() was simply 0. To differentiate between port 0 and 1, when both are in STA mode, allocate a second macid (with value 1) and set sta_info->macid according to the used port_num in rtl8xxxu_sta_add(). Signed-off-by:
Martin Kaistra <martin.kaistra@linutronix.de> Reviewed-by:
Ping-Ke Shih <pkshih@realtek.com> Signed-off-by:
Kalle Valo <kvalo@kernel.org> Link: https://msgid.link/20231222101442.626837-18-martin.kaistra@linutronix.de
-
Martin Kaistra authored
Call set_bssid() with the correct port_num now. Signed-off-by:
-
Martin Kaistra authored
Call set_linktype and set_bssid now with correct port_num. Call stop_tx_beacon only for port 0, as we don't support beacons on port 1. Explicit changes to BEACON will only happen for AP type interfaces, so we don't need an additional check there. Signed-off-by:
-
Martin Kaistra authored
Add a custom struct to store in vif->drv_priv with a reference to port_num and fill it when a new interface is added. Choose a free port_num for the newly added interface. As we only want to support AP mode/sending beacons on port 0, only change the beacon settings if a new interface is actually assigned to port 0. Call set_linktype() and set_mac() with the appropriate port_num. Signed-off-by:
-
Martin Kaistra authored
Check first whether priv->vifs[0] exists and is of type STATION, then go to priv->vifs[1]. Make sure to call refresh_rate_mask for both interfaces. Signed-off-by:
-
Martin Kaistra authored
As we only want to support AP mode/sending beacons on port 0, change from priv->vif to priv->vifs[0] in the check for AP mode. Additionally, if we are in AP mode, don't filter RX beacon and probe response frames to still allow working STATION mode on the other interface. Signed-off-by:
-
Martin Kaistra authored
As we only want to support AP mode/sending beacons on port 0, it is enough to replace priv->vif with priv->vifs[0]. Signed-off-by:
-
Martin Kaistra authored
In concurrent mode supported by this driver, both interfaces will use the same channel and same wireless mode. It is therefore possible to get the wireless mode by checking the first connected interface. Signed-off-by:
-
Martin Kaistra authored
To prepare for concurrent mode, enhance rtl8xxxu_set_bssid() to write the BSSID of the respective interface to REG_BSSID or REG_BSSID1. Like done with rtl8xxxu_set_mac(), call rtl8xxxu_set_bssid() with port_num = 0, until the callers also support multiple interfaces. Signed-off-by:
-
Martin Kaistra authored
If both interfaces are in STATION mode and both are connected to an AP, there might be conflicting CFO values for the two connections. Ignore the CFO information in this case. Signed-off-by:
-
Martin Kaistra authored
The driver will support two interfaces soon, which both can be in station mode, so extend the check, whether cfo information should be parsed, to cover both interfaces. For better code readability put the lines with priv->vifs[port_num] in a separate function. Signed-off-by:
-
Martin Kaistra authored
There are multiple places in the code where the current connection status of wifi is checked. The driver will support two interfaces soon and either one of them (or both) could be connected. Convert all uses of (vif && vif->cfg.assoc) to a new helper function rtl8xxxu_is_assoc() which checks both interfaces. Signed-off-by:
-
Martin Kaistra authored
To prepare for concurrent mode, enhance rtl8xxxu_set_mac() to write the mac address of the respective interface to REG_MACID or REG_MACID1. Remove the call to rtl8xxxu_set_mac() from the init function as we set it in rtl8xxxu_add_interface() later anyway. Until rtl8xxxu_add_interface() can handle both interfaces, call rtl8xxxu_set_mac() with port_num = 0. Signed-off-by:
-
Martin Kaistra authored
The driver currently does not support AP or concurrent mode for 8188e, so just use priv->vifs[0] instead of priv->vif for now. Signed-off-by:
-
Martin Kaistra authored
To prepare for concurrent mode, enhance the set_linktype function to be able to set the linktype in the MSR register for both hardware ports. Until the users of set_linktype can handle multiple interfaces, use port_num = 0. Signed-off-by:
-
Martin Kaistra authored
To prepare for concurrent mode, add an array ("vifs") to rtl8xxxu_priv to keep track of both interfaces. Keep the old priv->vif as long there are still users of it and let priv->vifs[0] point to the same location. Signed-off-by: -
Martin Kaistra authored
priv->vif gets already set in rtl8xxxu_add_interface, there is no need to set it also in rtl8xxxu_bss_info_changed(). Signed-off-by:
-
Ping-Ke Shih authored
Refine the power parameters for better step response especially at high current ramp case that is caused by power inductor variation. Signed-off-by:
-
Colin Ian King authored
There are two spelling mistakes in rtw89_err error messages. Fix these and also add space between [ERR] and message text. Signed-off-by:
Colin Ian King <colin.i.king@gmail.com> Acked-by:
-
Ping-Ke Shih authored
The channel_info is hardware settings to reflect operational status, such as scale factor, report unit, buffer matrix size, RU size and so on. Then, we can get desired reports to do further tuning. Signed-off-by:
-
Ping-Ke Shih authored
TX power is controlled by BB layer basically, but it should interact with MAC layer, so these registers are put on MAC register domain and called BB wrapper, which contains TX power for each MAC ID, OFDMA RU power, and consideration of power type table. Signed-off-by:
-
Ping-Ke Shih authored
NCTL standing for nano-controller is used to assist RF calibration. Basically, we write settings from a table, but format of the table can't describe register mask and additional conditions, so add a function to set this kind of settings. Signed-off-by:
-
Ping-Ke Shih authored
BB parameter file is a list of tuple {addr, val} with conditional hardware version. However, tuples within a condition can't be empty, so insert a special dummy tuple for this case. Then, ignore this tuple when writing. Signed-off-by: -
Cheng-Chieh Hsieh authored
DIG standing for dynamic initial gain that is used to adjust RX coverage, and PD lower threshold is packet detection power level by received signal strength to avoid false detection of the WiFi packet. Because of the hardware is different between WiFi 7 and 6 ICs, we adjust flow and add register definition for 8922A. Signed-off-by:
Cheng-Chieh Hsieh <cj.hsieh@realtek.com> Signed-off-by:
-
Chung-Hsuan Hung authored
Set values of LNA, TIA and RPL gain compensation read from firmware file when channel is changed. Signed-off-by:
Chung-Hsuan Hung <hsuan8331@realtek.com> Signed-off-by:
-
Chung-Hsuan Hung authored
Add RX gain offset dynamic setting flow according to different bands and bandwidths. RX gain offset values will be different according to different channel bands, therefore, this dynamic mechanism is needed while channel is changed. Add this to parse data from the element of firmware file, and then we can use them easier at runtime. Signed-off-by:
-
Ping-Ke Shih authored
WiFi 7 chips use different bb_gain_info struct, so move existing struct to a union in advance. This doesn't change logic at all. Signed-off-by:
-
Zong-Zhe Yang authored
Update TX power tables to RF version R37. Mainly update configurations for Canada 5.9 GHz (U-NII 4) according to IC (Industry Canada) certification. Signed-off-by:
Zong-Zhe Yang <kevin_yang@realtek.com> Signed-off-by:
-
Zong-Zhe Yang authored
Update TX power tables to RF version R36. Mainly update configurations for Canada 5.9 GHz (U-NII 4) according to IC (Industry Canada) certification. Signed-off-by:
-
Chin-Yen Lee authored
Sometimes driver can't use kernel API pci_read/write_config_byte to access the PCI config space of above address 0x100 due to the negotiated PCI setting. 8852AE/8852BE/8851BE provide another way called DBI function, which belongs to WiFi mac and could access all PCI config space for this case. Link: https://lore.kernel.org/linux-wireless/79fe81b7db7148b9a7da2353c16d70fb@realtek.com/T/#t Signed-off-by:
Chin-Yen Lee <timlee@realtek.com> Signed-off-by:
-
- Jan 08, 2024
-
-
Jakub Kicinski authored
Revert "net/mlx5: Implement management PF Ethernet profile" This reverts commit 22c46406. Revert "net/mlx5: Enable SD feature" This reverts commit c88c49ac. Revert "net/mlx5e: Block TLS device offload on combined SD netdev" This reverts commit 83a59ce0. Revert "net/mlx5e: Support per-mdev queue counter" This reverts commit d72baceb. Revert "net/mlx5e: Support cross-vhca RSS" This reverts commit c73a3ab8. Revert "net/mlx5e: Let channels be SD-aware" This reverts commit e4f9686b. Revert "net/mlx5e: Create EN core HW resources for all secondary devices" This reverts commit c4fb94aa. Revert "net/mlx5e: Create single netdev per SD group" This reverts commit e2578b4f. Revert "net/mlx5: SD, Add informative prints in kernel log" This reverts commit c82d3603. Revert "net/mlx5: SD, Implement steering for primary and secondaries" This reverts commit 605fcce3. Revert "net/mlx5: SD, Implement devcom communication and primary election" This reverts commit a45af9a9. Revert "net/mlx5: SD, Implement basic query and instantiation" This reverts commit 63b9ce94. Revert "net/mlx5: SD, Introduce SD lib" This reverts commit 4a04a31f. Revert "net/mlx5: Fix query of sd_group field" This reverts commit e04984a3. Revert "net/mlx5e: Use the correct lag ports number when creating TISes" This reverts commit a7e7b40c. There are some unanswered questions on the list, and we don't have any docs. Given the lack of replies so far and the fact that v6.8 merge window has started - let's revert this and revisit for v6.9. Link: https://lore.kernel.org/all/20231221005721.186607-1-saeed@kernel.org/ Signed-off-by:
Jakub Kicinski <kuba@kernel.org>
-
Jakub Kicinski authored
Revert "net: stmmac: Use interrupt mode INTM=1 for per channel irq" This reverts commit 36af9f25. Revert "net: stmmac: Add support for TX/RX channel interrupt" This reverts commit 9072e03d. Revert "net: stmmac: Make MSI interrupt routine generic" This reverts commit 477bd4be. Revert "dt-bindings: net: snps,dwmac: per channel irq" This reverts commit 67d47c8a. Device tree bindings need to be reviewed. Link: https://lore.kernel.org/all/2df9fe3e-7971-4aa2-89a9-0e085b3b00d7@linaro.org/ Signed-off-by:
-
Christophe JAILLET authored
ida_alloc() and ida_free() should be preferred to the deprecated ida_simple_get() and ida_simple_remove(). This is less verbose. Note that the upper bound of ida_alloc_range() is inclusive while the one of ida_simple_get() was exclusive. So calls have been updated accordingly. Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Reviewed-by:
Simon Horman <horms@kernel.org> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Christophe JAILLET authored
s/diffentiate/differentiate/ Signed-off-by:
-
Jamal Hadi Salim authored
Commit ba24ea12 ("net/sched: Retire ipt action") removed the ipt action but not the testcases. This patch removes the outstanding tdc tests. Signed-off-by:
Jamal Hadi Salim <jhs@mojatatu.com> Signed-off-by:
-
David S. Miller authored
Swee Leong Ching says: ==================== net: stmmac: Enable Per DMA Channel interrupt Add Per DMA Channel interrupt feature for DWXGMAC IP. Patchset (link below) contains per DMA channel interrupt, But it was achieved. https://lore.kernel.org/lkml/20230821203328.GA2197059- robh@kernel.org/t/#m849b529a642e1bff89c05a07efc25d6a94c8bfb4 Some of the changes in this patchset are based on reviewer comment on patchset mentioned beforehand. ==================== Signed-off-by:
-
Swee Leong Ching authored
Enable per DMA channel interrupt that uses shared peripheral interrupt (SPI), so only per channel TX and RX intr (TI/RI) are handled by TX/RX ISR without calling common interrupt ISR. Signed-off-by:
Teoh Ji Sheng <ji.sheng.teoh@intel.com> Signed-off-by:
Swee Leong Ching <leong.ching.swee@intel.com> Signed-off-by:
-
Swee Leong Ching authored
Enable TX/RX channel interrupt registration for MAC that interrupts CPU through shared peripheral interrupt (SPI). Per channel interrupts and interrupt-names are registered through, Eg: 4 tx and 4 rx channels: interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>; <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>; <GIC_SPI 105 IRQ_TYPE_LEVEL_HIGH>; <GIC_SPI 106 IRQ_TYPE_LEVEL_HIGH>; <GIC_SPI 107 IRQ_TYPE_LEVEL_HIGH>; interrupt-names = "dma_tx0", "dma_tx1", "dma_tx2", "dma_tx3", "dma_rx0", "dma_rx1", "dma_rx2", "dma_rx3"; Signed-off-by: -
Swee Leong Ching authored
There is no support for per DMA channel interrupt for non-MSI platform, where the MAC's per channel interrupt hooks up to interrupt controller(GIC) through shared peripheral interrupt(SPI) to handle interrupt from TX/RX transmit channel. This patch generalize the existing MSI ISR to also support non-MSI platform. Signed-off-by:
-
Swee Leong Ching authored
Add dt-bindings for per channel irq. Signed-off-by:
Rohan G Thomas <rohan.g.thomas@intel.com> Signed-off-by:
-
