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

TOMOYO Linux Cross Reference
Linux/Documentation/devicetree/bindings/mfd/mfd.txt

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 Multi-Function Devices (MFD)
  2 
  3 These devices comprise a nexus for heterogeneous hardware blocks containing
  4 more than one non-unique yet varying hardware functionality.
  5 
  6 A typical MFD can be:
  7 
  8 - A mixed signal ASIC on an external bus, sometimes a PMIC (Power Management
  9   Integrated Circuit) that is manufactured in a lower technology node (rough
 10   silicon) that handles analog drivers for things like audio amplifiers, LED
 11   drivers, level shifters, PHY (physical interfaces to things like USB or
 12   ethernet), regulators etc.
 13 
 14 - A range of memory registers containing "miscellaneous system registers" also
 15   known as a system controller "syscon" or any other memory range containing a
 16   mix of unrelated hardware devices.
 17 
 18 Optional properties:
 19 
 20 - compatible : "simple-mfd" - this signifies that the operating system
 21   should consider all subnodes of the MFD device as separate and independent
 22   devices, so not needing any resources to be provided by the parent device.
 23   Similarly to how "simple-bus" indicates when to see subnodes as children for
 24   a simple memory-mapped bus.
 25   For more complex devices, when the nexus driver has to probe registers to
 26   figure out what child devices exist etc, this should not be used. In the
 27   latter case the child devices will be determined by the operating system.
 28 
 29 - ranges: Describes the address mapping relationship to the parent. Should set
 30   the child's base address to 0, the physical address within parent's address
 31   space, and the length of the address map.
 32 
 33 - #address-cells: Specifies the number of cells used to represent physical base
 34   addresses. Must be present if ranges is used.
 35 
 36 - #size-cells: Specifies the number of cells used to represent the size of an
 37   address. Must be present if ranges is used.
 38 
 39 Example:
 40 
 41 foo@1000 {
 42         compatible = "syscon", "simple-mfd";
 43         reg = <0x01000 0x1000>;
 44 
 45         led@8.0 {
 46                 compatible = "register-bit-led";
 47                 offset = <0x08>;
 48                 mask = <0x01>;
 49                 label = "myled";
 50                 default-state = "on";
 51         };
 52 };

~ [ 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