- 15 Sep, 2021 6 commits
-
-
Aleksander Jan Bajkowski authored
Configure the burst length in Ethernet drivers. This improves Ethernet performance by 58%. According to the vendor BSP, 8W burst length is supported by ar9 and newer SoCs. The NAT benchmark results on xRX200 (Down/Up): * 2W: 330 Mb/s * 4W: 432 Mb/s 372 Mb/s * 8W: 520 Mb/s 389 Mb/s Tested on xRX200 and xRX330. Signed-off-by:
Aleksander Jan Bajkowski <olek2@wp.pl> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Aleksander Jan Bajkowski authored
Make the burst length configurable by the drivers. Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by:
-
Aleksander Jan Bajkowski authored
The current definition of 2W burst length is invalid. This patch fixes it. Current downstream DEU driver doesn't use DMA. An incorrect burst length value doesn't cause any errors. This patch also adds other burst length values. Fixes: dfec1a82 ("MIPS: Lantiq: Add DMA support") Signed-off-by:
-
Aleksander Jan Bajkowski authored
Different SoCs have a different number of channels, e.g .: * amazon-se has 10 channels, * danube+ar9 have 20 channels, * vr9 has 28 channels, * ar10 has 24 channels. We can read the ID register and, depending on the reported number of channels, reset the appropriate number of channels. Signed-off-by:
-
Aleksander Jan Bajkowski authored
Reading the DMA registers immediately after the reset causes Data Bus Error. Adding a small delay fixes this issue. Signed-off-by:
-
Linus Walleij authored
This drops the code setting bit 9 on egress frames on the Realtek "type A" (RTL8366RB) frames. This bit was set on ingress frames for unknown reason, and was set on egress frames as the format of ingress and egress frames was believed to be the same. As that assumption turned out to be false, and since this bit seems to have zero effect on the behaviour of the switch let's drop this bit entirely. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Reviewed-by:
Andrew Lunn <andrew@lunn.ch> Reviewed-by:
Florian Fainelli <f.fainelli@gmail.com> Link: https://lore.kernel.org/r/20210913143156.1264570-1-linus.walleij@linaro.orgSigned-off-by:
Jakub Kicinski <kuba@kernel.org>
-
- 14 Sep, 2021 29 commits
-
-
David S. Miller authored
Guangbin Huang says: ==================== PF support get MAC address space assigned by firmware This series add support PF to get unicast/multicast MAC address space assigned by firmware for the HNS3 ethernet driver. ==================== Signed-off-by: -
Guangbin Huang authored
The new firmware supports to divides the whole multicast MAC address space equally to functions of all PFs, and calculates the space size of each PF according to its function number. To support this feature, PF driver adds querying multicast MAC address space size from firmware and limits used number according to space size. Signed-off-by:
Guangbin Huang <huangguangbin2@huawei.com> Signed-off-by:
-
Guangbin Huang authored
Currently, there are two ways for PF to set the unicast MAC address space size: specified by config parameters in firmware or set to default value. That's mean if the config parameters in firmware is zero, driver will divide the whole unicast MAC address space equally to 8 PFs. However, in this case, the unicast MAC address space will be wasted a lot when the hardware actually has less then 8 PFs. And in the other hand, if one PF has much more VFs than other PFs, then each function of this PF will has much less address space than other PFs. In order to ameliorate the above two situations, introduce the third way of unicast MAC address space assignment: firmware divides the whole unicast MAC address space equally to functions of all PFs, and calculates the space size of each PF according to its function number. PF queries the space size by the querying device specification command when in initialization process. The third way assignment is lower priority than specified by config parameters, only if the config parameters is zero can be used, and if firmware does not support the third way assignment, then driver still divides the whole unicast MAC address space equally to 8 PFs. Signed-off-by:
-
Ansuel Smith authored
Add support for qca8327 internal phy needed for correct init of the switch port. It does use the same qca8337 function and reg just with a different id. Signed-off-by:
Ansuel Smith <ansuelsmth@gmail.com> Tested-by:
Rosen Penev <rosenp@gmail.com> Tested-by:
-
Yajun Deng authored
The __alloc_frag_align() is short, and only called by two functions, so inline page_frag_alloc_align() for reduce the overhead of calls. Reported-by:
kernel test robot <oliver.sang@intel.com> Signed-off-by:
Yajun Deng <yajun.deng@linux.dev> Signed-off-by:
-
Heiner Kallweit authored
It shouldn't happen, but can happen that readable eeprom size is smaller than announced. Then we would be stuck in an endless loop here because after reaching the actual end reads return eeprom.len = 0. I faced this issue when making a mistake in driver development. Detect this scenario and return an error. Signed-off-by:
Heiner Kallweit <hkallweit1@gmail.com> Signed-off-by:
-
M Chetan Kumar authored
Removed "stdbool.h" inclusion in iosm_ipc_imem.h Fixes: 13bb8429 ("net: wwan: iosm: firmware flashing and coredump collection") Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
M Chetan Kumar <m.chetan.kumar@linux.intel.com> Signed-off-by:
-
Min Li authored
Also correct how initialize_dco_operating_mode is called Signed-off-by:
Min Li <min.li.xe@renesas.com> Signed-off-by:
-
Min Li authored
So far we don't need to support new 5.2 functions but different register addresses Signed-off-by:
-
Min Li authored
Not need since TCS firmware file will configure it properlly. Signed-off-by:
-
Heiner Kallweit authored
This patch is a follow-up to beb401ec ("r8169: deprecate support for RTL_GIGA_MAC_VER_27") that came with 5.12. Nobody complained, so let's remove support for this chip version. Signed-off-by:
-
David S. Miller authored
Guvenc Gulce says: ==================== net/smc: add EID support please apply the following patch series for smc to netdev's net-next tree. The series introduce the so called Enterprise ID support for smc protocol. Including the generic netlink based interface. ==================== Signed-off-by: -
Karsten Graul authored
With SMC-Dv2 users can configure if the static system EID should be used during CLC handshake, or if only user EIDs are allowed. Add generic netlink support to enable and disable the system EID, and to retrieve the system EID and its current enabled state. Signed-off-by:
Karsten Graul <kgraul@linux.ibm.com> Reviewed-by:
Guvenc Gulce <guvenc@linux.ibm.com> Signed-off-by:
-
Karsten Graul authored
The system EID is retrieved using an registered ISM device each time when needed. This adds some unnecessary complexity at all places where the system EID is needed, but no ISM device is at hand. Simplify the code and save the system EID in a static variable in smc_ism.c. Signed-off-by:
-
Karsten Graul authored
SMC-Dv2 allows users to define EIDs which allows to create separate name spaces enabling users to cluster their SMC-Dv2 connections. Add support for user defined EIDs and extent the generic netlink interface so users can add, remove and dump EIDs. Signed-off-by:
-
David S. Miller authored
Karsten Graul says: ==================== s390/net: updates 2021-09-14 Please apply the following patches to netdev's net-next tree. Stop using the wrappers in include/linux/pci-dma-compat.h, and fix warnings about incorrect kernel-doc comments. ==================== Signed-off-by: -
Christophe JAILLET authored
The wrappers in include/linux/pci-dma-compat.h should go away. The patch has been generated with the coccinelle script below. @@ expression e1, e2; @@ - pci_set_dma_mask(e1, e2) + dma_set_mask(&e1->dev, e2) Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Signed-off-by:
-
Heiko Carstens authored
Many comments above functions start with a kernel doc indicator, but the comments are not using kernel doc style. Get rid of the warnings by simply removing the indicator. E.g.: drivers/s390/net/netiucv.c:1852: warning: This comment starts with '/**', but isn't a kernel-doc comment. Reviewed-by:
Alexandra Winter <wintera@linux.ibm.com> Signed-off-by:
Heiko Carstens <hca@linux.ibm.com> Signed-off-by:
-
Heiko Carstens authored
Many comments above functions start with a kernel doc indicator, but the comments are not using kernel doc style. Get rid of the warnings by simply removing the indicator. E.g.: drivers/s390/net/lcs.c:2355: warning: This comment starts with '/**', but isn't a kernel-doc comment. Acked-by:
-
Heiko Carstens authored
Many comments above functions start with a kernel doc indicator, but the comments are not using kernel doc style. Get rid of the warnings by simply removing the indicator. E.g.: drivers/s390/net/ctcm_main.c:979: warning: This comment starts with '/**', but isn't a kernel-doc comment. Acked-by:
-
David S. Miller authored
Ido Schimmel says: ==================== mlxsw: spectrum: Adjustments to port split and label port Jiri says: This patchset includes patches that prepare the driver to support modular systems. PLLP register is introduced to get front panel port label which is no longer equivalent to "module + 1" for modular systems, where the numbering is per line card. So far for all systems all front panel ports had same format and could be split to the same number of subports. This is no longer true for modular systems, where every line card can have different types of front panel ports. The PMTDB register is introduced to easily query FW for split capabilities of particular front panel port. It is generic for use in modular and non-modular systems. ==================== Signed-off-by: -
Jiri Pirko authored
It is not used anymore, remove it. Signed-off-by:
Jiri Pirko <jiri@nvidia.com> Signed-off-by:
Ido Schimmel <idosch@nvidia.com> Signed-off-by:
-
Jiri Pirko authored
Newly introduced PMTDB register is there to provide all needed info about particular requested port split configuration. Use it instead of figuring the info out manually in the driver. Signed-off-by:
-
Jiri Pirko authored
The PMTDB register allows to query the possible module<->local port mapping than can be used in PMLP. It does not represent the actual/current mapping of the local to module. Actual mapping is only defined by PMLP. Signed-off-by:
-
Jiri Pirko authored
Instead of relying on the values coming from the PMLP register, use PLLP to get the information about port front panel number and split number. Signed-off-by:
-
Jiri Pirko authored
The PLLP register returns the mapping from Local Port into Label Port. Signed-off-by:
-
Jiri Pirko authored
During port creation, mlxsw_core_port_init() is called with the front panel port number and the split port sub-number. Currently, this information is determined by the driver without firmware assistance. Subsequent patches are going to query this information from firmware, but this requires the port to assigned to SWID. Therefore, move port SWID assignment before mlxsw_core_port_init(). Signed-off-by:
-
Jiri Pirko authored
During port creation, mlxsw_core_port_init() is called with the front panel port number and the split port sub-number. Currently, this information is determined by the driver without firmware assistance. Subsequent patches are going to query this information from firmware, but this requires the port to be mapped to a module. Therefore, move port mapping before mlxsw_core_port_init(). Signed-off-by:
-
Jiri Pirko authored
Add latest verified version of Nvidia Spectrum-family switch firmware, for Spectrum (13.2008.3326), Spectrum-2 (29.2008.3326) and Spectrum-3 (30.2008.3326). Signed-off-by:
-
- 13 Sep, 2021 5 commits
-
-
M Chetan Kumar authored
This patch brings-in support for M.2 7560 Device firmware flashing & coredump collection using devlink. - Driver Registers with Devlink framework. - Register devlink params callback for configuring device params required in flashing or coredump flow. - Implements devlink ops flash_update callback that programs modem firmware. - Creates region & snapshot required for device coredump log collection. On early detection of device in boot rom stage. Driver registers with Devlink framework and establish transport channel for PSI (Primary Signed Image) injection. Once PSI is injected to device, the device execution stage details are read to determine whether device is in flash or exception mode. The collected information is reported to devlink user space application & based on this informationi, application proceeds with either modem firmware flashing or coredump collection. Signed-off-by:
-
David S. Miller authored
Krzysztof Kozlowski says: ==================== nfc: minor printk cleanup Changes since v1: 1. Remove unused variable in pn533 (reported by kbuild). ==================== Signed-off-by: -
Krzysztof Kozlowski authored
nci_skb_alloc() already prints an error message on memory allocation failure. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> Signed-off-by:
-
Krzysztof Kozlowski authored
nfc_mei_phy_alloc() already prints an error message on memory allocation failure. Signed-off-by:
-
Krzysztof Kozlowski authored
nfc_mei_phy_alloc() already prints an error message on memory allocation failure. Signed-off-by:
-
