~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/mhi/topology.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 .. SPDX-License-Identifier: GPL-2.0
  2 
  3 ============
  4 MHI Topology
  5 ============
  6 
  7 This document provides information about the MHI topology modeling and
  8 representation in the kernel.
  9 
 10 MHI Controller
 11 --------------
 12 
 13 MHI controller driver manages the interaction with the MHI client devices
 14 such as the external modems and WiFi chipsets. It is also the MHI bus master
 15 which is in charge of managing the physical link between the host and device.
 16 It is however not involved in the actual data transfer as the data transfer
 17 is taken care by the physical bus such as PCIe. Each controller driver exposes
 18 channels and events based on the client device type.
 19 
 20 Below are the roles of the MHI controller driver:
 21 
 22 * Turns on the physical bus and establishes the link to the device
 23 * Configures IRQs, IOMMU, and IOMEM
 24 * Allocates struct mhi_controller and registers with the MHI bus framework
 25   with channel and event configurations using mhi_register_controller.
 26 * Initiates power on and shutdown sequence
 27 * Initiates suspend and resume power management operations of the device.
 28 
 29 MHI Device
 30 ----------
 31 
 32 MHI device is the logical device which binds to a maximum of two MHI channels
 33 for bi-directional communication. Once MHI is in powered on state, the MHI
 34 core will create MHI devices based on the channel configuration exposed
 35 by the controller. There can be a single MHI device for each channel or for a
 36 couple of channels.
 37 
 38 Each supported device is enumerated in::
 39 
 40         /sys/bus/mhi/devices/
 41 
 42 MHI Driver
 43 ----------
 44 
 45 MHI driver is the client driver which binds to one or more MHI devices. The MHI
 46 driver sends and receives the upper-layer protocol packets like IP packets,
 47 modem control messages, and diagnostics messages over MHI. The MHI core will
 48 bind the MHI devices to the MHI driver.
 49 
 50 Each supported driver is enumerated in::
 51 
 52         /sys/bus/mhi/drivers/
 53 
 54 Below are the roles of the MHI driver:
 55 
 56 * Registers the driver with the MHI bus framework using mhi_driver_register.
 57 * Prepares the device for transfer by calling mhi_prepare_for_transfer.
 58 * Initiates data transfer by calling mhi_queue_transfer.
 59 * Once the data transfer is finished, calls mhi_unprepare_from_transfer to
 60   end data transfer.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php