| /linux-4.1.27/sound/aoa/fabrics/ |
| D | layout.c | 638 if (gpio->methods && gpio->methods->get_##n) \
640 gpio->methods->get_##n(gpio); \
647 if (gpio->methods && gpio->methods->set_##n) \
648 gpio->methods->set_##n(gpio, \
730 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
734 v = ldev->gpio.methods->get_detect(&ldev->gpio, in detected_get()
854 v = ldev->gpio.methods->get_detect(&ldev->gpio, AOA_NOTIFY_HEADPHONE); in layout_notify()
858 ldev->gpio.methods->set_speakers(&ldev->gpio, !v); in layout_notify()
859 ldev->gpio.methods->set_headphone(&ldev->gpio, v); in layout_notify()
860 ldev->gpio.methods->set_lineout(&ldev->gpio, 0); in layout_notify()
[all …]
|
| /linux-4.1.27/drivers/i2c/busses/ |
| D | i2c-scmi.c | 35 struct smbus_methods_t *methods; member
162 method = smbus_cmi->methods->mt_sbr; in acpi_smbus_cmi_access()
166 method = smbus_cmi->methods->mt_sbw; in acpi_smbus_cmi_access()
302 if (!strcmp(name, smbus_cmi->methods->mt_info)) { in acpi_smbus_cmi_add_cap()
304 smbus_cmi->methods->mt_info, in acpi_smbus_cmi_add_cap()
308 smbus_cmi->methods->mt_info, status)); in acpi_smbus_cmi_add_cap()
331 } else if (!strcmp(name, smbus_cmi->methods->mt_sbr)) in acpi_smbus_cmi_add_cap()
333 else if (!strcmp(name, smbus_cmi->methods->mt_sbw)) in acpi_smbus_cmi_add_cap()
377 smbus_cmi->methods = in acpi_smbus_cmi_add()
|
| D | Kconfig | 287 BIOS to declare ACPI control methods as described in the SMBus Control
|
| /linux-4.1.27/sound/aoa/core/ |
| D | gpio-feature.c | 179 static struct gpio_methods methods; variable
190 if (methods.set_master) in ftr_gpio_all_amps_off()
204 if (methods.set_master) in ftr_gpio_all_amps_restore()
247 methods.set_master = ftr_gpio_set_master; in ftr_gpio_init()
248 methods.get_master = ftr_gpio_get_master; in ftr_gpio_init()
406 static struct gpio_methods methods = { variable
422 struct gpio_methods *ftr_gpio_methods = &methods;
|
| D | gpio-pmf.c | 236 static struct gpio_methods methods = { variable
252 struct gpio_methods *pmf_gpio_methods = &methods;
|
| /linux-4.1.27/Documentation/laptops/ |
| D | sony-laptop.txt | 76 More recent Vaio models expose a consistent set of ACPI methods to
93 In your kernel logs you will find the list of all ACPI methods
100 (3) SN06 and SN07 are used to call into the real methods based on
106 * For old models you can see the GCDP/GCDP methods used to pwer on/off
112 The sony-laptop driver creates, for some of those methods (the most
115 You can create other entries corresponding to your own laptop methods by
|
| D | toshiba_haps.txt | 34 This device comes with 3 methods:
|
| D | thinkpad-acpi.txt | 654 features of this driver, as it uses the same ACPI methods as
844 expose the CPU temperature through the standard ACPI methods. This
952 display backlight brightness control methods have 16 levels, ranging
|
| /linux-4.1.27/Documentation/infiniband/ |
| D | core_locking.txt | 11 all of the methods in struct ib_device may sleep. The exceptions
12 are any methods from the list:
51 All of the methods in struct ib_device exported by a low-level
114 A consumer is permitted to sleep in its add and remove methods.
|
| /linux-4.1.27/sound/aoa/codecs/ |
| D | onyx.c | 779 onyx->codec.gpio->methods->all_amps_off(onyx->codec.gpio); in onyx_switch_clock()
782 onyx->codec.gpio->methods->all_amps_restore(onyx->codec.gpio); in onyx_switch_clock()
821 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
823 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_resume()
825 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_resume()
869 if (!onyx->codec.gpio || !onyx->codec.gpio->methods) { in onyx_init_codec()
874 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
876 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 1); in onyx_init_codec()
878 onyx->codec.gpio->methods->set_hw_reset(onyx->codec.gpio, 0); in onyx_init_codec()
|
| D | tas.c | 676 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_reset_init()
678 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
680 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 1); in tas_reset_init()
682 tas->codec.gpio->methods->set_hw_reset(tas->codec.gpio, 0); in tas_reset_init()
684 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_reset_init()
722 tas->codec.gpio->methods->all_amps_off(tas->codec.gpio); in tas_switch_clock()
732 tas->codec.gpio->methods->all_amps_restore(tas->codec.gpio); in tas_switch_clock()
802 if (!tas->codec.gpio || !tas->codec.gpio->methods) { in tas_init_codec()
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | soc-camera.txt | 59 All camera host methods are passed in a struct soc_camera_host_ops:
74 .add and .remove methods are called when a sensor is attached to or detached
82 details about format conversion. The rest of the methods are called from
90 and optionally provide platform .power and .reset methods for the camera. This
99 board-specific power switching methods. soc_camera_apply_board_flags() takes
161 .get_formats and, if required, a .put_formats methods.
|
| D | v4l2-framework.txt | 228 v4l2_subdev pointer, for other busses you may have to use other methods.
912 The v4l2 core API provides a set of standard methods (called "videobuf")
913 for dealing with video buffers. Those methods allow a driver to implement
915 methods for using video buffers on devices that supports DMA with
1153 methods.
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | jack.txt | 33 machine driver and updated by jack detection methods.
48 Jack detection methods
58 provided by the snd_soc_jack_add_gpio() function. Other methods are
|
| /linux-4.1.27/drivers/rapidio/ |
| D | Kconfig | 57 or any number of methods to be built as modules.
58 Selecting a built-in method disables use of loadable methods.
|
| /linux-4.1.27/Documentation/power/ |
| D | basic-pm-debugging.txt | 54 global control methods(*)
58 global control methods(*) and the disabling of nonboot CPUs
62 control methods(*), the disabling of nonboot CPUs and suspending of
65 (*) the platform global control methods are only available on ACPI systems
82 invoke the global control methods (eg. ACPI global control methods) used to
85 methods used to cancel hibernation etc.
|
| D | devices.txt | 31 by implementing various role-specific suspend and resume methods to
57 various role-specific suspend and resume methods, so that the hardware
117 This structure is defined in include/linux/pm.h and the methods included in it
119 For now, it should be sufficient to remember that the last three methods are
126 power management methods. Therefore it is not described in this document, so
132 The core methods to suspend and resume devices reside in struct dev_pm_ops
138 classes and bus types) don't provide all power management methods.
140 Bus drivers implement these methods as appropriate for the hardware and the
280 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
304 driver-specific methods stored in dev->driver->pm, but they don't have to do
[all …]
|
| D | pci.txt | 44 approach requires the platform firmware to provide special methods that may be
58 In turn, if the methods provided by the platform firmware are used for changing
144 methods" that may be executed by the kernel to perform specific tasks, such as
145 putting a device into a low-power state. These control methods are encoded
153 ACPI control methods may be divided into global control methods, that are not
154 associated with any particular devices, and device control methods, that have
156 the platform. This means, in particular, that ACPI device control methods can
158 ACPI methods used for device power management fall into that category.
166 with the help of their own control methods, _ON and _OFF, that have to be
171 by the device in this state using their _ON control methods and (2) execute the
[all …]
|
| D | video.txt | 21 methods work on different systems, and no known method suits all of
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
| D | sysfs-devices-power_state | 7 management methods.
|
| D | sysfs-devices-real_power_state | 7 power management methods and use ACPI power resources for power
|
| D | sysfs-class-extcon | 57 Inputs of all the methods are required to meet the
|
| D | sysfs-power | 42 sleep on the next suspend. There are four methods supported:
|
| /linux-4.1.27/Documentation/timers/ |
| D | 00-INDEX | 14 - Summary of the different methods for the scheduler clock-interrupts management.
|
| D | NO_HZ.txt | 197 offload may be selected via several methods:
|
| /linux-4.1.27/sound/aoa/ |
| D | aoa-gpio.h | 75 struct gpio_methods *methods; member
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | sysfs.txt | 54 the filesystem. Sysfs forwards file I/O operations to methods defined
125 show and store methods of the attribute owners.
139 calls the associated methods.
168 To read or write attributes, show() or store() methods must be
212 - show() methods should return the number of bytes printed into the
223 - The object passed to the methods will be pinned in memory via sysfs
|
| D | vfs.txt | 235 All methods are called without any locks being held, unless otherwise
236 noted. This means that most methods can block safely. All methods are
323 is a pointer to a "struct inode_operations" which describes the methods that
370 Again, all methods are called without any locks being held, unless
388 If you wish to overload the dentry methods then you should
784 ->swap_{out,in} methods.
832 Again, all methods are called without any locks being held, unless
919 here. These methods may be set to NULL, as they are either optional or
|
| D | porting | 16 New methods: ->alloc_inode() and ->destroy_inode().
278 moved from generic methods (block_write_begin, cont_write_begin,
|
| D | ext2.txt | 287 scheme but less reliable. Both methods are equally resolvable by their
|
| D | Locking | 1 The text below describes the locking rules for VFS-related methods.
|
| D | xfs-delayed-logging-design.txt | 781 logging methods are in the middle of the life cycle - they still have the same
791 be able to swap methods automatically and transparently depending on load
|
| /linux-4.1.27/Documentation/ |
| D | video-output.txt | 7 can be used to hook platform specific methods to enable/disable video output
|
| D | rfkill.txt | 41 transmitter with the kernel, methods for turning it on and off and, letting
|
| D | dell_rbu.txt | 20 image methods. In case of monolithic the driver allocates a contiguous chunk
|
| D | assoc_array.txt | 137 This points to a number of methods, all of which need to be provided:
211 passed to the methods in the ops table when they are called.
230 passed to the methods in the ops table when they are called.
|
| D | vme_api.txt | 210 to be used, other methods can be used to allocate a buffer, though care must be
223 Slave windows map local memory onto the VME bus, the standard methods for
|
| D | SubmittingDrivers | 92 necessary, the .suspend and .resume methods used during the
|
| D | kmemleak.txt | 200 the pointer is calculated by other methods than the usual container_of
|
| D | cpu-hotplug.txt | 37 a laptop run SMP kernels which didn't support these methods. SMP support
|
| D | cachetlb.txt | 28 invoke one of the following flush methods _after_ the page table
|
| D | kobject.txt | 238 ktypes and release methods
|
| D | kernel-parameters.txt | 249 Disable auto-serialization of AML methods
250 AML control methods that contain the opcodes to create
2656 hardware access methods are allowed. Use this
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 34 Also, codes returned by adapter probe methods follow rules which are
73 Returned by driver probe() methods. This is a bit more
90 Returned by driver probe() methods to indicate that they
|
| D | upgrading-clients | 10 the old to the new new binding methods.
95 .detach_client methods can be removed, along with the addr_data,
115 Add the probe and remove methods to the i2c_driver, as so:
|
| D | instantiating-devices | 193 only way back then. Where possible, methods 1 and 2 should be preferred.
203 instantiation (methods 1 and 2) is much preferred for it is safer and
|
| /linux-4.1.27/Documentation/acpi/ |
| D | method-customizing.txt | 7 Linux supports customizing ACPI control methods at runtime.
68 ACPI methods, we need to redo step c) ~ g) for multiple times.
|
| D | namespace.txt | 37 control methods, encoded in AML (ACPI Machine Language). The data block
245 with specific control methods (as indicated by the ACPI defined
287 control methods. One ACPI device object may be linked this way to
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 310 can be controlled through the optional ACPI methods _PS0, _PS1, _PS2, and _PS3;
320 methods. They are then tied back to D-states for a particular device
325 The kernel ACPI code will also assume that the _PSx methods follow the normal
326 ACPI rules for such methods:
340 Such code in _PSx methods will of course be very platform specific. But,
359 methods to be expected). The only exceptions to this are CPU clocks where
360 CPPC provides a much richer interface than ACPI methods. If the clocks
364 they could do so by providing ACPI methods that could be invoked by Linux
366 such methods, even if they are provided. Such methods are not currently
|
| D | acpi_object_usage.txt | 439 usage, change them in these methods.
521 In Section 15 of the ACPI specification, several methods are mentioned as
|
| D | booting.txt | 189 enable-methods are described below.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | shtc1 | 27 address 0x70. See Documentation/i2c/instantiating-devices for methods to
|
| D | ltc4245 | 98 The LTC4245 chip can be configured to sample all GPIO pins with two methods:
|
| D | f71882fg | 88 Both PWM (pulse-width modulation) and DC fan speed control methods are
|
| D | w83791d | 101 Since both methods read and write the underlying hardware, they can be used
|
| D | f71805f | 129 Both PWM (pulse-width modulation) and DC fan speed control methods are
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | TODO | 24 method would be to use accurate table methods for these routines. I have
27 These methods are used in GLIBC for some of the transcendental functions.
|
| /linux-4.1.27/Documentation/locking/ |
| D | ww-mutex-design.txt | 94 definitions for methods #1 and #2:
197 Unlocking works the same way for both methods #1 and #2:
221 Note that this approach differs in two important ways from the above methods:
229 Note also that methods #1 and #2 and method #3 can be combined, e.g. to first lock a
231 methods. And then lock any additional objects affected by the operations using
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.concap | 125 protocol may not call any *dops methods after this. */
136 dummy methods here */
160 /* Control methods must be set to NULL by devices which do not
182 be accessed via *pops methods only*/
|
| D | README.sc | 73 versus between 16K and 64K. New methods for using the shared RAM
|
| /linux-4.1.27/Documentation/rapidio/ |
| D | rapidio.txt | 114 discovery methods as statically linked components or loadable modules.
120 several methods to initiate an enumeration and/or discovery process:
158 destination ID can be assigned to a master port using various methods depending
170 traditional methods of passing module parameter "hdid=" during its loading:
190 This requirement is cased by the fact that enumeration/discovery methods invoke
303 methods as new configuration options without significant impact to the core
|
| /linux-4.1.27/Documentation/crypto/ |
| D | async-tx-api.txt | 26 The async_tx API provides methods for describing a chain of asynchronous
84 following methods:
101 There are two methods for an application to learn about the completion
|
| D | api-intro.txt | 82 methods may only be called from softirq and user contexts. For
|
| /linux-4.1.27/Documentation/x86/ |
| D | early-microcode.txt | 28 In addition to these two legacy methods, the early loading method described
|
| /linux-4.1.27/drivers/platform/chrome/ |
| D | Kconfig | 57 typically has its own communication methods.
|
| /linux-4.1.27/Documentation/gpio/ |
| D | driver.txt | 44 - methods to establish GPIO direction
45 - methods used to access GPIO values
47 - flag saying whether calls to its methods may sleep
|
| D | gpio-legacy.txt | 531 - methods to establish GPIO direction
532 - methods used to access GPIO values
533 - flag saying whether calls to its methods may sleep
|
| /linux-4.1.27/Documentation/networking/ |
| D | dmfe.txt | 51 Implement pci_driver::suspend() and pci_driver::resume() power management methods.
|
| D | README.ipw2200 | 187 private, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux
190 The general form of using the private wireless methods is:
198 The supported private methods are:
|
| D | dm9000.txt | 132 about link (carrier) availability. This is managed by several methods
|
| D | ipvs-sysctl.txt | 23 in backup mode to avoid packet loops for DR/TUN methods.
|
| D | PLIP.txt | 112 PLIP uses several different data transfer methods. The first (and the
|
| D | 6pack.txt | 25 DAMA channel access methods.
|
| D | bonding.txt | 1763 There are two methods to insure that the VLAN device operates
1850 the same information. If both methods fail (i.e., the driver either
|
| /linux-4.1.27/drivers/iio/ |
| D | Kconfig | 19 acquisition methods.
|
| /linux-4.1.27/Documentation/usb/ |
| D | anchors.txt | 9 keeping track of URBs and provides methods to deal with
|
| D | power-management.txt | 297 methods in its usb_driver structure, and the reset_resume method is
298 optional. The methods' jobs are quite simple:
334 methods get called when the interfaces are suspended or resumed. In
348 three of the methods listed above. In addition, a driver indicates
|
| /linux-4.1.27/security/keys/ |
| D | Kconfig | 12 It also includes provision of methods by which such keys might be
|
| /linux-4.1.27/Documentation/serial/ |
| D | tty.txt | 115 Line discipline methods can call the following methods of the underlying
184 Line discipline methods have access to tty->flags field containing the
|
| D | driver | 18 information (defined by uart_port) and a set of control methods (defined
71 hardware specific driver. It contains all the methods to control the
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 137 of the available parity distribution methods.
145 in one of the available parity distribution methods.
360 of the available parity distribution methods.
368 in one of the available parity distribution methods.
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | porting.txt | 288 bus driver should define single instances of the generic methods that
306 The generic driver should be initialized with these methods before it
323 methods.
|
| D | platform.txt | 37 provide probe() and remove() methods. They support power management
|
| /linux-4.1.27/Documentation/ptp/ |
| D | ptp.txt | 64 Drivers must ensure that all of the methods in interface are
|
| /linux-4.1.27/Documentation/fmc/ |
| D | carrier.txt | 129 The carrier provides a number of methods by means of the
149 The individual methods perform the following tasks:
213 methods: for example the SPEC driver may define that its carrier
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-iov-howto.txt | 30 Multiple methods are available for SR-IOV enablement.
|
| /linux-4.1.27/drivers/thermal/ |
| D | Kconfig | 250 notification methods.
261 notification methods.The other trip is a critical trip point, which
|
| /linux-4.1.27/Documentation/security/ |
| D | IMA-templates.txt | 81 currently the following methods are supported:
|
| D | keys.txt | 1320 instantiate and update methods.
|
| /linux-4.1.27/Documentation/extcon/ |
| D | porting-android-switch-class | 85 methods to register notifier_block for cable events:
|
| /linux-4.1.27/arch/mips/ |
| D | Kconfig.debug | 110 can try to select SYS_SUPPORTS_ZBOOT and use the other methods to
|
| /linux-4.1.27/Documentation/trace/ |
| D | tracepoint-analysis.txt | 15 what is going on within the system. There are a large number of methods for
17 this document describes some of the methods that can be used.
|
| /linux-4.1.27/Documentation/w1/ |
| D | w1.generic | 59 You can call above methods by reading appropriate sysfs files.
|
| /linux-4.1.27/Documentation/spi/ |
| D | spi-summary | 479 bus number (maybe the same as the platform device ID) and three methods
482 and those methods.)
577 SPI subsystem, just implement the queued methods specified above. Using
579 providing pure process-context execution of methods. The message queue
|
| /linux-4.1.27/Documentation/power/powercap/ |
| D | powercap.txt | 12 'control types', which correspond to different methods of power capping. For
|
| /linux-4.1.27/drivers/acpi/ |
| D | Kconfig | 351 tristate "Allow ACPI methods to be inserted/replaced at run time"
355 This debug facility allows ACPI AML methods to be inserted and/or
|
| /linux-4.1.27/Documentation/arm/ |
| D | Interrupts | 122 Set the mask/unmask methods for handling this IRQ
|
| D | IXP4xx | 76 IXP4xx provides two methods of accessing PCI memory space:
|
| D | cluster-pm-race-avoidance.txt | 36 methods of coordination are required in order to guarantee safe
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | backend-api.txt | 77 The cache methods are executed one of two contexts:
288 These methods are used to exclusively lock an object. It must be possible
297 These methods are used to pin an object into the cache. Once pinned an
|
| D | netfs-api.txt | 894 The netfs can use this information in methods such as releasepage() to
|
| /linux-4.1.27/Documentation/scsi/ |
| D | osd.txt | 79 b. Any of the osd_req_* methods is used to encode a request of the specified
|
| D | st.txt | 12 one of the following three methods:
338 SCSI mode page 15. Note that some drives other methods for
|
| D | scsi_fc_transport.txt | 54 expected. Once instantiated by one of the above methods, it will have a
|
| /linux-4.1.27/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 203 IXP4xx provides two methods of accessing PCI memory space:
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | pcc-cpufreq.txt | 116 * supports the PCC interface, and the associated PCCH() and PCCP() methods
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | paride.txt | 11 host computer. While some devices (notably scanners) use ad-hoc methods
54 paride module which provides a registry and some common methods for
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 483 various methods, which are callbacks from the cgroup system, along
533 Each subsystem may export the following methods. The only mandatory
534 methods are css_alloc/free. Any others that are null are presumed to
|
| /linux-4.1.27/Documentation/s390/ |
| D | monreader.txt | 119 There are two alternative methods for reading: either non-blocking read in
|
| D | cds.txt | 29 functional layer was introduced that provides generic I/O access methods to
142 This methods implies that Linux/390 doesn't require to probe for free (not
|
| /linux-4.1.27/Documentation/dvb/ |
| D | README.dvb-usb | 22 - other functions/methods which can be shared by several drivers (such as
|
| /linux-4.1.27/drivers/iio/adc/ |
| D | Kconfig | 310 driver supports both RT and SW conversion methods.
|
| /linux-4.1.27/Documentation/fb/ |
| D | fbcon.txt | 195 restored properly. The following is one of the several methods that you can do:
|
| /linux-4.1.27/arch/ia64/ |
| D | Kconfig | 533 region 0xA1. AML methods can use this OpRegion to call arbitrary
|
| /linux-4.1.27/Documentation/input/ |
| D | event-codes.txt | 267 compatibility, both methods need to be checked in userspace.
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.lex.c_shipped | 852 /* Accessor methods to globals.
2123 /* Accessor methods (get/set functions) to struct members. */
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 1.Intro | 94 proprietary development methods.
|
| /linux-4.1.27/scripts/genksyms/ |
| D | lex.lex.c_shipped | 592 /* Accessor methods to globals.
1728 /* Accessor methods (get/set functions) to struct members. */
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | HD-Audio.txt | 14 methods for the HD-audio hardware.
61 `position_fix=3` means to use a combination of both methods, needed
|
| D | ALSA-Configuration.txt | 258 ATI IXP has two different methods to control SPDIF output. One is
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-lexer.lex.c_shipped | 685 /* Accessor methods to globals.
1991 /* Accessor methods (get/set functions) to struct members. */
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | modules.txt | 539 kbuild for building and can therefore use the same methods as
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 107 There are two possible methods of using Kdump.
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 362 ct_item_ops->drop_link() methods. If the ->allow_link() method exists,
|
| /linux-4.1.27/drivers/platform/x86/ |
| D | Kconfig | 573 defined methods and data blocks in a PNP0C14 device, which are then
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 325 no shortage of straightforward methods for accomplishing this.
1140 Proposes comparing RCU to lock-free methods for the Linux kernel.
|
| /linux-4.1.27/drivers/tty/serial/ |
| D | Kconfig | 180 communication methods, for things like PPP you still must fully
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1723 Implement faster copy_to_user and clear_user methods for CPU
|