2011-05-26 22:08:35 +00:00
|
|
|
#include <linux/notifier.h>
|
2005-10-13 16:54:41 +00:00
|
|
|
|
2007-11-02 02:41:16 +00:00
|
|
|
/**
|
2010-11-15 22:13:18 +00:00
|
|
|
* struct subsys_private - structure to hold the private to the driver core portions of the bus_type/class structure.
|
2007-11-02 02:41:16 +00:00
|
|
|
*
|
2010-11-15 22:13:18 +00:00
|
|
|
* @subsys - the struct kset that defines this subsystem
|
2011-12-14 22:29:38 +00:00
|
|
|
* @devices_kset - the subsystem's 'devices' directory
|
|
|
|
* @interfaces - list of subsystem interfaces associated
|
|
|
|
* @mutex - protect the devices, and interfaces lists.
|
2010-11-15 22:13:18 +00:00
|
|
|
*
|
|
|
|
* @drivers_kset - the list of drivers associated
|
2007-11-02 02:41:16 +00:00
|
|
|
* @klist_devices - the klist to iterate over the @devices_kset
|
|
|
|
* @klist_drivers - the klist to iterate over the @drivers_kset
|
|
|
|
* @bus_notifier - the bus notifier list for anything that cares about things
|
2010-11-15 22:13:18 +00:00
|
|
|
* on this bus.
|
2007-11-02 02:41:16 +00:00
|
|
|
* @bus - pointer back to the struct bus_type that this structure is associated
|
2010-11-15 22:13:18 +00:00
|
|
|
* with.
|
|
|
|
*
|
|
|
|
* @glue_dirs - "glue" directory to put in-between the parent device to
|
|
|
|
* avoid namespace conflicts
|
|
|
|
* @class - pointer back to the struct class that this structure is associated
|
|
|
|
* with.
|
2007-11-02 02:41:16 +00:00
|
|
|
*
|
|
|
|
* This structure is the one that is the actual kobject allowing struct
|
2010-11-15 22:13:18 +00:00
|
|
|
* bus_type/class to be statically allocated safely. Nothing outside of the
|
|
|
|
* driver core should ever touch these fields.
|
2007-11-02 02:41:16 +00:00
|
|
|
*/
|
2010-11-15 22:13:18 +00:00
|
|
|
struct subsys_private {
|
2007-11-02 02:41:16 +00:00
|
|
|
struct kset subsys;
|
|
|
|
struct kset *devices_kset;
|
2011-12-14 22:29:38 +00:00
|
|
|
struct list_head interfaces;
|
|
|
|
struct mutex mutex;
|
2010-11-15 22:13:18 +00:00
|
|
|
|
|
|
|
struct kset *drivers_kset;
|
2007-11-02 02:41:16 +00:00
|
|
|
struct klist klist_devices;
|
|
|
|
struct klist klist_drivers;
|
|
|
|
struct blocking_notifier_head bus_notifier;
|
|
|
|
unsigned int drivers_autoprobe:1;
|
|
|
|
struct bus_type *bus;
|
2010-11-15 22:13:18 +00:00
|
|
|
|
|
|
|
struct kset glue_dirs;
|
|
|
|
struct class *class;
|
2007-11-02 02:41:16 +00:00
|
|
|
};
|
2010-11-15 22:13:18 +00:00
|
|
|
#define to_subsys_private(obj) container_of(obj, struct subsys_private, subsys.kobj)
|
2007-11-02 02:41:16 +00:00
|
|
|
|
2007-11-28 23:59:15 +00:00
|
|
|
struct driver_private {
|
|
|
|
struct kobject kobj;
|
|
|
|
struct klist klist_devices;
|
|
|
|
struct klist_node knode_bus;
|
|
|
|
struct module_kobject *mkobj;
|
|
|
|
struct device_driver *driver;
|
|
|
|
};
|
|
|
|
#define to_driver(obj) container_of(obj, struct driver_private, kobj)
|
2005-10-13 16:54:41 +00:00
|
|
|
|
2008-12-16 20:23:36 +00:00
|
|
|
/**
|
|
|
|
* struct device_private - structure to hold the private to the driver core portions of the device structure.
|
|
|
|
*
|
2008-12-16 20:24:56 +00:00
|
|
|
* @klist_children - klist containing all children of this device
|
|
|
|
* @knode_parent - node in sibling list
|
2008-12-16 20:25:49 +00:00
|
|
|
* @knode_driver - node in driver list
|
2008-12-16 20:26:21 +00:00
|
|
|
* @knode_bus - node in bus list
|
2012-03-08 20:17:22 +00:00
|
|
|
* @deferred_probe - entry in deferred_probe_list which is used to retry the
|
|
|
|
* binding of drivers which were unable to get all the resources needed by
|
|
|
|
* the device; typically because it depends on another driver getting
|
|
|
|
* probed first.
|
2015-06-29 14:59:02 +00:00
|
|
|
* @device - pointer back to the struct device that this structure is
|
2008-12-16 20:23:36 +00:00
|
|
|
* associated with.
|
|
|
|
*
|
|
|
|
* Nothing outside of the driver core should ever touch these fields.
|
|
|
|
*/
|
|
|
|
struct device_private {
|
2008-12-16 20:24:56 +00:00
|
|
|
struct klist klist_children;
|
|
|
|
struct klist_node knode_parent;
|
2008-12-16 20:25:49 +00:00
|
|
|
struct klist_node knode_driver;
|
2008-12-16 20:26:21 +00:00
|
|
|
struct klist_node knode_bus;
|
2012-03-08 20:17:22 +00:00
|
|
|
struct list_head deferred_probe;
|
2008-12-16 20:23:36 +00:00
|
|
|
struct device *device;
|
|
|
|
};
|
2008-12-16 20:24:56 +00:00
|
|
|
#define to_device_private_parent(obj) \
|
|
|
|
container_of(obj, struct device_private, knode_parent)
|
2008-12-16 20:25:49 +00:00
|
|
|
#define to_device_private_driver(obj) \
|
|
|
|
container_of(obj, struct device_private, knode_driver)
|
2008-12-16 20:26:21 +00:00
|
|
|
#define to_device_private_bus(obj) \
|
|
|
|
container_of(obj, struct device_private, knode_bus)
|
2008-12-16 20:23:36 +00:00
|
|
|
|
2009-05-11 21:16:57 +00:00
|
|
|
extern int device_private_init(struct device *dev);
|
|
|
|
|
2007-11-02 02:41:16 +00:00
|
|
|
/* initialisation functions */
|
2005-10-13 16:54:41 +00:00
|
|
|
extern int devices_init(void);
|
|
|
|
extern int buses_init(void);
|
|
|
|
extern int classes_init(void);
|
|
|
|
extern int firmware_init(void);
|
2006-05-09 10:53:49 +00:00
|
|
|
#ifdef CONFIG_SYS_HYPERVISOR
|
|
|
|
extern int hypervisor_init(void);
|
|
|
|
#else
|
|
|
|
static inline int hypervisor_init(void) { return 0; }
|
|
|
|
#endif
|
2005-10-13 16:54:41 +00:00
|
|
|
extern int platform_bus_init(void);
|
2012-01-10 02:59:49 +00:00
|
|
|
extern void cpu_dev_init(void);
|
ACPI / hotplug / driver core: Handle containers in a special way
ACPI container devices require special hotplug handling, at least
on some systems, since generally user space needs to carry out
system-specific cleanup before it makes sense to offline devices in
the container. However, the current ACPI hotplug code for containers
first attempts to offline devices in the container and only then it
notifies user space of the container offline.
Moreover, after commit 202317a573b2 (ACPI / scan: Add acpi_device
objects for all device nodes in the namespace), ACPI device objects
representing containers are present as long as the ACPI namespace
nodes corresponding to them are present, which may be forever, even
if the container devices are physically detached from the system (the
return values of the corresponding _STA methods change in those
cases, but generally the namespace nodes themselves are still there).
Thus it is useful to introduce entities representing containers that
will go away during container hot-unplug.
The goal of this change is to address both the above issues.
The idea is to create a "companion" container system device for each
of the ACPI container device objects during the initial namespace
scan or on a hotplug event making the container present. That system
device will be unregistered on container removal. A new bus type
for container devices is added for this purpose, because device
offline and online operations need to be defined for them. The
online operation is a trivial function that is always successful
and the offline uses a callback pointed to by the container device's
offline member.
For ACPI containers that callback simply walks the list of ACPI
device objects right below the container object (its children) and
checks if all of their physical companion devices are offline. If
that's not the case, it returns -EBUSY and the container system
devivce cannot be put offline. Consequently, to put the container
system device offline, it is necessary to put all of the physical
devices depending on its ACPI companion object offline beforehand.
Container system devices created for ACPI container objects are
initially online. They are created by the container ACPI scan
handler whose hotplug.demand_offline flag is set. That causes
acpi_scan_hot_remove() to check if the companion container system
device is offline before attempting to remove an ACPI container or
any devices below it. If the check fails, a KOBJ_CHANGE uevent is
emitted for the container system device in question and user space
is expected to offline all devices below the container and the
container itself in response to it. Then, user space can finalize
the removal of the container with the help of its ACPI device
object's eject attribute in sysfs.
Tested-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-12-29 14:25:48 +00:00
|
|
|
extern void container_dev_init(void);
|
2005-10-13 16:54:41 +00:00
|
|
|
|
2013-03-12 18:30:05 +00:00
|
|
|
struct kobject *virtual_device_parent(struct device *dev);
|
|
|
|
|
2008-01-25 06:50:12 +00:00
|
|
|
extern int bus_add_device(struct device *dev);
|
2009-07-30 19:27:18 +00:00
|
|
|
extern void bus_probe_device(struct device *dev);
|
2008-01-25 06:50:12 +00:00
|
|
|
extern void bus_remove_device(struct device *dev);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-01-25 06:50:12 +00:00
|
|
|
extern int bus_add_driver(struct device_driver *drv);
|
|
|
|
extern void bus_remove_driver(struct device_driver *drv);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-01-25 06:50:12 +00:00
|
|
|
extern void driver_detach(struct device_driver *drv);
|
|
|
|
extern int driver_probe_device(struct device_driver *drv, struct device *dev);
|
2012-03-05 15:47:41 +00:00
|
|
|
extern void driver_deferred_probe_del(struct device *dev);
|
2009-01-21 15:27:47 +00:00
|
|
|
static inline int driver_match_device(struct device_driver *drv,
|
|
|
|
struct device *dev)
|
|
|
|
{
|
2009-03-27 13:50:00 +00:00
|
|
|
return drv->bus->match ? drv->bus->match(dev, drv) : 1;
|
2009-01-21 15:27:47 +00:00
|
|
|
}
|
2015-03-30 23:20:04 +00:00
|
|
|
extern bool driver_allows_async_probing(struct device_driver *drv);
|
2005-03-21 18:52:54 +00:00
|
|
|
|
2013-08-08 22:22:56 +00:00
|
|
|
extern int driver_add_groups(struct device_driver *drv,
|
|
|
|
const struct attribute_group **groups);
|
|
|
|
extern void driver_remove_groups(struct device_driver *drv,
|
|
|
|
const struct attribute_group **groups);
|
|
|
|
|
2013-08-08 22:22:55 +00:00
|
|
|
extern int device_add_groups(struct device *dev,
|
|
|
|
const struct attribute_group **groups);
|
|
|
|
extern void device_remove_groups(struct device *dev,
|
|
|
|
const struct attribute_group **groups);
|
|
|
|
|
2006-06-20 20:59:20 +00:00
|
|
|
extern char *make_class_name(const char *name, struct kobject *kobj);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-06-17 23:42:54 +00:00
|
|
|
extern int devres_release_all(struct device *dev);
|
2007-04-13 20:15:19 +00:00
|
|
|
|
2011-12-14 22:29:38 +00:00
|
|
|
/* /sys/devices directory */
|
2007-11-01 15:29:06 +00:00
|
|
|
extern struct kset *devices_kset;
|
2007-11-28 20:23:18 +00:00
|
|
|
|
2007-12-31 18:05:43 +00:00
|
|
|
#if defined(CONFIG_MODULES) && defined(CONFIG_SYSFS)
|
2007-11-28 20:23:18 +00:00
|
|
|
extern void module_add_driver(struct module *mod, struct device_driver *drv);
|
|
|
|
extern void module_remove_driver(struct device_driver *drv);
|
|
|
|
#else
|
|
|
|
static inline void module_add_driver(struct module *mod,
|
|
|
|
struct device_driver *drv) { }
|
|
|
|
static inline void module_remove_driver(struct device_driver *drv) { }
|
|
|
|
#endif
|
Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev
Devtmpfs lets the kernel create a tmpfs instance called devtmpfs
very early at kernel initialization, before any driver-core device
is registered. Every device with a major/minor will provide a
device node in devtmpfs.
Devtmpfs can be changed and altered by userspace at any time,
and in any way needed - just like today's udev-mounted tmpfs.
Unmodified udev versions will run just fine on top of it, and will
recognize an already existing kernel-created device node and use it.
The default node permissions are root:root 0600. Proper permissions
and user/group ownership, meaningful symlinks, all other policy still
needs to be applied by userspace.
If a node is created by devtmps, devtmpfs will remove the device node
when the device goes away. If the device node was created by
userspace, or the devtmpfs created node was replaced by userspace, it
will no longer be removed by devtmpfs.
If it is requested to auto-mount it, it makes init=/bin/sh work
without any further userspace support. /dev will be fully populated
and dynamic, and always reflect the current device state of the kernel.
With the commonly used dynamic device numbers, it solves the problem
where static devices nodes may point to the wrong devices.
It is intended to make the initial bootup logic simpler and more robust,
by de-coupling the creation of the inital environment, to reliably run
userspace processes, from a complex userspace bootstrap logic to provide
a working /dev.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Jan Blunck <jblunck@suse.de>
Tested-By: Harald Hoyer <harald@redhat.com>
Tested-By: Scott James Remnant <scott@ubuntu.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-04-30 13:23:42 +00:00
|
|
|
|
|
|
|
#ifdef CONFIG_DEVTMPFS
|
|
|
|
extern int devtmpfs_init(void);
|
|
|
|
#else
|
|
|
|
static inline int devtmpfs_init(void) { return 0; }
|
|
|
|
#endif
|