Changes in Kconfig

035e3bef - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled

Mon, 07 Nov 2022 07:35:02 +0000

net: wwan: iosm: fix driver not working with INTEL_IOMMU disabledWith INTEL_IOMMU disable config or by forcing intel_iommu=off fromgrub some of the features of IOSM driver like browsing, flashing &coredump collection is not working.When driver calls DMA API - dma_map_single() for tx transfers. It isresulting in dma mapping error.Set the device DMA addressing capabilities using dma_set_mask() andremove the INTEL_IOMMU dependency in kconfig so that driver followsthe platform config either INTEL_IOMMU enable or disable.Fixes: f7af616c632e ("net: iosm: infrastructure")Signed-off-by: M Chetan Kumar Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

3349e4a4 - net: wwan: t7xx: Add port for modem logging

Fri, 28 Oct 2022 15:35:34 +0000

net: wwan: t7xx: Add port for modem loggingThe Modem Logging (MDL) port provides an interface to collect modemlogs for debugging purposes. MDL is supported by the relay interface,and the mtk_t7xx port infrastructure. MDL allows user-space apps tocontrol logging via mbim command and to collect logs via the relayinterface, while port infrastructure facilitates communication betweenthe driver and the modem.Signed-off-by: Moises Veleta Signed-off-by: M Chetan Kumar Signed-off-by: Devegowda Chandrashekar Acked-by: Ricardo Martinez Reviewed-by: Sergey Ryazanov Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

bf294c3f - Revert "Merge branch 'wwan-t7xx-fw-flashing-and-coredump-support'"

Fri, 19 Aug 2022 22:29:38 +0000

Revert "Merge branch 'wwan-t7xx-fw-flashing-and-coredump-support'"This reverts commit 5417197dd516a8e115aa69f62a7b7554b0c3829c, reversingchanges made to 0630f64d25a0f0a8c6a9ce9fde8750b3b561e6f5.Reverting to allow addressing review comments.Link: https://lore.kernel.org/all/4c5dbea0-52a9-1c3d-7547-00ea54c90550@linux.intel.com/Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/wwan/Kconfig

87dae9e7 - net: wwan: t7xx: Enable devlink based fw flashing and coredump collection

Tue, 16 Aug 2022 04:24:05 +0000

net: wwan: t7xx: Enable devlink based fw flashing and coredump collectionThis patch brings-in support for t7xx wwan device firmware flashing &coredump collection using devlink.Driver Registers with Devlink framework.Implements devlink ops flash_update callback that programs modem firmware.Creates region & snapshot required for device coredump log collection.On early detection of wwan device in fastboot mode driver sets up CLDMA0 HWtx/rx queues for raw data transfer then registers with devlink framework.Upon receiving firmware image & partition details driver sends fastbootcommands for flashing the firmware.In this flow the fastboot command & response gets exchanged between driverand device. Once firmware flashing is success completion status is reportedto user space application.Below is the devlink command usage for firmware flashing$devlink dev flash pci/$BDF file ABC.img component ABCNote: ABC.img is the firmware to be programmed to "ABC" partition.In case of coredump collection when wwan device encounters an exceptionit reboots & stays in fastboot mode for coredump collection by host driver.On detecting exception state driver collects the core dump, creates thedevlink region & reports an event to user space application for dumpcollection. The user space application invokes devlink region read commandfor dump collection.Below are the devlink commands used for coredump collection.devlink region new pci/$BDF/mr_dumpdevlink region read pci/$BDF/mr_dump snapshot $ID address $ADD length $LENdevlink region del pci/$BDF/mr_dump snapshot $IDSigned-off-by: M Chetan Kumar Signed-off-by: Devegowda Chandrashekar Signed-off-by: Mishra Soumya Prakash Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

13e920d9 - net: wwan: t7xx: Add core components

Fri, 06 May 2022 18:13:00 +0000

net: wwan: t7xx: Add core componentsRegisters the t7xx device driver with the kernel. Setup all the corecomponents: PCIe layer, Modem Host Cross Core Interface (MHCCIF),modem control operations, modem state machine, and buildinfrastructure.* PCIe layer code implements driver probe and removal.* MHCCIF provides interrupt channels to communicate events such as handshake, PM and port enumeration.* Modem control implements the entry point for modem init, reset and exit.* The modem status monitor is a state machine used by modem control to complete initialization and stop. It is used also to propagate exception events reported by other components.Signed-off-by: Haijun Liu Signed-off-by: Chandrashekar Devegowda Co-developed-by: Ricardo Martinez Signed-off-by: Ricardo Martinez Reviewed-by: Loic Poulain Reviewed-by: Ilpo Järvinen Reviewed-by: Sergey Ryazanov Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

