'\" t
.\"     Title: __platform_driver_probe
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: January 2017
.\"    Manual: Device drivers infrastructure
.\"    Source: Kernel Hackers Manual 4.8.15
.\"  Language: English
.\"
.TH "__PLATFORM_DRIVER_PR" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "Device drivers infrastructure"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
__platform_driver_probe \- register driver for non\-hotpluggable device
.SH "SYNOPSIS"
.HP \w'int\ __platform_driver_probe('u
.BI "int __platform_driver_probe(struct\ platform_driver\ *\ " "drv" ", int\ (*" "probe" ")\ (struct\ platform_device\ *), struct\ module\ *\ " "module" ");"
.SH "ARGUMENTS"
.PP
\fIdrv\fR
.RS 4
platform driver structure
.RE
.PP
\fIprobe\fR
.RS 4
the driver probe routine, probably from an __init section
.RE
.PP
\fImodule\fR
.RS 4
module which will be the owner of the driver
.RE
.SH "DESCRIPTION"
.PP
Use this instead of
\fBplatform_driver_register\fR
when you know the device is not hotpluggable and has already been registered, and you want to remove its run\-once
\fBprobe\fR
infrastructure from memory after the driver has bound to the device\&.
.PP
One typical use for this would be with drivers for controllers integrated into system\-on\-chip processors, where the controller devices have been configured as part of board setup\&.
.PP
Note that this is incompatible with deferred probing\&.
.PP
Returns zero if the driver registered and bound to a device, else returns a negative error code and with the driver not registered\&.
.SH "COPYRIGHT"
.br