Home
last modified time | relevance | path

Searched refs:starts (Results 1 – 186 of 186) sorted by relevance

/linux-4.1.27/arch/arm/boot/dts/
Domap54xx-clocks.dtsi124 ti,index-starts-at-one;
167 ti,index-starts-at-one;
197 ti,index-starts-at-one;
222 ti,index-starts-at-one;
231 ti,index-starts-at-one;
240 ti,index-starts-at-one;
249 ti,index-starts-at-one;
258 ti,index-starts-at-one;
267 ti,index-starts-at-one;
276 ti,index-starts-at-one;
[all …]
Ddra7xx-clocks.dtsi211 ti,index-starts-at-one;
231 ti,index-starts-at-one;
242 ti,index-starts-at-one;
274 ti,index-starts-at-one;
300 ti,index-starts-at-one;
342 ti,index-starts-at-one;
376 ti,index-starts-at-one;
410 ti,index-starts-at-one;
421 ti,index-starts-at-one;
455 ti,index-starts-at-one;
[all …]
Domap44xx-clocks.dtsi156 ti,index-starts-at-one;
193 ti,index-starts-at-one;
225 ti,index-starts-at-one;
236 ti,index-starts-at-one;
255 ti,index-starts-at-one;
292 ti,index-starts-at-one;
310 ti,index-starts-at-one;
327 ti,index-starts-at-one;
343 ti,index-starts-at-one;
375 ti,index-starts-at-one;
[all …]
Dam43xx-clocks.dtsi218 ti,index-starts-at-one;
229 ti,index-starts-at-one;
240 ti,index-starts-at-one;
258 ti,index-starts-at-one;
276 ti,index-starts-at-one;
294 ti,index-starts-at-one;
313 ti,index-starts-at-one;
596 ti,index-starts-at-one;
672 ti,index-starts-at-one;
Domap3xxx-clocks.dtsi31 ti,index-starts-at-one;
209 ti,index-starts-at-one;
251 ti,index-starts-at-one;
298 ti,index-starts-at-one;
316 ti,index-starts-at-one;
340 ti,index-starts-at-one;
366 ti,index-starts-at-one;
424 ti,index-starts-at-one;
452 ti,index-starts-at-one;
481 ti,index-starts-at-one;
[all …]
Dam33xx-clocks.dtsi185 ti,index-starts-at-one;
194 ti,index-starts-at-one;
203 ti,index-starts-at-one;
219 ti,index-starts-at-one;
235 ti,index-starts-at-one;
259 ti,index-starts-at-one;
276 ti,index-starts-at-one;
Domap2430-clocks.dtsi70 ti,index-starts-at-one;
338 ti,index-starts-at-one;
343 ti,index-starts-at-one;
Domap3430es1-clocks.dtsi25 ti,index-starts-at-one;
146 ti,index-starts-at-one;
Domap24xx-clocks.dtsi99 ti,index-starts-at-one;
109 ti,index-starts-at-one;
240 ti,index-starts-at-one;
270 ti,index-starts-at-one;
287 ti,index-starts-at-one;
310 ti,index-starts-at-one;
334 ti,index-starts-at-one;
Domap34xx-omap36xx-clocks.dtsi163 ti,index-starts-at-one;
182 ti,index-starts-at-one;
Domap36xx-omap3430es2plus-clocks.dtsi152 ti,index-starts-at-one;
Domap36xx-am35xx-omap3430es2plus-clocks.dtsi43 ti,index-starts-at-one;
Domap2420-clocks.dtsi59 ti,index-starts-at-one;
/linux-4.1.27/Documentation/devicetree/bindings/clock/ti/
Dmux.txt24 "index-starts-at-one" modified the scheme as follows:
47 - ti,index-starts-at-one : valid input select programming starts at 1, not
59 ti,index-starts-at-one;
Ddivider.txt17 ti,index-starts-at-one - valid divisor values start at 1, not the default
69 - ti,index-starts-at-one : valid divisor programming starts at 1, not zero,
86 ti,index-starts-at-one;
104 ti,index-starts-at-one;
Dautoidle.txt26 ti,index-starts-at-one;
Dcomposite.txt47 ti,index-starts-at-one;
/linux-4.1.27/Documentation/isdn/
DREADME.audio49 CONNECT and starts sending audio data to
82 with CONNECT and starts sending audio data
98 starts sending audio data to the application. There are several
129 CONNECT, and starts transferring data from application to the phone line.
DINTERFACE37 the version number. If that number starts with 0, it refers to the old,
38 separately distributed package. If it starts with one of the letters
138 int channel-number locally to the HL-driver. (starts with 0)
167 int channel-number locally to the HL-driver. (starts with 0)
191 int channel-number locally to the HL-driver. (starts with 0)
DsyncPPP.FAQ37 If your remote side immediately starts to send
DREADME420 which starts with "eth". The number of "eth"-interfaces is limited by
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-rpmsg21 starts listening on one end of a channel, it assigns it with
39 starts listening on one end of a channel, it assigns it with
65 or remote, starts listening on it for messages (and is thus
Dsysfs-driver-xen-blkback16 max_persistent_grants, the LRU kicks in and starts
Dsysfs-class-uwb_rc-wusbhc7 This starts the host controller, allowing it to accept connection from
Ddev-kmsg68 The human readable text string starts directly after the ';'
Dsysfs-block-bcache84 backing device, writeback from cache to backing device starts
/linux-4.1.27/Documentation/
Dworkqueue.txt191 new work item starts execution until thawed.
271 0 w0 starts and burns CPU
275 20 w1 starts and burns CPU
278 35 w2 starts and burns CPU
285 0 w0 starts and burns CPU
287 5 w1 starts and burns CPU
289 10 w2 starts and burns CPU
299 0 w0 starts and burns CPU
301 5 w1 starts and burns CPU
306 20 w2 starts and burns CPU
[all …]
Dmd-cluster.txt40 DLM starts node count from one and bitmap slots start from zero, one is
127 starts a cluster recovery thread. The cluster recovery thread:
138 of the areas which are suspended. Before a resync starts, the node
Dpwm.txt103 characterizes a signal starts high for the duration of the duty cycle and
105 polarity starts low for the duration of the duty cycle and goes high for the
Dsvga.txt10 kernel decompression starts) and works only on 80X86 machines.
81 The modes displayed on the menu are partially sorted: The list starts with
Dpinctrl.txt330 The GPIO range of "chip a" starts from the GPIO base of 32 and actual
331 pin range also starts from 32. However "chip b" has different starting
332 offset for the GPIO range and pin range. The GPIO range of "chip b" starts
333 from GPIO number 48, while the pin range of "chip b" starts from 64.
1303 mux in and bias pins in a certain way before the GPIO subsystems starts to
Dparport-lowlevel.txt847 Find a device by class. The search starts from device number from+1.
879 Find a device by vendor and model. The search starts from device
Dmd.txt284 When written to inactive array, starts without resync
291 When written to inactive array, starts with resync
Drpmsg.txt54 When a driver starts listening on a channel, its rx callback is bound with
DIPMI.txt419 can be specified when the driver starts up.
521 can be specified when the driver starts up.
Ddma-buf-sharing.txt410 interesting ways depending upong the exporter (if userspace starts depending
Dedac.txt710 inject_enable starts the error generation when something different
DCodingStyle24 a block of control starts and ends. Especially when you've been looking
DDMA-API-HOWTO.txt632 ends and the second one starts on a page boundary - in fact this is a huge
DSubmittingPatches142 Solve only one problem per patch. If your description starts to get
Dkernel-parameters.txt3022 given grace period before RCU starts
/linux-4.1.27/Documentation/mmc/
Dmmc-async-req.txt38 It starts a new MMC command request for a host. The function isn't
40 for completion of that request and starts the new one and returns. It
42 request it starts the new request and returns immediately.
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dcs4270.txt14 deasserted before communication to the codec starts.
Dak4104.txt16 deasserted before communication to the device starts.
Dcs4265.txt16 deasserted before communication to the codec starts.
Dst,sta32x.txt10 deasserted before communication to the codec starts.
14 starts.
Dst,sta350.txt10 deasserted before communication to the codec starts.
14 starts.
Dcs35l32.txt16 deasserted before communication to the codec starts.
/linux-4.1.27/Documentation/leds/
Dledtrig-oneshot.txt40 shot - write any non-empty string to signal an events, this starts a blink
55 echo 1 > shot # led starts blinking, ignored if already blinking
Dledtrig-transient.txt119 echo 1 > activate - starts timer = duration when duration is not 0.
/linux-4.1.27/arch/cris/arch-v10/lib/
Ddram_init.S90 lslq 16, $r2 ; mrs data starts at bit 16
106 lslq 9, $r4 ; Command starts at bit 9
/linux-4.1.27/Documentation/video4linux/
Dpxa_camera.txt16 When a buffer is queued (pxa_videobuf_ops->buf_queue), the QCI starts.
85 starts the DMA chain.
87 The DMA chain starts transferring data into videobuffer RAM pages.
Dhauppauge-wintv-cx88-ir.txt41 over time, so don't assume any sample starts at any particular place.
DREADME.cx8817 - Neverless the builtin TV sound decoder starts working now,
Domap3isp.txt76 triggered exactly when the reception of the first line of the frame starts
208 done before streaming, it will take effect as soon as the pipeline starts to
Dmeye.txt104 call to MEYEIOC_QBUF_CAPT starts the streaming capture.
DREADME.cpia281 The compression engine starts out at maximum compression, and will
Dv4l2-controls.txt460 starts or stops streaming.
Dv4l2-framework.txt803 device node you register always starts with index 0.
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-tz1090-pdc.txt7 region. This starts at and cover the SOC_GPIO_CONTROL registers.
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/
Dgpio-wdt.txt11 - level: Low or high level starts counting WDT timeout,
/linux-4.1.27/arch/cris/boot/compressed/
DREADME21 assumes the DRAM starts at 0x40000000 and that it is at least 8 MB,
/linux-4.1.27/arch/arm/kernel/
Dhead-nommu.S216 ldr r0, =PLAT_PHYS_OFFSET @ RAM starts at PHYS_OFFSET
228 mov r0, #0 @ BG region starts at 0x0
/linux-4.1.27/Documentation/hwmon/
Dw8379350 - If the value is 3, it starts monitoring using a remote termal diode
52 - If the value is 6, it starts monitoring using the temperature sensor
Dasc7621188 to the point where the automatic thermal control circuit starts
Dsysfs-interface50 threshold, "min" (low threshold). Numbering usually starts from 1,
/linux-4.1.27/Documentation/filesystems/
Dqnx6.txt64 The Audi MMI 3G first superblock directly starts at byte 0.
90 The filesize is stored 64bit. Inode counting starts with 1. (whilst long
141 The first block is block 0, which starts 0x1000 after superblock start.
Dspufs.txt298 uled to a physical SPU, it starts execution at the instruction pointer
DLocking237 ->readpages() populates the pagecache with the passed pages and starts
Dcoda.txt209 pre-processing, the VFS starts invoking exported routines in the FS
211 request starts, and here the Coda specific kernel code comes into
/linux-4.1.27/Documentation/devicetree/
Dchangesets.txt24 3. mutex_lock(of_mutex) - starts a changeset; The global of_mutex
Dusage-model.txt331 The trick is that the kernel starts at the root of the tree and looks
Dbooting-without-of.txt465 starts at the offset given by off_dt_strings).
471 starts at the offset given by off_dt_struct).
642 "OF_DT_BEGIN_NODE" token starts a new node, and the "OF_DT_END_NODE"
/linux-4.1.27/Documentation/arm/
DPorting68 always starts at zero, this is the maximum address that a user
97 Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the
DBooting88 A valid tagged list starts with ATAG_CORE and ends with ATAG_NONE.
/linux-4.1.27/drivers/spi/
Dspi-s3c24xx-fiq.S35 @ each entry starts with a word entry of how long it is
/linux-4.1.27/Documentation/device-mapper/
Ddm-flakey.txt41 Counting starts at 1, to replace the first byte.
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dfsl-spi.txt46 - fsl,csbef: chip select assertion time in bits before frame starts
/linux-4.1.27/Documentation/x86/
Dearly-microcode.txt17 During BSP boot (before SMP starts), if the kernel finds the microcode file in
Dintel_mpx.txt35 starts. New instruction prefixes are noops for old CPUs.
Dboot.txt899 The 32-bit (non-real-mode) kernel starts at offset (setup_sects+1)*512
/linux-4.1.27/Documentation/video4linux/cx88/
Dhauppauge-wintv-cx88-ir.txt41 over time, so don't assume any sample starts at any particular place.
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dnvidia,tegra20-kbc.txt30 - nvidia,repeat-delay-ms: delay in milliseconds before repeat starts
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Ddma.txt22 - cell-index : DMA channel index starts at 0.
88 - cell-index : DMA channel index starts at 0.
Dmpc5200.txt142 use when setting up PSC clocking. cell-index number starts at '0'. ie:
/linux-4.1.27/arch/cris/arch-v32/mach-fs/
Ddram_init.S61 lslq 2, $r4 ; mrs_data starts at bit 2
/linux-4.1.27/tools/perf/Documentation/
Dperf-annotate.txt66 used. This interfaces starts by centering on the line with more
/linux-4.1.27/arch/cris/boot/rescue/
Dkimagerescue.S48 ;; since etrax actually starts at address 2 when booting from flash, we
Dhead_v10.S123 ;; Since etrax actually starts at address 2 when booting from flash, we
/linux-4.1.27/Documentation/networking/
Dcxacru.txt90 "restart" (stops, waits 1.5s, then starts)
Dnetif-msg.txt24 3 Interface starts and stops, including normal status messages
Dbaycom.txt72 starts to send as soon as there's a packet to transmit and does not care
73 about DCD, i.e. it starts to send even if there's someone else on the channel.
Dnetdev-FAQ.txt38 on the cadence of Linux development. Each new release starts off with
73 Finally, the vX.Y gets released, and the whole cycle starts over.
Dnetconsole.txt55 Built-in netconsole starts immediately after the TCP stack is
Dbatman-adv.txt52 starts using/broadcasting on this/these interface(s).
Dfilter.txt455 the user pre-selected packet. Numbering starts just as in Wireshark
834 loops and other CFG validation; second step starts from the first insn and
1013 Second step starts from the first insn and descends all possible paths.
Dixgb.txt240 # set number of unprocessed input packets before kernel starts dropping them; default 300
Dtimestamping.txt143 The counter starts at zero. It is initialized the first time that
Dscaling.txt181 net.core.netdev_max_backlog), the kernel starts a per-flow packet
Darcnet.txt506 commands, as well as any pertinent log entries (ie. anything that starts
Dip-sysctl.txt685 this number, UDP starts to moderate memory usage.
1810 this number, SCTP starts to moderate memory usage.
/linux-4.1.27/Documentation/scsi/
Dbnx2fc.txt37 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
Dscsi_eh.txt258 2. EH starts
DChangeLog.megaraid450 no BIOS to start the controller. The FW starts to boot after receiving
Dncr53c8xx.txt1031 starts the next job.
/linux-4.1.27/arch/m68k/
DKconfig.machine330 Define the address that RAM starts at. On many platforms this is
383 and the kernel starts after that. The 0x400 default was based on
402 Define the address that the ROM region starts at. Some platforms
/linux-4.1.27/Documentation/block/
Dwriteback_cache_control.txt27 storage before the flagged bio starts. In addition the REQ_FLUSH flag can be
Dcfq-iosched.txt219 to IOPS mode and starts providing fairness in terms of number of requests
Dbiodoc.txt961 starts.
/linux-4.1.27/Documentation/locking/
Drt-mutex.txt66 it starts executing it can acquire the mutex. Until the mutex is taken
Dlockstat.txt164 (subclass starts from 0), since in this case, as line 50 suggests,
/linux-4.1.27/Documentation/vm/
Dpage_owner.txt53 is initialized some time later than that page allocator starts in sparse
Dfrontswap.txt67 When a workload starts swapping, performance falls through the floor.
Dnuma_memory_policy.txt182 policy can be viewed as a Preferred policy that starts at the node
/linux-4.1.27/Documentation/filesystems/nfs/
Drpc-server-gss.txt89 before starting nfsd. Whoever starts nfsd can guarantee this by reading
Dnfsroot.txt180 To specify which file contains the program that starts system
/linux-4.1.27/Documentation/kbuild/
Dkconfig-language.txt37 Every line starts with a key word and can be followed by multiple
38 arguments. "config" starts a new config entry. The following lines
253 line starts with a keyword (except help texts). The following keywords
/linux-4.1.27/Documentation/acpi/
Dvideo_extension.txt105 disable this behaviour once a GUI environment starts up and wants to have full
/linux-4.1.27/Documentation/rapidio/
Drapidio.txt189 they must be loaded before enumeration/discovery process starts.
203 to be started before an enumeration starts to ensure that all RapidIO
316 must ensure that they are loaded before the enumeration/discovery starts.
/linux-4.1.27/Documentation/parisc/
Dregisters17 CR16 (Interval Timer) read for cycle count/write starts Interval Tmr
/linux-4.1.27/Documentation/cgroups/
Ddevices.txt13 The root device cgroup starts with rwm to 'all'. A child device
/linux-4.1.27/drivers/mtd/ubi/
DKconfig20 of UBI devices. When this threshold is exceeded, UBI starts performing
/linux-4.1.27/Documentation/frv/
Datomic-ops.txt78 It starts by setting ICC3.Z to true for later use, and also transforming that into CC3 being in the
/linux-4.1.27/arch/s390/kernel/
Dhead.S50 .long 0x02000410,0x60000050 # Initial processing starts
/linux-4.1.27/Documentation/scheduler/
Dsched-domains.txt45 CPU's runqueue and the newly found busiest one and starts moving tasks from it
Dcompletion.txt213 a thread starts waiting. This is achieved by the waiter "consuming"
Dsched-deadline.txt133 arrival time r_j (the time when the job starts), an amount of computation
/linux-4.1.27/Documentation/power/
Dstates.txt48 operating state is lost (the CPU retains power), so the system easily starts up
Dswsusp-dmcrypt.txt129 If resume starts, script execution terminates here.
Druntime_pm.txt597 ways. If a device is active when a system sleep starts, everything is
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt58 in jiffies. An RCU-tasks stall warning starts wtih the line:
92 Finally, if the grace period ends just as the stall warning starts
Dtorture.txt124 The number of seconds to wait after rcutorture starts
/linux-4.1.27/drivers/scsi/
Dscsi_debug.c3895 int starts[SDEBUG_MAX_PARTS + 2]; in sdebug_build_parts() local
3911 starts[0] = sdebug_sectors_per; in sdebug_build_parts()
3913 starts[k] = ((k * sectors_per_part) / heads_by_sects) in sdebug_build_parts()
3915 starts[scsi_debug_num_parts] = num_sectors; in sdebug_build_parts()
3916 starts[scsi_debug_num_parts + 1] = 0; in sdebug_build_parts()
3921 for (k = 0; starts[k + 1]; ++k, ++pp) { in sdebug_build_parts()
3922 start_sec = starts[k]; in sdebug_build_parts()
3923 end_sec = starts[k + 1] - 1; in sdebug_build_parts()
/linux-4.1.27/Documentation/cris/
DREADME131 Init starts up...
/linux-4.1.27/Documentation/usb/
Derror-codes.txt159 disconnect. In the interval before the hub driver starts disconnect
DWUSB-Design-overview.txt284 starts sending MMCs.
308 into /devconnect/). This process starts the authentication process for
Dgadget_serial.txt164 plugged in, the "Found New Hardware Wizard" starts up. Select
Dusb-serial.txt235 The Earthmate starts out at 4800 8N1 by default... the driver will
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dhead.S32 ;; since etrax actually starts at address 2 when booting from flash, we
342 ;; init_task (but starts in the top of the page, size 8192)
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-class-ubi200 volume update starts, and cleaned when it ends. So the presence
/linux-4.1.27/Documentation/ia64/
Dserial.txt75 kernel starts booting.
/linux-4.1.27/Documentation/fb/
Dvesafb.txt136 the video memory (i.e. starts reading from top if it
Duvesafb.txt66 the video memory (i.e. starts reading from top if it
Dframebuffer.txt206 Since the monitor doesn't know when a new scanline starts, the graphics board
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt84 starts at an offset of 0 kB from the beginning of the floppy.
/linux-4.1.27/drivers/block/paride/
DTransition-notes13 the result of ps_tq execution. Therefore, the sequence starts with
/linux-4.1.27/Documentation/security/
Dkeys-request-key.txt9 The process starts by either the kernel requesting a service by calling
/linux-4.1.27/Documentation/sound/oss/
DPAS1630 Sound configuration starts by making some yes/no questions. Be careful
DREADME.OSS731 Sound configuration starts by making some yes/no questions. Be careful
/linux-4.1.27/Documentation/trace/
Dmmiotrace.txt126 one line in the log. A record starts with a keyword, followed by keyword-
Dftrace.txt470 buffer and starts dropping events.
2066 starts of pointing to a simple return. (Enabling FTRACE will
/linux-4.1.27/drivers/usb/usbip/
Dusbip_protocol.txt166 0xC + | | | The second exported USB device starts at i=1
/linux-4.1.27/arch/m68k/ifpsp060/
DTEST.DOC201 # ftest.sa starts here; start of "Entry-point" section.
/linux-4.1.27/arch/frv/
DKconfig300 So if the linker starts complaining that accesses to GPREL data are
/linux-4.1.27/drivers/mtd/devices/
DKconfig182 available RAM starts, and the MTDRAM driver will use it instead of
/linux-4.1.27/drivers/xen/
DKconfig182 PCI topology starts at 00.00.0, or (1) for passthrough if you want
/linux-4.1.27/drivers/staging/panel/
DKconfig22 modules with different arguments. Numbering starts with '0' for LPT1,
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt3244 starts at address 0x1000b1b1 <handle_mm_fault+57>
3258 starts at address 0x1000b1b7 <handle_mm_fault+63>
3262 starts at address 0x1000b1d0 <handle_mm_fault+88>
3266 starts at address 0x1000b1da <handle_mm_fault+98>
3270 starts at address 0x1000b1f0 <handle_mm_fault+120>
3274 starts at address 0x1000b200 <handle_mm_fault+136>
3278 starts at address 0x1000b210 <handle_mm_fault+152>
3281 Line 1168 of "memory.c" starts at address 0x1000b21e <handle_mm_fault+166>
3583 starts at address 0x1001c2a1 <block_write+1073>
3586 Line 110 of "block_dev.c" starts at address 0x1001c2bf <block_write+1103>
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-kernel-api.txt122 * start: this is a pointer to the routine that starts the watchdog timer
/linux-4.1.27/Documentation/development-process/
D3.Early-stage12 Like any engineering project, a successful kernel enhancement starts with a
D2.Process66 At that point the whole process starts over again.
/linux-4.1.27/arch/powerpc/boot/dts/
Dvirtex440-ml510.dts344 * i/o region (which starts at 0xa0000000) for pci
/linux-4.1.27/drivers/video/backlight/
DKconfig56 power control driver for it. The panel starts up in power
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt151 starts to stutter due to this.
/linux-4.1.27/Documentation/spi/
Dspi-summary100 clock starts low, so the first (leading) edge is rising, and
102 starts high, so the first (leading) edge is falling.
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt391 This function handles the trip events from sensor drivers. It starts
/linux-4.1.27/tools/perf/
Ddesign.txt195 The 'disabled' bit specifies whether the counter starts out disabled
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt288 and starts the transfer. Whenever that transfer is done, it
/linux-4.1.27/arch/s390/
DKconfig718 Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
/linux-4.1.27/tools/usb/usbip/
DCOPYING314 when it starts in an interactive mode:
/linux-4.1.27/drivers/staging/rtl8192e/
Dlicense313 it starts in an interactive mode:
/linux-4.1.27/drivers/staging/rtl8192u/
Dcopying314 when it starts in an interactive mode:
/linux-4.1.27/
DCOPYING330 when it starts in an interactive mode:
/linux-4.1.27/Documentation/arm64/
Dacpi_object_usage.txt366 the driver expects before it starts probing.
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt139 The linear range starts at (gfn << PAGE_SHIFT) and its size is determined
/linux-4.1.27/Documentation/mtd/
Dnand_ecc.txt451 For 4 the code starts with:
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1376 then starts ( & sometimes terminates IO ).
1642 run: (re)starts a program
2070 ( this starts the network stack & hopefully calls ifconfig tr0 up ).
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.reg66 * Each bit, when set starts a specific SCSI sequence on the bus
Daic79xx.seq904 * command phase starts. There is only one problem
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt706 versions of libc.so.5 from 1996) that assume that brk area starts
/linux-4.1.27/drivers/video/fbdev/
DKconfig1265 The driver starts in monitor mode. You must use the matroxset tool
1315 The driver starts in monitor mode and you must use the matroxset
/linux-4.1.27/drivers/mfd/
DKconfig121 'pre-amble' bytes before the response actually starts.
/linux-4.1.27/drivers/rtc/
DKconfig43 starts up, and when it resumes from a low power state. This
/linux-4.1.27/arch/arm/
DKconfig1162 which starts prior to an ASID switch but completes afterwards. This
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt1098 speakup + f2. Speakup will tell you that the window starts at the
/linux-4.1.27/arch/x86/
DKconfig1952 First, resume from hibernate or suspend always starts from CPU0.