Introduction to Linux Device Drivers

Part 2, Platform and Character Drivers

Based on 3.14 Linux kernel

John Linn, Strategic Applications Engineer 10/2014

Copyright 2014 Xilinx

.

Agenda
Device Nodes
Platform Device Drivers
Character Device Drivers
Sys FileSystem Attributes
Debugging

Copyright 2014 Xilinx

.

Prerequisites
Experience building and running Linux
Experience with the C programming language
Goals
Make you aware of the architecture and frameworks of Linux
Point you to good reference material where you can learn all the details
The references are in the last slide
Linux Device Drivers is a book that is heavily used by all Linux kernel developers

The following are not goals of this training

Make you a device driver developer
Make you ready to submit a driver upstream to the kernel community

Copyright 2014 Xilinx

.

Introduction
A lot of good documentation exists in the public domain if you
know where to find it

A lot of the information in this presentation is based on others

work including Free Electrons
Free Electrons provides excellent training materials for free and
licensed as Creative Commons CC-BY-SA
http://free-electrons.com/docs
License: Creative Commons Attribution - Share Alike 3.0

http://creativecommons.org/licenses/by-sa/3.0/legalcode

You are free:

to copy, distribute, display, and perform the work

to make derivative works

to make commercial use of the work

Under the following conditions:

Attribution. You must give the original author credit.

Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license
identical to this one.

For any reuse or distribution, you must make clear to others the license terms of this work.

Any of these conditions can be waived if you get permission from the copyright holder.

Your fair use and other rights are in no way affected by the above.

Copyright 2014 Xilinx

.

Device Nodes
Devices in the kernel are block or character devices and are
identified using a major and a minor number
The major number indicates the family of the device

The minor number indicates the number of the device to allow

multiple instances of a major device type
Major and minor numbers can be statically or dynamically allocated
The statically allocated numbers are typically identical across Linux systems

Device Nodes are documented in the kernel tree at

Documentation/devices.txt

Copyright 2014 Xilinx

.

Device Files
Most system objects in UNIX are represented as files
This allows applications to manipulate system objects with the
normal file operations (open, read, write, close, etc.)

Devices are represented as files to the applications through

device files
A device file is a special type of file that associates a file name
visible to userspace applications to the triplet (type, major,
minor) that the kernel understands
Device files are stored in the /dev directory of the root file system

Copyright 2014 Xilinx

.

Device File Examples

Device files in the file system are illustrated below (ls /dev al)

Example C code that uses the file API to write data to a serial port

Copyright 2014 Xilinx

.

Device File Creation

Device files can be created manually using the mknod command
mknod /dev/<device> [c|b] major minor
Needs root privileges

Components can be added to create/remove device files

automatically when devices appear and disappear
devtmpfs virtual filesystem (built into the Xilinx kernel by default)
udev, solution used by desktop and server Linux systems
Udev runs as a daemon and listens for uevents the kernel sends out when a new
device is initialized or removed from the system

mdev, a lighter solution than udev, provided in BusyBox

BusyBox combines tiny versions of many common UNIX utilities into a single
small executable. It provides replacements for most of the utilities you usually
find in GNU fileutils, shellutils, etc.

Copyright 2014 Xilinx

.

Platform Devices
Hardware devices may be connected through a bus allowing
enumeration, hotplugging, or providing unique identifiers for devices
(such as PCI, PCIe and USB)
On embedded systems, devices are often not connected through a
bus which allows the devices to be uniquely identified.
Many devices are directly part of a system-on-chip: UARTs, Ethernet
controllers, SPI or I2C controllers, graphic or audio devices, etc.

In this case devices, instead of being dynamically detected, must be

statically described in either the kernel source code or the device
tree
The platform bus, a software abstraction, was created to handle such
devices. It supports platform drivers that handle platform devices.
The platform bus works like other buses (USB, PCI), except that
devices are enumerated statically rather than being discovered
dynamically

Copyright 2014 Xilinx

.

Platform Devices And Device Tree

As platform devices cannot be detected dynamically, they are
defined statically using a device tree
Platform devices can also be defined in source code (as was
done before device tree in the ARM kernel)
This is not typically done anymore as device tree operation is encouraged

Each device managed by a particular driver typically uses

