StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12923107
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-16T20:44:12.953
FavoriteCount
0
LastActivityDate
2012-10-16T22:46:15.953
LastEditDate
2012-10-16T22:46:15.953
LastEditorUserId
1599004
OwnerUserId
1599004
ParentId
12917198
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
A device driver is not a "program" that has a <code>main {}</code> with a start point and exit point. It's more like an API or a library or a collection of routines. In this case, it's a set of entry points declared by <code>MODULE_INIT()</code>, <code>MODULE_EXIT()</code>, perhaps <code>EXPORT_SYMBOL()</code> and structures that list entry points for operations. For block devices, the driver is expected to provide the list of operations it can perform by declaring its functions for those operations in (from <code>include/linux/blkdev.h</code>): <pre><code>struct block_device_operations { int (*open) (); int (*release) (); int (*ioctl) (); int (*compat_ioctl) (); int (*direct_access) (); unsigned int (*check_events) (); /* ->media_changed() is DEPRECATED, use ->check_events() instead */ int (*media_changed) (); void (*unlock_native_capacity) (); int (*revalidate_disk) (); int (*getgeo)(); /* this callback is with swap_lock and sometimes page table lock held */ void (*swap_slot_free_notify) (); struct module *owner; }; </code></pre> For char devices, the driver is expected to provide the list of operations it can perform by declaring its functions for those operations in (from <code>include/linux/fs.h</code>): <pre><code>struct file_operations { struct module *owner; loff_t (*llseek) (); ssize_t (*read) (); ssize_t (*write) (); ssize_t (*aio_read) (); ssize_t (*aio_write) (); int (*readdir) (); unsigned int (*poll) (); long (*unlocked_ioctl) (); long (*compat_ioctl) (); int (*mmap) (); int (*open) (); int (*flush) (); int (*release) (); int (*fsync) (); int (*aio_fsync) (); int (*fasync) (); int (*lock) (); ssize_t (*sendpage) (); unsigned long (*get_unmapped_area)(); int (*check_flags)(); int (*flock) (); ssize_t (*splice_write)(); ssize_t (*splice_read)(); int (*setlease)(); long (*fallocate)(); }; </code></pre> For platform devices, the driver is expected to provide the list of operations it can perform by declaring its functions for those operations in (from <code>include/linux/platform_device.h</code>): <pre><code>struct platform_driver { int (*probe)(); int (*remove)(); void (*shutdown)(); int (*suspend)(); int (*resume)(); struct device_driver driver; const struct platform_device_id *id_table; }; </code></pre> The driver, especially char drivers, does not have to support every operation listed. Note that there are macros to facilitate the coding of these structures by naming the structure entries. <blockquote> Does the driver program starts at the MOUDLUE_INIT() macro? </blockquote> The driver's init() routine specified in <code>MODULE_INIT()</code> will be called during boot (when statically linked in) or when the module is dynamically loaded. The driver passes its structure of operations to the device's subsystem when it registers itself during its init(). These device driver entry points, e.g. open() or read(), are typically executed when the user app invokes a C library call (in user space) and after a switch to kernel space. Note that the i2c driver you're looking at is a <a href="http://www.kernel.org/doc/Documentation/driver-model/platform.txt" rel="noreferrer">platform driver</a> for a bus that is used by leaf devices, and its functions exposed by <code>EXPORT_SYMBOL()</code> would be called by other drivers. Only the driver's init() routine specified in <code>MODULE_INIT()</code> is guaranteed to be called. The driver's exit() routine specified in <code>MODULE_EXIT()</code> would only be executed if/when the module is dynamically unloaded. The driver's op routines will be called asynchronously (just like its interrupt service routine) in unknown order. Hopefully user programs will invoke an open() before issuing a read() or an ioctl() operation, and invoke other operations in a sensible fashion. A well-written and robust driver should accommodate any order or sequence of operations, and produce sane results to ensure system integrity. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLinux Device Driver Program, where the program starts?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsawdust
UserOwnerUserId
1. USsawdust
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUndeletion
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.