Home
last modified time | relevance | path

Searched refs:components (Results 1 – 167 of 167) sorted by relevance

/linux-4.4.14/lib/
Dbuild_OID_registry57 my @components = split(/[.]/, $oid);
60 my $size = $#components;
61 for (my $loop = 2; $loop <= $#components; $loop++) {
62 my $c = $components[$loop];
97 my @components = split(/[.]/, $oids[$i]);
99 push @octets, $components[0] * 40 + $components[1];
101 for (my $loop = 2; $loop <= $#components; $loop++) {
102 my $c = $components[$loop];
/linux-4.4.14/drivers/misc/
Denclosure.c124 enclosure_register(struct device *dev, const char *name, int components, in enclosure_register() argument
129 sizeof(struct enclosure_component)*components, in enclosure_register()
138 edev->components = components; in enclosure_register()
148 for (i = 0; i < components; i++) { in enclosure_register()
182 for (i = 0; i < edev->components; i++) in enclosure_unregister()
265 for (i = 0; i < edev->components; i++) { in enclosure_component_find_by_name()
302 if (number >= edev->components) in enclosure_component_alloc()
379 if (!edev || component >= edev->components) in enclosure_add_device()
412 for (i = 0; i < edev->components; i++) { in enclosure_remove_device()
435 return snprintf(buf, 40, "%d\n", edev->components); in components_show()
[all …]
/linux-4.4.14/drivers/base/
Dcomponent.c32 struct list_head components; member
71 list_add_tail(&c->master_node, &master->components); in component_attach_master()
140 while (!list_empty(&master->components)) { in master_remove_components()
141 struct component *c = list_first_entry(&master->components, in master_remove_components()
310 INIT_LIST_HEAD(&master->components); in component_master_add_with_match()
376 list_for_each_entry_reverse(c, &master->components, master_node) in component_unbind_all()
445 list_for_each_entry(c, &master->components, master_node) { in component_bind_all()
452 list_for_each_entry_continue_reverse(c, &master->components, in component_bind_all()
DKconfig256 hardware components that do not support I/O map nor scatter-gather.
/linux-4.4.14/Documentation/sound/alsa/soc/
Dpops_clicks.txt5 of components within the audio subsystem. This is noticeable on PCs when an
10 because the components within the subsystem are being dynamically powered
21 components in a specific order. This order is different for startup and
37 playback in that components are powered in a sequence depending upon stream
Ddapm.txt44 internal codec components). All audio components that effect power are called
66 o Regulator - External regulator that supplies power to audio components.
67 o Clock - External clock that supplies clock to audio components.
Dcodec.txt132 components and their relationships and registers to the ASoC core.
DDPCM.txt164 components (as some DSPs have strong requirements for the ordering DAI/DSP
/linux-4.4.14/drivers/scsi/
Dses.c460 for (i = 0; i < edev->components; i++) { in ses_enclosure_find_by_addr()
480 int i, j, page7_len, len, components; in ses_enclosure_data_process() local
518 components = 0; in ses_enclosure_data_process()
542 components++, in ses_enclosure_data_process()
546 ecomp = &edev->component[components++]; in ses_enclosure_data_process()
622 int i, types, len, components = 0; in ses_intf_add() local
681 components += type_ptr[1]; in ses_intf_add()
721 scomp = kzalloc(sizeof(struct ses_component) * components, GFP_KERNEL); in ses_intf_add()
726 components, &ses_enclosure_callbacks); in ses_intf_add()
735 for (i = 0; i < components; i++) in ses_intf_add()
D53c700.scr34 ; SG components is preceded by a script fragment which moves the
D53c700_d.h_shipped37 ; SG components is preceded by a script fragment which moves the
/linux-4.4.14/security/integrity/
DKconfig8 of a number of different components including the Integrity
13 Each of these components can be enabled/disabled separately.
14 Refer to the individual components for additional details.
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dpower-controller.txt3 Power-management integrated circuits or miscellaneous hardware components are
5 components might need to define this capability, which tells the kernel that
/linux-4.4.14/drivers/hwtracing/coresight/
DKconfig10 a topological view of the CoreSight components based on a DT
11 specification and configure the right serie of components when a
39 components and a trace for bridging the gap between the on-chip
40 coresight components and a trace port collection engine, typically
/linux-4.4.14/Documentation/video4linux/bttv/
DTHANKS17 components on their cards. (E.g. how the tuner type is detected)
20 - Hauppauge for telling how the sound input is selected and what components
DCards19 All other cards only differ by additional components as tuners, sound
/linux-4.4.14/Documentation/dvb/
Dget_dvb_firmware24 @components = ( "sp8870", "sp887x", "tda10045", "tda10046",
39 for ($i=0; $i < scalar(@components); $i++) {
40 if ($cid eq $components[$i]) {
937 @components = sort @components;
938 for($i=0; $i < scalar(@components); $i++) {
939 print STDERR "\t" . $components[$i] . "\n";
/linux-4.4.14/samples/pktgen/
DREADME.rst35 configuring the different components of pktgen: pg_ctrl(), pg_thread()
38 These functions correspond to pktgens different components.
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Drenesas,rsrc-card.txt34 - audio-routing : A list of the connections between audio components.
37 use audio-prefix if some components is using same sink/sources naming.
Datmel-at91sam9g20ek-wm8731-audio.txt6 - atmel,audio-routing: A list of the connections between audio components.
Dux500-mop500.txt3 This node is responsible for linking together all ux500 Audio Driver components.
Datmel-sam9x5-wm8731-audio.txt8 - atmel,audio-routing: A list of the connections between audio components.
Dsamsung,odroidx2-max98090.txt10 components; each entry is a pair of strings, the first being the
Dnvidia,tegra-audio-wm9712.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Datmel-wm8904.txt6 - atmel,audio-routing: A list of the connections between audio components.
Dimx-audio-wm8962.txt13 - audio-routing : A list of the connections between audio components.
Domap-twl4030.txt12 - ti,audio-routing: List of connections between audio components.
Dnvidia,tegra-audio-wm8753.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Dnvidia,tegra-audio-alc5632.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Dimx-audio-sgtl5000.txt13 - audio-routing : A list of the connections between audio components.
Dimx-audio-es8328.txt10 - audio-routing : A list of the connections between audio components.
Dnvidia,tegra-audio-max98090.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Dnvidia,tegra-audio-rt5640.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Ddavinci-evm-audio.txt8 - ti,audio-routing : A list of the connections between audio components.
Domap-abe-twl6040.txt9 - ti,audio-routing: List of connections between audio components.
Dnvidia,tegra-audio-wm8903.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Dnvidia,tegra-audio-rt5677.txt12 - nvidia,audio-routing : A list of the connections between audio components.
Dfsl-asoc-card.txt43 - audio-routing : A list of the connections between audio components.
Dsimple-card.txt14 - simple-audio-card,routing : A list of the connections between audio components.
/linux-4.4.14/sound/aoa/
DKconfig7 Apple Onboard Audio components.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcoresight.txt3 CoreSight components are compliant with the ARM CoreSight architecture
5 SoCs tracing needs. These trace components can generally be classified as
11 * Required properties for all components *except* non-configurable replicators:
/linux-4.4.14/sound/core/
Dinit.c881 ptr = strstr(card->components, component); in snd_component_add()
886 if (strlen(card->components) + 1 + len + 1 > sizeof(card->components)) { in snd_component_add()
890 if (card->components[0] != '\0') in snd_component_add()
891 strcat(card->components, " "); in snd_component_add()
892 strcat(card->components, component); in snd_component_add()
Dcontrol.c734 strlcpy(info->components, card->components, sizeof(info->components)); in snd_ctl_card_info()
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dethernet.txt23 is used for components that can have configurable receive fifo sizes,
27 is used for components that can have configurable fifo sizes.
/linux-4.4.14/Documentation/devicetree/bindings/display/bridge/
Dadi,adv7511.txt15 arrangement of components on the data bus. The combination of the following
30 - adi,input-style: The input components arrangement variant (1, 2 or 3), as
/linux-4.4.14/Documentation/trace/
Dcoresight.txt15 that have many SoCs and other components like GPU and DMA engines. ARM has
16 developed a HW assisted tracing solution by means of different components, each
82 While on target configuration of the components is done via the APB bus,
84 a way to aggregate and distribute signals between CoreSight components.
88 the basic tracing functionality, enabling components such ETM/PTM, funnel,
167 perform base operations related to the components, each component having
/linux-4.4.14/drivers/staging/wilc1000/
DTODO7 - make spi and sdio components coexist in one build
/linux-4.4.14/drivers/media/platform/s5p-jpeg/
Djpeg-core.c794 int c, x, components; in exynos4_jpeg_parse_decode_h_tbl() local
809 components = get_byte(&jpeg_buffer); in exynos4_jpeg_parse_decode_h_tbl()
810 if (components == -1) in exynos4_jpeg_parse_decode_h_tbl()
812 while (components--) { in exynos4_jpeg_parse_decode_h_tbl()
889 int c, x, components; in exynos4_jpeg_parse_decode_q_tbl() local
897 components = get_byte(&jpeg_buffer); in exynos4_jpeg_parse_decode_q_tbl()
898 if (components == -1) in exynos4_jpeg_parse_decode_q_tbl()
901 exynos4_jpeg_set_dec_components(jpeg->regs, components); in exynos4_jpeg_parse_decode_q_tbl()
903 while (components--) { in exynos4_jpeg_parse_decode_q_tbl()
1100 int c, components = 0, notfound, n_dht = 0, n_dqt = 0; in s5p_jpeg_parse_hdr() local
[all …]
Djpeg-core.h206 u32 components; member
/linux-4.4.14/Documentation/fb/
Dapi.txt39 specifying color components layout.
114 Pixels are broken into red, green and blue components, and each component
124 blue components. The colormap is read-only for FB_VISUAL_STATIC_PSEUDOCOLOR
132 Pixels are broken into red, green and blue components, and each component
258 color components in memory.
268 green, blue and alpha (transparency) components. Location and size of each
Dinternals.txt80 pseudo color, where the red, green and blue components are always equal to
/linux-4.4.14/fs/ecryptfs/
DKconfig10 eCryptfs. Userspace components are required and can be
/linux-4.4.14/include/linux/
Denclosure.h114 int components; member
Dnfs_xdr.h1095 struct nfs4_string components[NFS4_PATHNAME_MAXCOMPONENTS]; member
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt4 components in the system. This information can be used to derive the rate at
/linux-4.4.14/Documentation/power/regulator/
Ddesign.txt14 have different power requirements, and not all components with power
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dbrcm,bcm2835-cprman.txt10 the PLL channels. Most other hardware components source from the
/linux-4.4.14/Documentation/acpi/
Ddebug.txt26 The "debug_layer" is a mask that selects components of interest, e.g., a
34 The possible components are defined in include/acpi/acoutput.h and
/linux-4.4.14/Documentation/vm/
Dnuma9 comprises multiple components or assemblies each of which may contain 0
11 disambiguate the hardware view of these physical components/assemblies
12 from the software abstraction thereof, we'll call the components/assemblies
16 of the system--although some components necessary for a stand-alone SMP system
Dpagemap.txt8 There are four components to pagemap:
Dtranshuge.txt26 components: 1) the TLB miss will run faster (especially with
38 - "graceful fallback": mm components which don't have transparent
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/ab8500/
Dfg.txt9 components of this module are:
/linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/
Dvideo.txt26 width expressed as a number of bits per pixel component. All components must
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Darm,smmu-v3.txt5 and event queues and adding support for the ATS and PRI components of
/linux-4.4.14/Documentation/video4linux/
Domap4_camera.txt8 Which contains several components that can be categorized in 3 big groups:
Dvivid.txt509 The generated data contains the In-phase and Quadrature components of a
/linux-4.4.14/Documentation/s390/
D3270.ChangeLog39 * the components are remodularized: added source modules are
Ds390dbf.txt21 Kernel components (e.g. device drivers) can register themselves at the debug
/linux-4.4.14/drivers/staging/lustre/lustre/
DKconfig27 Lustre components can also be found at
/linux-4.4.14/Documentation/netlabel/
Dintroduction.txt12 is composed of three main components, the protocol engines, the communication
/linux-4.4.14/Documentation/sound/oss/
DPSS-updates43 just configure non-sound components. 0 configures all components, a non-0
DREADME.ymfsb74 digital-in capable components has to be able to handle 48kHz Fs.
DREADME.OSS599 chips is to connect other audio components to the PC bus. The
/linux-4.4.14/drivers/uio/
DKconfig133 PRUSS driver requires user space components, examples and user space
151 (among other MF624 related information and software components)
/linux-4.4.14/Documentation/frv/
Dbooting.txt83 how to find its root filesystem. This is made up of the following components,
128 The remaining components are all optional:
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dcommon.txt9 can influence the way of the LED device initialization, the LED components
/linux-4.4.14/Documentation/devicetree/bindings/display/
Darm,pl11x.txt65 - PL110 and PL111 TFT 8:8:8 panel, R & B components swapped:
Dst,stih4xx.txt21 - sti-display-subsystem: Master device for DRM sub-components
22 This device must be the parent of all the sub-components and is responsible
/linux-4.4.14/drivers/net/ethernet/ibm/emac/
Dcore.h455 u32 components; member
Dcore.c2130 hdr->components = 0; in emac_ethtool_get_regs()
2136 hdr->components |= EMAC_ETHTOOL_REGS_ZMII; in emac_ethtool_get_regs()
2140 hdr->components |= EMAC_ETHTOOL_REGS_RGMII; in emac_ethtool_get_regs()
2144 hdr->components |= EMAC_ETHTOOL_REGS_TAH; in emac_ethtool_get_regs()
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Ddra7-atl.txt10 internally within the SoC or external components) two sets of bindings is needed:
/linux-4.4.14/Documentation/EDID/
DHOWTO.txt5 either correctly working because all components follow the standards -
/linux-4.4.14/Documentation/early-userspace/
DREADME12 It consists of several major infrastructure components:
94 The standalone klibc distribution currently provides three components,
/linux-4.4.14/Documentation/laptops/
Ddisk-shock-protection.txt29 Please note, however, that other components have to be set up on your
128 source development of the required software components so far, Linux
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt11 information on its major components.
28 Each of these components is represented in the subsystem by an associated data
29 structure. The core logical components of the RapidIO subsystem are defined
114 discovery methods as statically linked components or loadable modules.
/linux-4.4.14/Documentation/mic/
Dmic_overview.txt35 Here is a block diagram of the various components described above. The
/linux-4.4.14/fs/nfsd/
Dnfs4xdr.c1924 char *components, char esc_enter, in nfsd4_encode_components_esc() argument
1933 dprintk("nfsd4_encode_components(%s)\n", components); in nfsd4_encode_components_esc()
1941 end = str = components; in nfsd4_encode_components_esc()
1984 char *components) in nfsd4_encode_components() argument
1986 return nfsd4_encode_components_esc(xdr, sep, components, 0, 0); in nfsd4_encode_components()
2016 struct dentry **components = NULL; in nfsd4_encode_path() local
2036 new = krealloc(components, in nfsd4_encode_path()
2041 components = new; in nfsd4_encode_path()
2043 components[ncomponents++] = cur.dentry; in nfsd4_encode_path()
2053 struct dentry *dentry = components[ncomponents - 1]; in nfsd4_encode_path()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.txt51 geography of a PCI bus address by concatenating the various components to
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt38 its components.
/linux-4.4.14/Documentation/networking/
Daltera_tse.txt6 using the SGDMA and MSGDMA soft DMA IP components. The driver uses the
18 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP
19 components that can be assembled and built into an FPGA using the Altera
DREADME.ipw2200239 access various components of the operating system. The Intel(R)
DLICENSE.qlcnic172 form) with the major components (compiler, kernel, and so on) of the
DLICENSE.qlge172 form) with the major components (compiler, kernel, and so on) of the
Dswitchdev.txt11 Figure 1 is a block diagram showing the components of the switchdev model for
Dpacket_mmap.txt1002 components of a system.
Drxrpc.txt85 that has both kernel (filesystem) and userspace (utility) components.
Darcnet-hardware.txt2355 ?? -- Some components on a smaller board and attached with 20 pins all
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dti-edma.txt3 The eDMA3 consists of two components: Channel controller (CC) and Transfer
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt168 If you built the RDMA components as modules, load them at
201 For the NFS components enabled above (client and/or server),
/linux-4.4.14/Documentation/filesystems/cifs/
DTODO93 1) check out max path names and max path name components against various server
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-power85 components against damage from overvoltage on the input supply. See
Dsysfs-bus-coresight-devices-etm3x8 of coresight components linking the source to the sink is
Dsysfs-bus-coresight-devices-etm4x8 of coresight components linking the source to the sink is
Dsysfs-bus-iio1260 components or just infrared light, respectively.
1283 Raw value of quaternion components using a format
/linux-4.4.14/include/sound/
Dcore.h103 char components[128]; /* card components delimited with member
/linux-4.4.14/arch/arm/boot/dts/
Ddove-cm-a510.dtsi46 * The CM-A510 comes with several optional components:
Dtegra124-jetson-tk1.dts1375 /* Expansion GEN1_I2C_*, mini-PCIe I2C, on-board components */
1421 /* Expansion PWR_I2C_*, on-board components */
/linux-4.4.14/Documentation/sound/alsa/
Dtimestamping.txt38 of time as measured by different components of audio hardware. In
108 hardware components the delay is typically not known with precision.
/linux-4.4.14/Documentation/
Dintel_txt.txt76 pre-launch components can be removed from the trust chain, DMA
77 protection is provided to all launched components, a large number
Drfkill.txt34 The rfkill subsystem is composed of three main components:
Dxz.txt24 XZ related components in the kernel
Dgcov.txt159 machine. If any of the path components is symbolic link, the actual
Dprintk-formats.txt249 n last components. %pD does the same thing for struct file.
Dkernel-doc-nano-HOWTO.txt116 form of block comments above functions. The components of this system
Dunshare.txt228 etc, had roughly two components. The first component allocated
Drpmsg.txt28 frameworks talking with remote OMX components) or kernel drivers (controlling
Dinitrd.txt118 support for the initial RAM disk enabled. Also, at least all components
Dmemory-barriers.txt347 components of the system.
401 other components of the system.
418 the other components of the system.
432 ACQUIRE operation with respect to the other components of the system.
447 before the RELEASE operation with respect to the other components of the
Dedac.txt106 Within this directory there currently reside 2 components:
Dmd.txt216 multipath), all components must be the same size - or at least
Dkernel-parameters.txt473 when initialising the APIC and IO-APIC components.
/linux-4.4.14/fs/nfs/
Dnfs4namespace.c43 const struct nfs4_string *component = &pathname->components[n]; in nfs4_pathname_string()
Dnfs4xdr.c3580 struct nfs4_string *component = &path->components[path->ncomponents]; in decode_pathname()
3594 path->components[0].len=0; in decode_pathname()
3595 path->components[0].data=NULL; in decode_pathname()
/linux-4.4.14/drivers/mfd/
DKconfig49 individual components like LCD backlight, LEDs, GPIOs and Kepad
103 components like regulators or the PEK (Power Enable Key) under the
154 individual components like LCD backlight, voltage regulators,
283 individul components like voltage regulators under corresponding
455 select individual components like voltage regulators, RTC and
467 components like codec device, headset/Mic device under the
478 select individual components like voltage regulators, RTC and
/linux-4.4.14/Documentation/power/
Dstates.txt70 powering down some more low-level components that aren't directly controlled by
Druntime_pm.txt647 or hardware operation. Instead, all hardware components are put into low-power
649 state effectively follows from the states the hardware components end up in
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dbrcm,brcmnand.txt59 handled via standard, modular components (e.g., their interrupts look like a
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt124 components are needed:
/linux-4.4.14/drivers/net/wireless/ath/ath9k/
DKconfig93 as DFS support requires more components that still need to be
/linux-4.4.14/Documentation/filesystems/
Dceph.txt15 * Easy deployment: most FS components are userspace daemons
Dntfs.txt240 You will need to create a table of the components of the volume/stripe set and
252 components and their sizes in sectors, i.e. multiples of 512-byte blocks.
291 <Disk> components where you will get the LDM Name for the disk that is found in
DLocking487 components. And there are other reasons why the current interface is a mess...
/linux-4.4.14/Documentation/gpio/
Ddrivers-on-gpio.txt95 embedded hacking in particular by providing ready-made components.
/linux-4.4.14/Documentation/arm/
DIXP4xx38 The following components of the chips are not supported by Linux and
/linux-4.4.14/Documentation/hwmon/
Dltc297875 additional components on a single die. The chip is instantiated and reported
Dlm9361 processor Xeon class motherboard with a minimum of external components.
/linux-4.4.14/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt7 components, those drivers can be lightened making it a user of the framework.
/linux-4.4.14/include/uapi/sound/
Dasound.h815 …unsigned char components[128]; /* card components / fine identification, delimited with one space … member
/linux-4.4.14/fs/
DKconfig.binfmt122 If any crucial components of your system (such as /sbin/init
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt30 - Monitoring hardware state and platform components
/linux-4.4.14/arch/x86/crypto/
Dsha512-avx2-asm.S228 # XOR the three components
233 # Add three components, w[t-16], w[t-7] and sigma0
/linux-4.4.14/Documentation/driver-model/
Dplatform.txt156 It's built from two components:
/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt241 generated by devices will normally have 3 components--
/linux-4.4.14/Documentation/PCI/
Dpcieaer-howto.txt24 required of all PCI Express components providing a minimum defined
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dfman.txt403 components in the system support a faster speed.
/linux-4.4.14/Documentation/arm/OMAP/
DDSS126 Some clarification what the different components do:
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt71 The disadvantage is there are more distinct components to configure, and
/linux-4.4.14/scripts/
Dspelling.txt249 componnents||components
/linux-4.4.14/Documentation/i2c/
Dwriting-clients127 and complex components such as DVB adapters, those assumptions became more
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dthermal.txt5 A thermal structure includes thermal zones and their components,
/linux-4.4.14/Documentation/scsi/
DLICENSE.qla4xxx173 form) with the major components (compiler, kernel, and so on) of the
DLICENSE.qla2xxx174 form) with the major components (compiler, kernel, and so on) of the
Dscsi_fc_transport.txt13 This file documents the features and components of the SCSI FC Transport.
/linux-4.4.14/drivers/staging/rtl8192u/
Dcopying162 form) with the major components (compiler, kernel, and so on) of the
/linux-4.4.14/tools/usb/usbip/
DCOPYING162 form) with the major components (compiler, kernel, and so on) of the
/linux-4.4.14/Documentation/usb/
Dusb-serial.txt107 This driver is only one of a set of components required to utilize
Dpower-management.txt36 needs to use it. (There also are forms of PM in which components are
/linux-4.4.14/drivers/staging/rtl8192e/
Dlicense165 components (compiler, kernel, and so on) of the operating system on which
/linux-4.4.14/
DCOPYING178 form) with the major components (compiler, kernel, and so on) of the
/linux-4.4.14/drivers/char/
DKconfig444 kernel driver and a user level application. Together these components
/linux-4.4.14/arch/arm64/
DKconfig773 kernel at EL1. AArch32-specific components such as system calls,
/linux-4.4.14/firmware/
DWHENCE247 Licence: "all firmware components are redistributable in binary form"
/linux-4.4.14/Documentation/cgroups/
Dmemory.txt562 For efficiency, as other kernel components, memory cgroup uses some optimization
/linux-4.4.14/Documentation/security/
DSmack.txt16 Smack consists of three major components:
/linux-4.4.14/Documentation/block/
Dbiodoc.txt250 Kernel components like filesystems could also take their own i/o scheduling
/linux-4.4.14/Documentation/RCU/
DRTFP.txt1962 Lays out the three basic components of RCU: (1) publish-subscribe,
/linux-4.4.14/drivers/staging/speakup/
Dspkguide.txt547 with some components built into the kernel, and others as modules. As