1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" []>
5 <book id="LinuxKernelAPI">
7 <title>The Linux Kernel API</title>
11 This documentation is free software; you can redistribute
12 it and/or modify it under the terms of the GNU General Public
13 License as published by the Free Software Foundation; either
14 version 2 of the License, or (at your option) any later
19 This program is distributed in the hope that it will be
20 useful, but WITHOUT ANY WARRANTY; without even the implied
21 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
22 See the GNU General Public License for more details.
26 You should have received a copy of the GNU General Public
27 License along with this program; if not, write to the Free
28 Software Foundation, Inc., 59 Temple Place, Suite 330, Boston,
33 For more details see the file COPYING in the source
34 distribution of Linux.
42 <title>Driver Basics</title>
43 <sect1><title>Driver Entry and Exit points</title>
44 !Iinclude/linux/init.h
47 <sect1><title>Atomic and pointer manipulation</title>
48 !Iinclude/asm-x86/atomic_32.h
49 !Iinclude/asm-x86/unaligned.h
52 <sect1><title>Delaying, scheduling, and timer routines</title>
53 !Iinclude/linux/sched.h
57 <sect1><title>High-resolution timers</title>
58 !Iinclude/linux/ktime.h
59 !Iinclude/linux/hrtimer.h
62 <sect1><title>Workqueues and Kevents</title>
65 <sect1><title>Internal Functions</title>
68 !Iinclude/linux/kthread.h
72 <sect1><title>Kernel objects manipulation</title>
74 X!Iinclude/linux/kobject.h
79 <sect1><title>Kernel utility functions</title>
80 !Iinclude/linux/kernel.h
87 <sect1><title>Device Resource Management</title>
88 !Edrivers/base/devres.c
94 <title>Data Types</title>
95 <sect1><title>Doubly Linked Lists</title>
96 !Iinclude/linux/list.h
101 <title>Basic C Library Functions</title>
104 When writing drivers, you cannot in general use routines which are
105 from the C Library. Some of the functions have been found generally
106 useful and they are listed below. The behaviour of these functions
107 may vary slightly from those defined by ANSI, and these deviations
108 are noted in the text.
111 <sect1><title>String Conversions</title>
115 <sect1><title>String Manipulation</title>
116 <!-- All functions are exported at now
121 <sect1><title>Bit Operations</title>
122 !Iinclude/asm-x86/bitops_32.h
126 <chapter id="kernel-lib">
127 <title>Basic Kernel Library Functions</title>
130 The Linux kernel provides more basic utility functions.
133 <sect1><title>Bitmap Operations</title>
138 <sect1><title>Command-line Parsing</title>
142 <sect1 id="crc"><title>CRC Functions</title>
152 <title>Memory Management in Linux</title>
153 <sect1><title>The Slab Cache</title>
154 !Iinclude/linux/slab.h
157 <sect1><title>User Space Memory Access</title>
158 !Iinclude/asm-x86/uaccess_32.h
159 !Earch/x86/lib/usercopy_32.c
161 <sect1><title>More Memory Management Functions</title>
169 !Emm/page-writeback.c
176 <title>Kernel IPC facilities</title>
178 <sect1><title>IPC utilities</title>
184 <title>FIFO Buffer</title>
185 <sect1><title>kfifo interface</title>
186 !Iinclude/linux/kfifo.h
191 <chapter id="relayfs">
192 <title>relay interface support</title>
195 Relay interface support
196 is designed to provide an efficient mechanism for tools and
197 facilities to relay large amounts of data from kernel space to
201 <sect1><title>relay interface</title>
207 <chapter id="netcore">
208 <title>Linux Networking</title>
209 <sect1><title>Networking Base Types</title>
210 !Iinclude/linux/net.h
212 <sect1><title>Socket Buffer Functions</title>
213 !Iinclude/linux/skbuff.h
218 !Enet/core/datagram.c
221 <sect1><title>Socket Filter</title>
224 <sect1><title>Generic Network Statistics</title>
225 !Iinclude/linux/gen_stats.h
226 !Enet/core/gen_stats.c
227 !Enet/core/gen_estimator.c
229 <sect1><title>SUN RPC subsystem</title>
230 <!-- The !D functionality is not perfect, garbage has to be protected by comments
231 !Dnet/sunrpc/sunrpc_syms.c
234 !Enet/sunrpc/svc_xprt.c
237 !Enet/sunrpc/socklib.c
239 !Enet/sunrpc/rpc_pipe.c
240 !Enet/sunrpc/rpcb_clnt.c
245 <chapter id="netdev">
246 <title>Network device support</title>
247 <sect1><title>Driver Support</title>
250 !Enet/sched/sch_generic.c
251 !Iinclude/linux/etherdevice.h
252 !Iinclude/linux/netdevice.h
254 <sect1><title>PHY Support</title>
255 !Edrivers/net/phy/phy.c
256 !Idrivers/net/phy/phy.c
257 !Edrivers/net/phy/phy_device.c
258 !Idrivers/net/phy/phy_device.c
259 !Edrivers/net/phy/mdio_bus.c
260 !Idrivers/net/phy/mdio_bus.c
262 <!-- FIXME: Removed for now since no structured comments in source
263 <sect1><title>Wireless</title>
264 X!Enet/core/wireless.c
267 <sect1><title>Synchronous PPP</title>
268 !Edrivers/net/wan/syncppp.c
272 <chapter id="modload">
273 <title>Module Support</title>
274 <sect1><title>Module Loading</title>
277 <sect1><title>Inter Module support</title>
279 Refer to the file kernel/module.c for more information.
281 <!-- FIXME: Removed for now since no structured comments in source
287 <chapter id="hardware">
288 <title>Hardware Interfaces</title>
289 <sect1><title>Interrupt Handling</title>
290 !Ekernel/irq/manage.c
293 <sect1><title>DMA Channels</title>
297 <sect1><title>Resources Management</title>
302 <sect1><title>MTRR Handling</title>
303 !Earch/x86/kernel/cpu/mtrr/main.c
306 <sect1><title>PCI Support Library</title>
308 !Edrivers/pci/pci-driver.c
309 !Edrivers/pci/remove.c
310 !Edrivers/pci/pci-acpi.c
311 !Edrivers/pci/search.c
314 <!-- FIXME: Removed for now since no structured comments in source
315 X!Edrivers/pci/hotplug.c
317 !Edrivers/pci/probe.c
320 <sect1><title>PCI Hotplug Support Library</title>
321 !Edrivers/pci/hotplug/pci_hotplug_core.c
323 <sect1><title>MCA Architecture</title>
324 <sect2><title>MCA Device Functions</title>
326 Refer to the file arch/x86/kernel/mca_32.c for more information.
328 <!-- FIXME: Removed for now since no structured comments in source
329 X!Earch/x86/kernel/mca_32.c
332 <sect2><title>MCA Bus DMA</title>
333 !Iinclude/asm-x86/mca_dma.h
338 <chapter id="firmware">
339 <title>Firmware Interfaces</title>
340 <sect1><title>DMI Interfaces</title>
341 !Edrivers/firmware/dmi_scan.c
343 <sect1><title>EDD Interfaces</title>
344 !Idrivers/firmware/edd.c
348 <chapter id="security">
349 <title>Security Framework</title>
350 !Isecurity/security.c
354 <title>Audit Interfaces</title>
357 !Ikernel/auditfilter.c
360 <chapter id="accounting">
361 <title>Accounting Framework</title>
365 <chapter id="pmfuncs">
366 <title>Power Management</title>
370 <chapter id="devdrivers">
371 <title>Device drivers infrastructure</title>
372 <sect1><title>Device Drivers Base</title>
374 X!Iinclude/linux/device.h
376 !Edrivers/base/driver.c
377 !Edrivers/base/core.c
378 !Edrivers/base/class.c
379 !Edrivers/base/firmware_class.c
380 !Edrivers/base/transport_class.c
381 <!-- Cannot be included, because
382 attribute_container_add_class_device_adapter
383 and attribute_container_classdev_to_container
384 exceed allowed 44 characters maximum
385 X!Edrivers/base/attribute_container.c
389 X!Edrivers/base/interface.c
391 !Edrivers/base/platform.c
394 <sect1><title>Device Drivers Power Management</title>
395 !Edrivers/base/power/main.c
397 <sect1><title>Device Drivers ACPI Support</title>
398 <!-- Internal functions only
399 X!Edrivers/acpi/sleep/main.c
400 X!Edrivers/acpi/sleep/wakeup.c
401 X!Edrivers/acpi/motherboard.c
402 X!Edrivers/acpi/bus.c
404 !Edrivers/acpi/scan.c
405 !Idrivers/acpi/scan.c
406 <!-- No correct structured comments
407 X!Edrivers/acpi/pci_bind.c
410 <sect1><title>Device drivers PnP support</title>
412 <!-- No correct structured comments
413 X!Edrivers/pnp/system.c
416 !Idrivers/pnp/driver.c
417 !Edrivers/pnp/manager.c
418 !Edrivers/pnp/support.c
420 <sect1><title>Userspace IO devices</title>
422 !Iinclude/linux/uio_driver.h
426 <chapter id="blkdev">
427 <title>Block Devices</title>
431 !Eblock/blk-settings.c
433 !Eblock/blk-barrier.c
437 <chapter id="chrdev">
438 <title>Char devices</title>
442 <chapter id="miscdev">
443 <title>Miscellaneous Devices</title>
444 !Edrivers/char/misc.c
447 <chapter id="parportdev">
448 <title>Parallel Port Devices</title>
449 !Iinclude/linux/parport.h
450 !Edrivers/parport/ieee1284.c
451 !Edrivers/parport/share.c
452 !Idrivers/parport/daisy.c
455 <chapter id="message_devices">
456 <title>Message-based devices</title>
457 <sect1><title>Fusion message devices</title>
458 !Edrivers/message/fusion/mptbase.c
459 !Idrivers/message/fusion/mptbase.c
460 !Edrivers/message/fusion/mptscsih.c
461 !Idrivers/message/fusion/mptscsih.c
462 !Idrivers/message/fusion/mptctl.c
463 !Idrivers/message/fusion/mptspi.c
464 !Idrivers/message/fusion/mptfc.c
465 !Idrivers/message/fusion/mptlan.c
467 <sect1><title>I2O message devices</title>
468 !Iinclude/linux/i2o.h
469 !Idrivers/message/i2o/core.h
470 !Edrivers/message/i2o/iop.c
471 !Idrivers/message/i2o/iop.c
472 !Idrivers/message/i2o/config-osm.c
473 !Edrivers/message/i2o/exec-osm.c
474 !Idrivers/message/i2o/exec-osm.c
475 !Idrivers/message/i2o/bus-osm.c
476 !Edrivers/message/i2o/device.c
477 !Idrivers/message/i2o/device.c
478 !Idrivers/message/i2o/driver.c
479 !Idrivers/message/i2o/pci.c
480 !Idrivers/message/i2o/i2o_block.c
481 !Idrivers/message/i2o/i2o_scsi.c
482 !Idrivers/message/i2o/i2o_proc.c
486 <chapter id="snddev">
487 <title>Sound Devices</title>
488 !Iinclude/sound/core.h
490 !Iinclude/sound/pcm.h
492 !Esound/core/device.c
494 !Esound/core/rawmidi.c
496 !Esound/core/memory.c
497 !Esound/core/pcm_memory.c
499 !Esound/core/isadma.c
500 !Esound/core/control.c
501 !Esound/core/pcm_lib.c
503 !Esound/core/pcm_native.c
504 !Esound/core/memalloc.c
505 <!-- FIXME: Removed for now since no structured comments in source
506 X!Isound/sound_firmware.c
510 <chapter id="uart16x50">
511 <title>16x50 UART Driver</title>
512 !Iinclude/linux/serial_core.h
513 !Edrivers/serial/serial_core.c
514 !Edrivers/serial/8250.c
517 <chapter id="z85230">
518 <title>Z85230 Support Library</title>
519 !Edrivers/net/wan/z85230.c
523 <title>Frame Buffer Library</title>
526 The frame buffer drivers depend heavily on four data structures.
527 These structures are declared in include/linux/fb.h. They are
528 fb_info, fb_var_screeninfo, fb_fix_screeninfo and fb_monospecs.
529 The last three can be made available to and from userland.
533 fb_info defines the current state of a particular video card.
534 Inside fb_info, there exists a fb_ops structure which is a
535 collection of needed functions to make fbdev and fbcon work.
536 fb_info is only visible to the kernel.
540 fb_var_screeninfo is used to describe the features of a video card
541 that are user defined. With fb_var_screeninfo, things such as
542 depth and the resolution may be defined.
546 The next structure is fb_fix_screeninfo. This defines the
547 properties of a card that are created when a mode is set and can't
548 be changed otherwise. A good example of this is the start of the
549 frame buffer memory. This "locks" the address of the frame buffer
550 memory, so that it cannot be changed or moved.
554 The last structure is fb_monospecs. In the old API, there was
555 little importance for fb_monospecs. This allowed for forbidden things
556 such as setting a mode of 800x600 on a fix frequency monitor. With
557 the new API, fb_monospecs prevents such things, and if used
558 correctly, can prevent a monitor from being cooked. fb_monospecs
559 will not be useful until kernels 2.5.x.
562 <sect1><title>Frame Buffer Memory</title>
563 !Edrivers/video/fbmem.c
566 <sect1><title>Frame Buffer Console</title>
567 X!Edrivers/video/console/fbcon.c
570 <sect1><title>Frame Buffer Colormap</title>
571 !Edrivers/video/fbcmap.c
574 drivers/video/fbgen.c has no docs, which stuffs up the sgml. Comment
575 out until somebody adds docs. KAO
576 <sect1><title>Frame Buffer Generic Functions</title>
577 X!Idrivers/video/fbgen.c
580 <sect1><title>Frame Buffer Video Mode Database</title>
581 !Idrivers/video/modedb.c
582 !Edrivers/video/modedb.c
584 <sect1><title>Frame Buffer Macintosh Video Mode Database</title>
585 !Edrivers/video/macmodes.c
587 <sect1><title>Frame Buffer Fonts</title>
589 Refer to the file drivers/video/console/fonts.c for more information.
591 <!-- FIXME: Removed for now since no structured comments in source
592 X!Idrivers/video/console/fonts.c
597 <chapter id="input_subsystem">
598 <title>Input Subsystem</title>
599 !Iinclude/linux/input.h
600 !Edrivers/input/input.c
601 !Edrivers/input/ff-core.c
602 !Edrivers/input/ff-memless.c
606 <title>Serial Peripheral Interface (SPI)</title>
608 SPI is the "Serial Peripheral Interface", widely used with
609 embedded systems because it is a simple and efficient
610 interface: basically a multiplexed shift register.
611 Its three signal wires hold a clock (SCK, often in the range
612 of 1-20 MHz), a "Master Out, Slave In" (MOSI) data line, and
613 a "Master In, Slave Out" (MISO) data line.
614 SPI is a full duplex protocol; for each bit shifted out the
615 MOSI line (one per clock) another is shifted in on the MISO line.
616 Those bits are assembled into words of various sizes on the
617 way to and from system memory.
618 An additional chipselect line is usually active-low (nCS);
619 four signals are normally used for each peripheral, plus
620 sometimes an interrupt.
623 The SPI bus facilities listed here provide a generalized
624 interface to declare SPI busses and devices, manage them
625 according to the standard Linux driver model, and perform
626 input/output operations.
627 At this time, only "master" side interfaces are supported,
628 where Linux talks to SPI peripherals and does not implement
629 such a peripheral itself.
630 (Interfaces to support implementing SPI slaves would
631 necessarily look different.)
634 The programming interface is structured around two kinds of driver,
635 and two kinds of device.
636 A "Controller Driver" abstracts the controller hardware, which may
637 be as simple as a set of GPIO pins or as complex as a pair of FIFOs
638 connected to dual DMA engines on the other side of the SPI shift
639 register (maximizing throughput). Such drivers bridge between
640 whatever bus they sit on (often the platform bus) and SPI, and
641 expose the SPI side of their device as a
642 <structname>struct spi_master</structname>.
643 SPI devices are children of that master, represented as a
644 <structname>struct spi_device</structname> and manufactured from
645 <structname>struct spi_board_info</structname> descriptors which
646 are usually provided by board-specific initialization code.
647 A <structname>struct spi_driver</structname> is called a
648 "Protocol Driver", and is bound to a spi_device using normal
652 The I/O model is a set of queued messages. Protocol drivers
653 submit one or more <structname>struct spi_message</structname>
654 objects, which are processed and completed asynchronously.
655 (There are synchronous wrappers, however.) Messages are
656 built from one or more <structname>struct spi_transfer</structname>
657 objects, each of which wraps a full duplex SPI transfer.
658 A variety of protocol tweaking options are needed, because
659 different chips adopt very different policies for how they
660 use the bits transferred with SPI.
662 !Iinclude/linux/spi/spi.h
663 !Fdrivers/spi/spi.c spi_register_board_info
668 <title>I<superscript>2</superscript>C and SMBus Subsystem</title>
671 I<superscript>2</superscript>C (or without fancy typography, "I2C")
672 is an acronym for the "Inter-IC" bus, a simple bus protocol which is
673 widely used where low data rate communications suffice.
674 Since it's also a licensed trademark, some vendors use another
675 name (such as "Two-Wire Interface", TWI) for the same bus.
676 I2C only needs two signals (SCL for clock, SDA for data), conserving
677 board real estate and minimizing signal quality issues.
678 Most I2C devices use seven bit addresses, and bus speeds of up
679 to 400 kHz; there's a high speed extension (3.4 MHz) that's not yet
681 I2C is a multi-master bus; open drain signaling is used to
682 arbitrate between masters, as well as to handshake and to
683 synchronize clocks from slower clients.
687 The Linux I2C programming interfaces support only the master
688 side of bus interactions, not the slave side.
689 The programming interface is structured around two kinds of driver,
690 and two kinds of device.
691 An I2C "Adapter Driver" abstracts the controller hardware; it binds
692 to a physical device (perhaps a PCI device or platform_device) and
693 exposes a <structname>struct i2c_adapter</structname> representing
694 each I2C bus segment it manages.
695 On each I2C bus segment will be I2C devices represented by a
696 <structname>struct i2c_client</structname>. Those devices will
697 be bound to a <structname>struct i2c_driver</structname>,
698 which should follow the standard Linux driver model.
699 (At this writing, a legacy model is more widely used.)
700 There are functions to perform various I2C protocol operations; at
701 this writing all such functions are usable only from task context.
705 The System Management Bus (SMBus) is a sibling protocol. Most SMBus
706 systems are also I2C conformant. The electrical constraints are
707 tighter for SMBus, and it standardizes particular protocol messages
708 and idioms. Controllers that support I2C can also support most
709 SMBus operations, but SMBus controllers don't support all the protocol
710 options that an I2C controller will.
711 There are functions to perform various SMBus protocol operations,
712 either using I2C primitives or by issuing SMBus commands to
713 i2c_adapter devices which don't support those I2C operations.
716 !Iinclude/linux/i2c.h
717 !Fdrivers/i2c/i2c-boardinfo.c i2c_register_board_info
718 !Edrivers/i2c/i2c-core.c