different hardware resources such as interrupts and I/O
addresses
Device tree processing in the kernel is responsible for adding
platform devices to the platform bus

Copyright 2014 Xilinx

.

Platform Driver
A platform driver is a device driver for a specific platform device on the
platform bus
Most Xilinx Linux device drivers used by customers are platform drivers

A platform driver does not inherently have any interface to user space
without hooking into a kernel framework, such as the character device
framework
The name platform only specifies the bus (the platform bus) that the device is
located on

Character, block, and network device drivers can all be platform device drivers if
the device they support is located on the platform bus

Platform drivers follow the standard driver model convention except

discovery/enumeration is handled outside the drivers
In ARM and Microblaze Linux architectures, device tree processing does the
discovery/enumeration of the platform bus

Platform devices and drivers are described in the kernel tree at

Documentation/driver-model/platform.txt
Copyright 2014 Xilinx
.

Platform Driver Initialization

A Platform driver is connected to the kernel by the
platform_driver_register() function
The kernel calls the probe() function of the driver when it
discovers the corresponding platform device
The probe() function is responsible for initializing the device,
mapping I/O memory, and registering the interrupt handlers
The bus infrastructure provides methods to get the addresses, interrupt
numbers and other device-specific information

The probe() function also registers the device to the kernel

framework
An example framework is the character device processing for a character
driver

Copyright 2014 Xilinx

.

Platform Driver Exit

The kernel calls the remove() function of the driver when the
corresponding platform device is no longer used by the kernel

The remove() function is responsible for unregistering the device

from the kernel framework and shuting it down
A platform driver is disconnected from the kernel by the
platform_driver_unregister() function

Copyright 2014 Xilinx

.

Platform Driver Resources Page 1

The platform driver has access to the I/O resources (memory
address and interrupt) in the device tree through a kernel API
This is an area of the API that has been changing such that you
can see other methods which may require more effort
platform_get_resource() gets the memory range for the device
from the device tree
platform_get_irq() gets the interrupt for the device from the
device tree
These kernel functions automatically read standard platform
device parameters from the platform device in the device tree
Other non-standard or user defined parameters can be read from
the device tree using other kernel functions named of_*

Copyright 2014 Xilinx

.

Platform Driver Resources Page 2

devm_ioremap_resource() maps the physical memory range of
the device into the virtual memory map
The memory attributes for this memory range default to non-cached

devm_request_irq() connects the interrupt handler to the

interrupt processing of the kernel
The devm*() functions of the kernel framework are kernel
managed resources which the kernel tracks and then
automatically handles them when the device goes away

Copyright 2014 Xilinx

.

Platform Device Driver In A Kernel Module

Starting with a simple kernel module
1.
static struct platform_driver simple_driver = {
};

Make it a simple empty platform

driver

2.

static int __init simple_init(void)

{
return platform_driver_register(&simple_driver);
}

Platform driver simple_driver is

connected to the kernel by the
platform_driver_register() function

3.

Platform driver simple_driver is

disconnected from the kernel by the
platform_driver_unregister() function

static void __exit simple_exit(void)

{
platform_driver_unregister(&simple_driver);
}

The module initialization function

simple_init() is called when the
module is inserted

module_init(simple_init);
module_exit(simple_exit);

The module exit function simple_exit()

is called when the module is removed

Copyright 2014 Xilinx

.

Platform Devices Driver Basics