283e6f5a - net: wwan: make debugfs optional

Tue, 07 Dec 2021 09:21:40 +0000

net: wwan: make debugfs optionalDebugfs interface is optional for the regular modem use. Some distrosand users will want to disable this feature for security or kernelsize reasons. So add a configuration option that allows to completelydisable the debugfs interface of the WWAN devices.A primary considered use case for this option was embedded firmwares.For example, in OpenWrt, you can not completely disable debugfs, as alot of wireless stuff can only be configured and monitored with thedebugfs knobs. At the same time, reducing the size of a kernel andmodules is an essential task in the world of embedded software.Disabling the WWAN and IOSM debugfs interfaces allows us to save 50K(x86-64 build) of space for module storage. Not much, but alreadyconsiderable when you only have 16MB of storage.So it is hard to just disable whole debugfs. Users need some finegrained set of options to control which debugfs interface is importantand should be available and which is not.The new configuration symbol is enabled by default and is hidden underthe EXPERT option. So a regular user would not be bothered by anotherone configuration question. While an embedded distro maintainer will beable to a little more reduce the final image size.Signed-off-by: Sergey Ryazanov Reviewed-by: Leon Romanovsky Reviewed-by: Loic Poulain Acked-by: M Chetan Kumar Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/wwan/Kconfig

5382911f - net: wwan: iosm: select CONFIG_RELAY

Sat, 04 Dec 2021 17:40:25 +0000

net: wwan: iosm: select CONFIG_RELAYThe iosm driver started using relayfs, but is missing the Kconfiglogic to ensure it's built into the kernel:x86_64-linux-ld: drivers/net/wwan/iosm/iosm_ipc_trace.o: in function `ipc_trace_create_buf_file_handler':iosm_ipc_trace.c:(.text+0x16): undefined reference to `relay_file_operations'x86_64-linux-ld: drivers/net/wwan/iosm/iosm_ipc_trace.o: in function `ipc_trace_subbuf_start_handler':iosm_ipc_trace.c:(.text+0x31): undefined reference to `relay_buf_full'x86_64-linux-ld: drivers/net/wwan/iosm/iosm_ipc_trace.o: in function `ipc_trace_ctrl_file_write':iosm_ipc_trace.c:(.text+0xd5): undefined reference to `relay_flush'x86_64-linux-ld: drivers/net/wwan/iosm/iosm_ipc_trace.o: in function `ipc_trace_port_rx':Fixes: 00ef32565b9b ("net: wwan: iosm: device trace collection using relayfs")Signed-off-by: Arnd Bergmann Acked-by: Sergey Ryazanov Reviewed-by: M Chetan Kumar Link: https://lore.kernel.org/r/20211204174033.950528-1-arnd@kernel.orgSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/wwan/Kconfig

21a0ffd9 - net: wwan: Add Qualcomm BAM-DMUX WWAN network driver

Sat, 27 Nov 2021 17:31:08 +0000

net: wwan: Add Qualcomm BAM-DMUX WWAN network driverThe BAM Data Multiplexer provides access to the network data channels ofmodems integrated into many older Qualcomm SoCs, e.g. Qualcomm MSM8916 orMSM8974. It is built using a simple protocol layer on top of a DMA engine(Qualcomm BAM) and bidirectional interrupts to coordinate power control.The modem announces a fixed set of channels by sending an OPEN command.The driver exports each channel as separate network interface so thata connection can be established via QMI from userspace. The networkinterface can work either in Ethernet or Raw-IP mode (configurable viaQMI). However, Ethernet mode seems to be broken with most firmwares(network packets are actually received as Raw-IP), therefore the driveronly supports Raw-IP mode.Note that the control channel (QMI/AT) is entirely separate fromBAM-DMUX and is already supported by the RPMSG_WWAN_CTRL driver.The driver uses runtime PM to coordinate power control with the modem.TX/RX buffers are put in a kind of "ring queue" and submitted viathe bam_dma driver of the DMAEngine subsystem.The basic architecture looks roughly like this: +------------+ +-------+ [IPv4/6] | BAM-DMUX | | | [Data...] | | | | ---------->|wwan0 | [DMUX chan: x] | | [IPv4/6] | (chan: 0) | [IPv4/6] | | [Data...] | | [Data...] | | ---------->|wwan1 |--------------->| Modem | | (chan: 1) | BAM | | [IPv4/6] | ... | (DMA Engine) | | [Data...] | | | | ---------->|wwan7 | | | | (chan: 7) | | | +------------+ +-------+Note that some newer firmware versions support QMAP ("rmnet" driver)as additional multiplexing layer on top of BAM-DMUX, but this is notcurrently supported by this driver.Signed-off-by: Stephan Gerhold Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

