19f14302dSWarner Losh.\" -*- nroff -*- 29f14302dSWarner Losh.\" 3*a339dcccSWarner Losh.\" Copyright (c) 2006 M. Warner Losh <imp@FreeBSD.org> 49f14302dSWarner Losh.\" 59f14302dSWarner Losh.\" Redistribution and use in source and binary forms, with or without 69f14302dSWarner Losh.\" modification, are permitted provided that the following conditions 79f14302dSWarner Losh.\" are met: 89f14302dSWarner Losh.\" 1. Redistributions of source code must retain the above copyright 99f14302dSWarner Losh.\" notice, this list of conditions and the following disclaimer. 109f14302dSWarner Losh.\" 2. Redistributions in binary form must reproduce the above copyright 119f14302dSWarner Losh.\" notice, this list of conditions and the following disclaimer in the 129f14302dSWarner Losh.\" documentation and/or other materials provided with the distribution. 139f14302dSWarner Losh.\" 149f14302dSWarner Losh.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR 159f14302dSWarner Losh.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 169f14302dSWarner Losh.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 179f14302dSWarner Losh.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, 189f14302dSWarner Losh.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 199f14302dSWarner Losh.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 209f14302dSWarner Losh.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 219f14302dSWarner Losh.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 229f14302dSWarner Losh.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 239f14302dSWarner Losh.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 249f14302dSWarner Losh.\" 25dabc7ac2SBjoern A. Zeeb.Dd June 18, 2011 269f14302dSWarner Losh.Dt DEVICE_GET_SYSCTL 9 279f14302dSWarner Losh.Os 289f14302dSWarner Losh.Sh NAME 299f14302dSWarner Losh.Nm device_get_sysctl_ctx , 309f14302dSWarner Losh.Nm device_get_sysctl_tree 31bd84dd2fSRuslan Ermilov.Nd manipulate the sysctl oid tree for driver specific sysctl nodes 329f14302dSWarner Losh.Sh SYNOPSIS 339f14302dSWarner Losh.In sys/param.h 349f14302dSWarner Losh.In sys/bus.h 35bd84dd2fSRuslan Ermilov.Ft "struct sysctl_ctx_list *" 369f14302dSWarner Losh.Fn device_get_sysctl_ctx "device_t dev" 37bd84dd2fSRuslan Ermilov.Ft "struct sysctl_oid *" 389f14302dSWarner Losh.Fn device_get_sysctl_tree "device_t dev" 399f14302dSWarner Losh.Sh DESCRIPTION 409f14302dSWarner LoshThe newbus system automatically adds a sysctl node for each device 419f14302dSWarner Loshin the system. 429f14302dSWarner LoshThis node can be accessed with the 439f14302dSWarner Losh.Fn device_get_sysctl_tree 449f14302dSWarner Loshfunction. 459f14302dSWarner LoshThe context for the node can be obtained with the 46dabc7ac2SBjoern A. Zeeb.Fn device_get_sysctl_ctx 479f14302dSWarner Loshfunction. 489f14302dSWarner Losh.Sh SEE ALSO 499f14302dSWarner Losh.Xr device 9 509f14302dSWarner Losh.Sh AUTHORS 519f14302dSWarner LoshThis manual page was written by 529f14302dSWarner Losh.An Warner Losh . 53