static int simple_probe(struct platform_device *pdev)
{
}
static int simple_remove(struct platform_device *pdev)
{
}
static struct of_device_id simple_of_match[] = {
{ .compatible = xilinx,simple", },
{ /* end of list */ },
};
static struct platform_driver simple_driver = {
.driver = {
.name = DRIVER_NAME,
.owner = THIS_MODULE,
.of_match_table = simple_of_match,
},
.probe
= simple_probe,
.remove
= simple_remove,
};

Copyright 2014 Xilinx

.

1.

Create the simple_probe() and

simple_remove() functions which
will be called by the kernel when
the driver is bound to a device

2.

Create the simple_of_match data

structure which is used to bind
the driver to the device and
matches the device tree

3.

Create the platform driver data

structure describing the platform
driver simple_driver

4.

The compatible member of

simple_of_match data is
connected to the kernel in the
structure simple_driver

5.

The simple_probe() and

simple_remove() functions are
connected to the kernel in the
structure simple_driver

Platform Device Driver Memory/Interrupt Details

int simple_irq() { };
int simple_probe()
{
resource = platform_get_resource(pdev, IORESOURCE_MEM, 0);

A simple
example
without error
processing

base_address = devm_ioremap_resource(dev, resource);

irq = platform_get_irq(pdev, 0);
devm_request_irq(dev, irq, &simple_irq, 0, DRIVER_NAME, lp);
}

Get the device memory range from the device tree by calling
platform_get_resource()
The devm_ioremap_resource() function is called to map the device
physical memory into the virtual address space
Get the interrupt number from the device tree by calling
platform_get_irq()
The interrupt function simple_irq() is connected to the kernel by calling
devm_request_irq() function
Copyright 2014 Xilinx
.

Character Device Driver

Character drivers can be useful for many customer IP blocks
From the point of view of an application, a character device is
essentially a file

The driver of a character device implements operations that let

applications access the device as a file: open, close, read, write,
etc.
A character driver implements the operations in the struct
file_operations structure and registers them
The Linux virtual filesystem layer calls the driver's operations
when a userspace application makes the corresponding system
call

A platform device driver can also be a character device driver if it

implements the interface and registers with the kernel framework

Copyright 2014 Xilinx

.

Character Device Driver File Operations

There are a number of operations that a character device can
optionally support
The open(), read(), write() and release() functions are typically
implemented as a minimum

open() function
Called when a userspace application opens a device file
Contains details such as the current position, the opening mode, etc.

Has a void *private_data pointer that one can freely use

release() function
Called when userspace application closes the file

ioctl() function
Called by a userspace application to perform some special I/O operation
which does not fit neatly into the read/write interface of a character device
Examples might be to control the baud rate of the serial port such that no
data is sent through the serial port, but its configuration is altered
Copyright 2014 Xilinx
.

File Operations, Read and Write Details

read() function
Called when a userspace application calls the read() library function for the
device

Reads data from the device, writes a specified maximum number of bytes
in the user-space buffer, and updates the file status
Returns the number of bytes read
Can block when there isn't enough data to read from the device

write() function
Called when a userspace application calls the write() library function for
the device
Writes a specified number of bytes from a userspace buffer, writes the
data to the device, updates the file status
Returns the number of bytes written
Can block when the device is not ready to accept the data

Copyright 2014 Xilinx

.

Copying Data Between Kernel and User Space

Moving data between userspace
and kernel space is the primary
method for I/O since the application
is in userspace and the device
drivers are in kernel space
The copy_to_user() function copies
a buffer of bytes from kernel space
to userspace
The copy_from_user() function
copies a buffer of bytes from
userspace to kernel space
Functions also exist for copying a
single datum
Zero copy methods exist but are
more complex and less typical
Copyright 2014 Xilinx
.

Character Device Driver Details

A character device framework is provided by the kernel. This
framework allows the device to be accessed using the file I/O
operations.
alloc_chrdev_region() allocates a character device number
unregister_chrdev_region() frees a previously allocated character
device number
cdev_init() initializes the character device structure
cdev_add() adds the character device to the kernel
cdev_del() removes the character device from the kernel

Copyright 2014 Xilinx

.

Creating A Character Device Simplified Example

Create empty file operation
functions simple_open(),
simple_write(), simple_read(),
simple_release()

int simple_open() { };
int simple_write() { };
int simple_read() { };
int simple_release() { };

Create the file_operations data

structure simple_fops

static struct file_operations simple_fops = {

.owner

= THIS_MODULE,

.open

= simple_open,

.write

The platform driver simple_probe()

function calls the character device
functions to create the character
device

= simple_write,

.read = simple_read,
.release = simple_release,
};

The cdev_init() function initializes

the character device including
setting up the file functions such as
simple_read() and simple_write()

int simple_probe()
{
struct cdev cdev;
cdev_init(&cdev, &simple_fops);

The cdev_add() function connects

the character device to the kernel

cdev_add(&cdev, .);
}

Copyright 2014 Xilinx

.

Creating The Device Node Details

A device node, as reviewed earlier, is needed to allow user space
to communicate with kernel space
Many people create device nodes manually as they were done in
the past, but using the API takes care of this
A class for the device in /sys is needed to allow a device node in
/dev to be automatically created
The class for the device in /sys is seen as a directory

The driver creates the class using the kernel API.

class_create() creates a class in the /sys/class directory
class_destroy() destroys the class
The driver creates the device node using the kernel API.
device_create() creates a device node in the /dev directory
device_destroy() removes a device node in the /dev directory

Copyright 2014 Xilinx

.

Sys FileSystem Attributes Rather Than Ioctl

The ioctl interface of device drivers is an older interface can be
less preferred in the kernel community
It is hard to document the interface for each driver which is typically unique

File attributes in the sys filesystem is the preferred method rather

than ioctl
They are more self documenting
They are easier to use as they can be accessed from a command line
using utilities like cat, echo and dd
For example, cat /sys/devices/amba.0/41200000.gpio/irqreg displays the
contents of the interrupt register for the GPIO device
Slower to access due to open and close

device_create_file() creates a file attribute under the current

device in /sys
device_remove_file() removes a file attribute under the current
device in /sys
Copyright 2014 Xilinx
.

Creating A Sys File Attribute Details

A file attribute is created in the directory of the device in
filesystem at /sys/devices/<bus>/<device>
The path is dependent on the node of the device in the device tree

Before calling device_create_file() to create the attribute, the

attribute data structure must be created
The macro DEVICE_ATTR() is used to create the attribute and
requires the following inputs.
A name for the attribute in the filesystem
Permissions which determine if the attribute can be read and/or written
A function to read the data from the driver
A function to write the data into the driver

Copyright 2014 Xilinx

.

Creating A File Attribute Simplified Example

A platform driver creates a file attribute /sys/devices/<bus>/<device>/irqreg which
can be read and written from user space
Create the empty access functions
simple_show_reg() and
simple_store_reg() which will be
simple_show_reg() { }
called to read/write the data
The permissions
simple_store_reg() { }
to allow read/write

Create the attribute data structure for

attribute irqreq which has read and
write access and uses the access
functions just created

DEVICE_ATTR(irqreg, S_IWUSR | S_IRUGO,

simple_show_reg, simple_store_reg);

The platform driver simple_probe()

function creates the file attribute
named irqreg in the sys filesystem
under the device by calling
device_create_file()

simple_probe()
{
device_create_file(dev, &dev_attr_irqreg);
}

Macros in Linux can be less obvious as details

are hidden. DEVICE_ATTR() causes the data
structure dev_attr_irqreg to be created.

Copyright 2014 Xilinx

.

The access functions,

simple_show_reg() and
simple_store_reg() are connected to
the kernel

Debugging With Printk

printk()
Kernel version of printf()
Priority of kernel messages (log level) can be specified with the following
symbols defined in <linux/kernel.h>

KERN_EMERG: Emergency message

KERN_ALERT: Alert message
KERN_CRIT: Critical situation
KERN_ERR: Error report
KERN_WARNING: Warning message
KERN_NOTICE: Noticeable message
KERN_INFO: Information
KERN_DEBUG: Debug message

Does not support floating point numbers

Example:
printk(KERN_DEBUG line %s:%i\n, __FILE__, __LINE__);

The log level can be altered from the command line in the proc file
system
echo 7 > /proc/sys/kernel/printk changes the current level so all messages
are printed

Copyright 2014 Xilinx

.

Other Debug Tools

The sys and proc file systems contain a lot of good information
/proc/interrupts shows the interrupt number assigned to a device
and the number of interrupts that have occurred

/proc/device-tree has the nodes of the device tree

Some nodes are binary such that hexdump must be used to view them

/proc/cmdline has the kernel command line, which can be handy

/proc/iomem shows the I/O memory claimed by device drivers

Copyright 2014 Xilinx

.

References
Linux Device Drivers Version 3
https://lwn.net/Kernel/LDD3/

Free Electrons
http://free-electrons.com/
http://lxr.free-electrons.com/

Linux Foundation
http://training.linuxfoundation.org/free-linux-training/linux-training-videos/howto-build-character-drivers-for-the-linux-kernel
http://training.linuxfoundation.org/free-linux-training/linux-trainingvideos/interrupt-handling-in-linux-device-drivers

Copyright 2014 Xilinx

.