607d574a - net: wwan: iosm: fw flashing & cd collection infrastructure changes

Sun, 19 Sep 2021 17:28:35 +0000

net: wwan: iosm: fw flashing & cd collection infrastructure changesIOSM Makefile & WWAN Kconfig changes to support fw flashing & cdcollection module compliation.Signed-off-by: M Chetan Kumar Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

d1ab2647 - Revert "net: wwan: iosm: firmware flashing and coredump collection"

Wed, 15 Sep 2021 21:58:23 +0000

Revert "net: wwan: iosm: firmware flashing and coredump collection"The devlink parameters are not the right mechanism to passextra parameters to device flashing. The params added arealso undocumented.This reverts commit 13bb8429ca98 ("net: wwan: iosm: firmwareflashing and coredump collection").Signed-off-by: Jakub Kicinski Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

13bb8429 - net: wwan: iosm: firmware flashing and coredump collection

Mon, 13 Sep 2021 13:04:12 +0000

net: wwan: iosm: firmware flashing and coredump collectionThis 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 withDevlink framework and establish transport channel for PSI (Primary SignedImage) injection. Once PSI is injected to device, the device executionstage details are read to determine whether device is in flash orexception mode. The collected information is reported to devlink userspace application & based on this informationi, application proceeds witheither modem firmware flashing or coredump collection.Signed-off-by: M Chetan Kumar Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

aa730a99 - net: wwan: Add MHI MBIM network driver

Tue, 03 Aug 2021 13:36:28 +0000

net: wwan: Add MHI MBIM network driverAdd new wwan driver for MBIM over MHI. MBIM is a transport protocolfor IP packets, allowing packet aggregation and muxing. Initiallydesigned for USB bus, it is also exposed through MHI bus for QCOMbased PCIe wwan modems.This driver supports the new wwan rtnetlink interface for multi-linkmanagement and has been tested with Quectel EM120R-GL M2 module.Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

5e90abf4 - net: wwan: Add RPMSG WWAN CTRL driver

Fri, 18 Jun 2021 17:36:10 +0000

net: wwan: Add RPMSG WWAN CTRL driverThe remote processor messaging (rpmsg) subsystem provides an interfaceto communicate with other remote processors. On many Qualcomm SoCs thisis used to communicate with an integrated modem DSP that implements mostof the modem functionality and provides high-level protocols likeQMI or AT to allow controlling the modem.For QMI, most older Qualcomm SoCs (e.g. MSM8916/MSM8974) havea standalone "DATA5_CNTL" channel that allows exchanging QMI messages.Note that newer SoCs (e.g. SDM845) only allow exchanging QMI messagesvia a shared QRTR channel that is available via a socket API on Linux.For AT, the "DATA4" channel accepts at least a limited set of ATcommands, on many older and newer Qualcomm SoCs, although QMI istypically the preferred control protocol.Often there are additional QMI/AT channels (usually named DATA*_CNTLfor QMI and DATA* for AT), but it is not clear if those are reallyfunctional on all devices. Also, at the moment there is no use casefor having multiple QMI/AT ports. If needed more channels could beadded later after more testing.Note that the data path (network interface) is entirely separatefrom the control path and varies between Qualcomm SoCs, e.g. "IPA"on newer Qualcomm SoCs or "BAM-DMUX" on some older ones.The RPMSG WWAN CTRL driver exposes the QMI/AT control ports via theWWAN subsystem, and therefore allows userspace like ModemManager toset up the modem. Until now, ModemManager had to use the RPMSG-specificrpmsg-char where the channels must be explicitly exposed as a chardevice first and don't show up directly in sysfs.The driver is a fairly simple glue layer between WWAN and RPMSGand is mostly based on the existing mhi_wwan_ctrl.c and rpmsg_char.c.Cc: Loic Poulain Cc: Bjorn Andersson Signed-off-by: Stephan Gerhold Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

