003 File Manager
Current Path:
/usr/src/sys/kern
usr
/
src
/
sys
/
kern
/
📁
..
📄
Make.tags.inc
(2.13 KB)
📄
Makefile
(302 B)
📄
bus_if.m
(26.31 KB)
📄
capabilities.conf
(13.67 KB)
📄
clock_if.m
(1.7 KB)
📄
cpufreq_if.m
(2.27 KB)
📄
device_if.m
(10.41 KB)
📄
firmw.S
(2.15 KB)
📄
genassym.sh
(1.11 KB)
📄
genoffset.c
(1.68 KB)
📄
genoffset.sh
(3.58 KB)
📄
imgact_aout.c
(9.45 KB)
📄
imgact_binmisc.c
(18.64 KB)
📄
imgact_elf.c
(76.32 KB)
📄
imgact_elf32.c
(1.47 KB)
📄
imgact_elf64.c
(1.47 KB)
📄
imgact_shell.c
(8.41 KB)
📄
init_main.c
(24.31 KB)
📄
init_sysent.c
(95.3 KB)
📄
kern_acct.c
(19.03 KB)
📄
kern_alq.c
(24.97 KB)
📄
kern_clock.c
(21.12 KB)
📄
kern_clocksource.c
(23.34 KB)
📄
kern_condvar.c
(11.28 KB)
📄
kern_conf.c
(36.14 KB)
📄
kern_cons.c
(15.75 KB)
📄
kern_context.c
(3.59 KB)
📄
kern_cpu.c
(30.77 KB)
📄
kern_cpuset.c
(59.78 KB)
📄
kern_ctf.c
(8.73 KB)
📄
kern_descrip.c
(112.87 KB)
📄
kern_dtrace.c
(2.94 KB)
📄
kern_dump.c
(8.51 KB)
📄
kern_environment.c
(22.75 KB)
📄
kern_et.c
(7.1 KB)
📄
kern_event.c
(62.49 KB)
📄
kern_exec.c
(46.67 KB)
📄
kern_exit.c
(34.61 KB)
📄
kern_fail.c
(29.32 KB)
📄
kern_ffclock.c
(12.66 KB)
📄
kern_fork.c
(28.29 KB)
📄
kern_hhook.c
(13.58 KB)
📄
kern_idle.c
(2.74 KB)
📄
kern_intr.c
(40.44 KB)
📄
kern_jail.c
(112.67 KB)
📄
kern_kcov.c
(15.32 KB)
📄
kern_khelp.c
(9.45 KB)
📄
kern_kthread.c
(11.8 KB)
📄
kern_ktr.c
(11.93 KB)
📄
kern_ktrace.c
(31.41 KB)
📄
kern_linker.c
(54.3 KB)
📄
kern_lock.c
(46.99 KB)
📄
kern_lockf.c
(64.46 KB)
📄
kern_lockstat.c
(3.8 KB)
📄
kern_loginclass.c
(6.69 KB)
📄
kern_malloc.c
(37.09 KB)
📄
kern_mbuf.c
(43.16 KB)
📄
kern_mib.c
(24.26 KB)
📄
kern_module.c
(11.05 KB)
📄
kern_mtxpool.c
(5.82 KB)
📄
kern_mutex.c
(33.62 KB)
📄
kern_ntptime.c
(32.49 KB)
📄
kern_osd.c
(12.37 KB)
📄
kern_physio.c
(5.74 KB)
📄
kern_pmc.c
(8.89 KB)
📄
kern_poll.c
(15.86 KB)
📄
kern_priv.c
(9.14 KB)
📄
kern_proc.c
(80.01 KB)
📄
kern_procctl.c
(19.48 KB)
📄
kern_prot.c
(57.94 KB)
📄
kern_racct.c
(34.01 KB)
📄
kern_rangelock.c
(8.67 KB)
📄
kern_rctl.c
(53.87 KB)
📄
kern_resource.c
(36.66 KB)
📄
kern_rmlock.c
(28.27 KB)
📄
kern_rwlock.c
(40.72 KB)
📄
kern_sdt.c
(2.05 KB)
📄
kern_sema.c
(4.85 KB)
📄
kern_sendfile.c
(33.97 KB)
📄
kern_sharedpage.c
(10.37 KB)
📄
kern_shutdown.c
(43.34 KB)
📄
kern_sig.c
(101.89 KB)
📄
kern_switch.c
(13.85 KB)
📄
kern_sx.c
(40.27 KB)
📄
kern_synch.c
(18.17 KB)
📄
kern_syscalls.c
(6.74 KB)
📄
kern_sysctl.c
(67.24 KB)
📄
kern_tc.c
(55.73 KB)
📄
kern_thr.c
(14.14 KB)
📄
kern_thread.c
(41.75 KB)
📄
kern_time.c
(40.89 KB)
📄
kern_timeout.c
(43.08 KB)
📄
kern_tslog.c
(3.44 KB)
📄
kern_ubsan.c
(50.74 KB)
📄
kern_umtx.c
(107.14 KB)
📄
kern_uuid.c
(11.68 KB)
📄
kern_xxx.c
(10.44 KB)
📄
ksched.c
(6.56 KB)
📄
link_elf.c
(47.99 KB)
📄
link_elf_obj.c
(44.41 KB)
📄
linker_if.m
(3.96 KB)
📄
makesyscalls.sh
(23.57 KB)
📄
md4c.c
(7.89 KB)
📄
md5c.c
(9.56 KB)
📄
msi_if.m
(2.48 KB)
📄
p1003_1b.c
(8.84 KB)
📄
pic_if.m
(3.9 KB)
📄
posix4_mib.c
(5.59 KB)
📄
sched_4bsd.c
(45.03 KB)
📄
sched_ule.c
(82.65 KB)
📄
serdev_if.m
(3.49 KB)
📄
stack_protector.c
(613 B)
📄
subr_acl_nfs4.c
(37.42 KB)
📄
subr_acl_posix1e.c
(17.71 KB)
📄
subr_atomic64.c
(3.97 KB)
📄
subr_autoconf.c
(7.7 KB)
📄
subr_blist.c
(31.88 KB)
📄
subr_boot.c
(5.8 KB)
📄
subr_bufring.c
(2.21 KB)
📄
subr_bus.c
(145.4 KB)
📄
subr_bus_dma.c
(19.67 KB)
📄
subr_busdma_bufalloc.c
(5.24 KB)
📄
subr_capability.c
(11.93 KB)
📄
subr_clock.c
(10.61 KB)
📄
subr_compressor.c
(13.11 KB)
📄
subr_counter.c
(4.44 KB)
📄
subr_coverage.c
(6.17 KB)
📄
subr_csan.c
(25.39 KB)
📄
subr_devmap.c
(9.8 KB)
📄
subr_devstat.c
(16.21 KB)
📄
subr_disk.c
(8.54 KB)
📄
subr_dummy_vdso_tc.c
(1.7 KB)
📄
subr_early.c
(2.26 KB)
📄
subr_epoch.c
(25.02 KB)
📄
subr_eventhandler.c
(9.17 KB)
📄
subr_fattime.c
(9.98 KB)
📄
subr_filter.c
(12.2 KB)
📄
subr_firmware.c
(13.88 KB)
📄
subr_gtaskqueue.c
(20.19 KB)
📄
subr_hash.c
(4.8 KB)
📄
subr_hints.c
(12.87 KB)
📄
subr_intr.c
(40.61 KB)
📄
subr_kdb.c
(16.13 KB)
📄
subr_kobj.c
(7.1 KB)
📄
subr_lock.c
(18.81 KB)
📄
subr_log.c
(7.64 KB)
📄
subr_mchain.c
(11.06 KB)
📄
subr_module.c
(12.98 KB)
📄
subr_msgbuf.c
(10.6 KB)
📄
subr_param.c
(10.93 KB)
📄
subr_pcpu.c
(10.18 KB)
📄
subr_pctrie.c
(20.99 KB)
📄
subr_physmem.c
(11.52 KB)
📄
subr_pidctrl.c
(5.43 KB)
📄
subr_power.c
(3.13 KB)
📄
subr_prf.c
(27.42 KB)
📄
subr_prng.c
(3.36 KB)
📄
subr_prof.c
(15.43 KB)
📄
subr_rangeset.c
(8.5 KB)
📄
subr_rman.c
(27.61 KB)
📄
subr_rtc.c
(11.42 KB)
📄
subr_sbuf.c
(20.53 KB)
📄
subr_scanf.c
(15.59 KB)
📄
subr_sfbuf.c
(6.17 KB)
📄
subr_sglist.c
(22.83 KB)
📄
subr_sleepqueue.c
(39.43 KB)
📄
subr_smp.c
(31.62 KB)
📄
subr_smr.c
(20.17 KB)
📄
subr_stack.c
(6.47 KB)
📄
subr_stats.c
(103.01 KB)
📄
subr_syscall.c
(7.98 KB)
📄
subr_taskqueue.c
(21.1 KB)
📄
subr_terminal.c
(15.52 KB)
📄
subr_trap.c
(10.87 KB)
📄
subr_turnstile.c
(35.58 KB)
📄
subr_uio.c
(11.38 KB)
📄
subr_unit.c
(22.97 KB)
📄
subr_vmem.c
(43.25 KB)
📄
subr_witness.c
(84.59 KB)
📄
sys_capability.c
(15.06 KB)
📄
sys_eventfd.c
(8.42 KB)
📄
sys_generic.c
(44.22 KB)
📄
sys_getrandom.c
(4.21 KB)
📄
sys_pipe.c
(45.14 KB)
📄
sys_procdesc.c
(14.57 KB)
📄
sys_process.c
(30.73 KB)
📄
sys_socket.c
(20.11 KB)
📄
syscalls.c
(22.73 KB)
📄
syscalls.master
(60.26 KB)
📄
systrace_args.c
(178.49 KB)
📄
sysv_ipc.c
(6.53 KB)
📄
sysv_msg.c
(48.65 KB)
📄
sysv_sem.c
(49.85 KB)
📄
sysv_shm.c
(43.93 KB)
📄
tty.c
(55.14 KB)
📄
tty_compat.c
(11.46 KB)
📄
tty_info.c
(9.93 KB)
📄
tty_inq.c
(12.22 KB)
📄
tty_outq.c
(8.74 KB)
📄
tty_pts.c
(19.74 KB)
📄
tty_tty.c
(2.83 KB)
📄
tty_ttydisc.c
(28.6 KB)
📄
uipc_accf.c
(8.07 KB)
📄
uipc_debug.c
(12.42 KB)
📄
uipc_domain.c
(13.13 KB)
📄
uipc_ktls.c
(55.7 KB)
📄
uipc_mbuf.c
(52.45 KB)
📄
uipc_mbuf2.c
(12.64 KB)
📄
uipc_mbufhash.c
(4.9 KB)
📄
uipc_mqueue.c
(64.64 KB)
📄
uipc_sem.c
(25.18 KB)
📄
uipc_shm.c
(50.47 KB)
📄
uipc_sockbuf.c
(42.9 KB)
📄
uipc_socket.c
(110.61 KB)
📄
uipc_syscalls.c
(35.94 KB)
📄
uipc_usrreq.c
(75.11 KB)
📄
vfs_acl.c
(14.5 KB)
📄
vfs_aio.c
(76.32 KB)
📄
vfs_bio.c
(145.39 KB)
📄
vfs_cache.c
(143.09 KB)
📄
vfs_cluster.c
(28.36 KB)
📄
vfs_default.c
(33.16 KB)
📄
vfs_export.c
(14.55 KB)
📄
vfs_extattr.c
(17.91 KB)
📄
vfs_hash.c
(6 KB)
📄
vfs_init.c
(15.86 KB)
📄
vfs_lookup.c
(45.48 KB)
📄
vfs_mount.c
(62.58 KB)
📄
vfs_mountroot.c
(26.23 KB)
📄
vfs_subr.c
(167.52 KB)
📄
vfs_syscalls.c
(106.86 KB)
📄
vfs_vnops.c
(86.28 KB)
📄
vnode_if.src
(13.66 KB)
Editing: device_if.m
#- # Copyright (c) 1998-2004 Doug Rabson # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $FreeBSD$ # #include <sys/bus.h> /** * @defgroup DEVICE device - KObj methods for all device drivers * @brief A basic set of methods required for all device drivers. * * The device interface is used to match devices to drivers during * autoconfiguration and provides methods to allow drivers to handle * system-wide events such as suspend, resume or shutdown. * @{ */ INTERFACE device; # Needed for timestamping device probe/attach calls HEADER { #include <sys/tslog.h> } # # Default implementations of some methods. # CODE { static int null_shutdown(device_t dev) { return 0; } static int null_suspend(device_t dev) { return 0; } static int null_resume(device_t dev) { return 0; } static int null_quiesce(device_t dev) { return 0; } static void * null_register(device_t dev) { return NULL; } }; /** * @brief Probe to see if a device matches a driver. * * Users should not call this method directly. Normally, this * is called via device_probe_and_attach() to select a driver * calling the DEVICE_PROBE() of all candidate drivers and attach * the winning driver (if any) to the device. * * This function is used to match devices to device drivers. * Typically, the driver will examine the device to see if * it is suitable for this driver. This might include checking * the values of various device instance variables or reading * hardware registers. * * In some cases, there may be more than one driver available * which can be used for a device (for instance there might * be a generic driver which works for a set of many types of * device and a more specific driver which works for a subset * of devices). Because of this, a driver should not assume * that it will be the driver that attaches to the device even * if it returns a success status from DEVICE_PROBE(). In particular, * a driver must free any resources which it allocated during * the probe before returning. The return value of DEVICE_PROBE() * is used to elect which driver is used - the driver which returns * the largest non-error value wins the election and attaches to * the device. Common non-error values are described in the * DEVICE_PROBE(9) manual page. * * If a driver matches the hardware, it should set the device * description string using device_set_desc() or * device_set_desc_copy(). This string is used to generate an * informative message when DEVICE_ATTACH() is called. * * As a special case, if a driver returns zero, the driver election * is cut short and that driver will attach to the device * immediately. This should rarely be used. * * For example, a probe method for a PCI device driver might look * like this: * * @code * int * foo_probe(device_t dev) * { * if (pci_get_vendor(dev) == FOOVENDOR && * pci_get_device(dev) == FOODEVICE) { * device_set_desc(dev, "Foo device"); * return (BUS_PROBE_DEFAULT); * } * return (ENXIO); * } * @endcode * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_probe, foo_probe) * @endcode * * @param dev the device to probe * * @retval 0 if this is the only possible driver for this * device * @retval negative if the driver can match this device - the * least negative value is used to select the * driver * @retval ENXIO if the driver does not match the device * @retval positive if some kind of error was detected during * the probe, a regular unix error code should * be returned to indicate the type of error * @see DEVICE_ATTACH(), pci_get_vendor(), pci_get_device() */ PROLOG { TSENTER2(device_get_name(dev)); } EPILOG { TSEXIT2(device_get_name(dev)); } METHOD int probe { device_t dev; }; /** * @brief Allow a device driver to detect devices not otherwise enumerated. * * The DEVICE_IDENTIFY() method is used by some drivers (e.g. the ISA * bus driver) to help populate the bus device with a useful set of * child devices, normally by calling the BUS_ADD_CHILD() method of * the parent device. For instance, the ISA bus driver uses several * special drivers, including the isahint driver and the pnp driver to * create child devices based on configuration hints and PnP bus * probes respectively. * * Many bus drivers which support true plug-and-play do not need to * use this method at all since child devices can be discovered * automatically without help from child drivers. * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_identify, foo_identify) * @endcode * * @param driver the driver whose identify method is being called * @param parent the parent device to use when adding new children */ STATICMETHOD void identify { driver_t *driver; device_t parent; }; /** * @brief Attach a device to a device driver * * Normally only called via device_probe_and_attach(), this is called * when a driver has succeeded in probing against a device. * This method should initialise the hardware and allocate other * system resources (e.g. devfs entries) as required. * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_attach, foo_attach) * @endcode * * @param dev the device to probe * * @retval 0 success * @retval non-zero if some kind of error was detected during * the attach, a regular unix error code should * be returned to indicate the type of error * @see DEVICE_PROBE() */ PROLOG { TSENTER2(device_get_name(dev)); } EPILOG { TSEXIT2(device_get_name(dev)); } METHOD int attach { device_t dev; }; /** * @brief Detach a driver from a device. * * This can be called if the user is replacing the * driver software or if a device is about to be physically removed * from the system (e.g. for removable hardware such as USB or PCCARD). * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_detach, foo_detach) * @endcode * * @param dev the device to detach * * @retval 0 success * @retval non-zero the detach could not be performed, e.g. if the * driver does not support detaching. * * @see DEVICE_ATTACH() */ METHOD int detach { device_t dev; }; /** * @brief Called during system shutdown. * * This method allows drivers to detect when the system is being shut down. * Some drivers need to use this to place their hardware in a consistent * state before rebooting the computer. * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_shutdown, foo_shutdown) * @endcode */ METHOD int shutdown { device_t dev; } DEFAULT null_shutdown; /** * @brief This is called by the power-management subsystem when a * suspend has been requested by the user or by some automatic * mechanism. * * This gives drivers a chance to veto the suspend or save their * configuration before power is removed. * * To include this method in a device driver, use a line like this in * the driver's method list: * * @code * KOBJMETHOD(device_suspend, foo_suspend) * @endcode * * @param dev the device being suspended * * @retval 0 success * @retval non-zero an error occurred while attempting to prepare the * device for suspension * * @see DEVICE_RESUME() */ METHOD int suspend { device_t dev; } DEFAULT null_suspend; /** * @brief This is called when the system resumes after a suspend. * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_resume, foo_resume) * @endcode * * @param dev the device being resumed * * @retval 0 success * @retval non-zero an error occurred while attempting to restore the * device from suspension * * @see DEVICE_SUSPEND() */ METHOD int resume { device_t dev; } DEFAULT null_resume; /** * @brief This is called when the driver is asked to quiesce itself. * * The driver should arrange for the orderly shutdown of this device. * All further access to the device should be curtailed. Soon there * will be a request to detach, but there won't necessarily be one. * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_quiesce, foo_quiesce) * @endcode * * @param dev the device being quiesced * * @retval 0 success * @retval non-zero an error occurred while attempting to quiesce the * device * * @see DEVICE_DETACH() */ METHOD int quiesce { device_t dev; } DEFAULT null_quiesce; /** * @brief This is called when the driver is asked to register handlers. * * * To include this method in a device driver, use a line like this * in the driver's method list: * * @code * KOBJMETHOD(device_register, foo_register) * @endcode * * @param dev the device for which handlers are being registered * * @retval NULL method not implemented * @retval non-NULL a pointer to implementation specific static driver state * */ METHOD void * register { device_t dev; } DEFAULT null_register;
Upload File
Create Folder