89212e16 - net: wwan: Fix WWAN config symbols

Mon, 14 Jun 2021 16:56:36 +0000

net: wwan: Fix WWAN config symbolsThere is not strong reason to have both WWAN and WWAN_CORE symbols,Let's build the WWAN core framework when WWAN is selected, in thesame way as for other subsystems.This fixes issue with mhi_net selecting WWAN_CORE without WWAN andreported by kernel test robot:Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for WWAN_CORE Depends on NETDEVICES && WWAN Selected by - MHI_NET && NETDEVICES && NET_CORE && MHI_BUSFixes: 9a44c1cc6388 ("net: Add a WWAN subsystem")Reported-by: kernel test robot Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

f7af616c - net: iosm: infrastructure

Sun, 13 Jun 2021 12:50:23 +0000

net: iosm: infrastructure1) Kconfig & Makefile changes for IOSM Driver compilation.2) Add IOSM Driver documentation.3) Modified MAINTAINER file for IOSM Driver addition.Signed-off-by: M Chetan Kumar Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

f36a111a - wwan_hwsim: WWAN device simulator

Tue, 08 Jun 2021 04:02:32 +0000

wwan_hwsim: WWAN device simulatorThis driver simulates a set of WWAN device with a set of AT controlports. It can be used to test WWAN kernel framework as well as userspace tools.Signed-off-by: Sergey Ryazanov Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

fa588eba - net: Add Qcom WWAN control driver

Fri, 16 Apr 2021 08:36:34 +0000

net: Add Qcom WWAN control driverThe MHI WWWAN control driver allows MHI QCOM-based modems to exposedifferent modem control protocols/ports via the WWAN framework, so thatuserspace modem tools or daemon (e.g. ModemManager) can control WWANconfig and state (APN config, SMS, provider selection...). A QCOM-basedmodem can expose one or several of the following protocols:- AT: Well known AT commands interactive protocol (microcom, minicom...)- MBIM: Mobile Broadband Interface Model (libmbim, mbimcli)- QMI: QCOM MSM/Modem Interface (libqmi, qmicli)- QCDM: QCOM Modem diagnostic interface (libqcdm)- FIREHOSE: XML-based protocol for Modem firmware management (qmi-firmware-update)Note that this patch is mostly a rework of the earlier MHI UCItentative that was a generic interface for accessing MHI bus fromuserspace. As suggested, this new version is WWAN specific and isdedicated to only expose channels used for controlling a modem, andfor which related opensource userpace support exist.Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig

9a44c1cc - net: Add a WWAN subsystem

Fri, 16 Apr 2021 08:36:33 +0000

net: Add a WWAN subsystemThis change introduces initial support for a WWAN framework. Given thecomplexity and heterogeneity of existing WWAN hardwares and interfaces,there is no strict definition of what a WWAN device is and how it shouldbe represented. It's often a collection of multiple devices that performthe global WWAN feature (netdev, tty, chardev, etc).One usual way to expose modem controls and configuration is via highlevel protocols such as the well known AT command protocol, MBIM orQMI. The USB modems started to expose them as character devices, anduser daemons such as ModemManager learnt to use them.This initial version adds the concept of WWAN port, which is a logicalpipe to a modem control protocol. The protocols are rawly exposed touser via character device, allowing straigthforward support in existingtools (ModemManager, ofono...). The WWAN core takes care of the genericpart, including character device management, and relies on port driveroperations to receive/submit protocol data.Since the different devices exposing protocols for a same WWAN hardwaredo not necessarily know about each others (e.g. two different USBinterfaces, PCI/MHI channel devices...) and can be created/removed indifferent orders, the WWAN core ensures that all WAN ports contributingto the 'whole' WWAN feature are grouped under the same virtual WWANdevice, relying on the provided parent device (e.g. mhi controller,USB device). It's a 'trick' I copied from Johannes's earlier WWANsubsystem proposal.This initial version is purposely minimalist, it's essentially movingthe generic part of the previously proposed mhi_wwan_ctrl driver insidea common WWAN framework, but the implementation is open and flexibleenough to allow extension for further drivers.Signed-off-by: Loic Poulain Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/wwan/Kconfig