Home
last modified time | relevance | path

Searched refs:starting (Results 1 – 200 of 281) sorted by relevance

12

/linux-4.4.14/net/ceph/
Dauth_none.c18 xi->starting = true; in reset()
32 return !xi->starting; in is_authenticated()
39 return xi->starting; in should_authenticate()
56 xi->starting = false; in handle_reply()
129 xi->starting = true; in ceph_auth_none_init()
Dauth_none.h21 bool starting; member
Dauth_x.h40 bool starting; member
Dauth_x.c511 if (xi->starting) { in ceph_x_handle_reply()
520 xi->starting = false; in ceph_x_handle_reply()
646 xi->starting = true; in ceph_x_reset()
778 xi->starting = true; in ceph_x_init()
/linux-4.4.14/Documentation/isdn/
DINTERFACE87 int Channel-number locally to the driver. (starting with 0)
252 arg = channel-number locally to the driver. (starting with 0)
274 arg = channel-number locally to the driver. (starting with 0)
285 arg = channel-number locally to the driver. (starting with 0)
297 arg = channel-number locally to the driver. (starting with 0)
308 arg = channel-number locally to the driver. (starting with 0)
319 arg = channel-number locally to the driver. (starting with 0)
334 arg = channel-number locally to the driver. (starting with 0)
345 arg = channel-number locally to the driver. (starting with 0)
356 arg = channel-number locally to the driver. (starting with 0)
[all …]
DsyncPPP.FAQ141 A: When starting, the ipppd calls functions which may
/linux-4.4.14/Documentation/fb/
Dpxafb.txt100 c. starting horizontal position (XPOS) should start on a 32-bit
115 3) var->nonstd for starting (x, y) and color format
126 4. var->nonstd is used to pass starting (x, y) position and color format,
141 XPOS - starting horizontal position
142 YPOS - starting vertical position
Dviafb.txt210 provide a good starting point to figure out which of those names match
Dintel810.txt154 to finish before starting another instruction. This will produce a
Dapi.txt290 despite starting with the V4L2_PIX_FMT_prefix, they are not restricted to V4L2
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,orion-intc.txt7 - reg: base address(es) of interrupt registers starting with CAUSE register
30 - reg: base address of bridge interrupt registers starting with CAUSE register
Dsnps,dw-apb-ictl.txt10 region starting with ENABLE_LOW register
Darm,vic.txt22 represents single interrupt source, starting from source 0 at LSb and ending
Dst,spear3xx-shirq.txt26 (starting from 0) of interrupts for all the groups.
Dbrcm,bcm7120-l2-intc.txt5 platforms. It can be found on BCM7xxx products starting with BCM7120.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dti-omap.txt15 instance starting 1
42 instance starting 1
Dti-omap-hsmmc.txt16 - ti,hwmods: Must be "mmc<n>", n is controller instance starting 1
/linux-4.4.14/Documentation/acpi/
Dgpio-properties.txt43 index - Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
75 GpioIo()/GpioInt() resource in _CRS starting from zero, the index of the target
76 line in that resource starting from zero, and the active-low flag for that line,
Dnamespace.txt87 4. Names starting with '_' are reserved by the ACPI specification.
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dmarvell,orion-timer.txt5 - reg: base address of the timer register starting with TIMERS CONTROL register
Drockchip,rk3288-timer.txt5 - reg: base address of the timer register starting with TIMERS CONTROL register
/linux-4.4.14/Documentation/virtual/kvm/devices/
Dxics.txt21 state word has the following bitfields, starting at the
43 bitfields, starting from the least-significant end of the word:
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt9 Each user-defined region specifies a starting sector, length and step.
50 starting with <start_sector>.
137 The index of the starting line in the output.
180 The index of the starting line in the output.
Dkcopyd.txt17 block-device along with the starting sector and size of the region. The source
Ddm-io.txt9 of the I/O. Each io_region indicates a block-device along with the starting
Dverity.txt141 (starting from the root), sorted in order of increasing index.
/linux-4.4.14/Documentation/serial/
Drocket.txt59 starting at zero (ex. /dev/ttyR0, /devttyR1, ...). If you have multiple cards
71 "mknod /dev/ttyRx c 46 x" where x is the port number starting at zero. For example:
97 requires a 68-byte contiguous block of I/O addresses, starting at one
103 contiguous block of I/O addresses, starting at one of the following
Dn_gsm.txt21 (a good starting point is util-linux-ng/sys-utils/ldattach.c)
65 for example GPS), starting with minor 1 (DLC0 is reserved for the management
/linux-4.4.14/kernel/configs/
Dxen.config16 # pretty useless systems starting from allnoconfig
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-timer.txt14 - interrupts: one interrupt per timer in the group, in order, starting
Dsrio.txt40 the controller. The ports are numbered starting at one (1) and should have
/linux-4.4.14/Documentation/devicetree/bindings/input/
Datmel,maxtouch.txt17 starting at the LSB. Linux keycodes are defined in
/linux-4.4.14/Documentation/usb/
Dfunctionfs.txt18 only one (endpoints and strings numbers starting from one and
19 interface numbers starting from zero). The FunctionFS changes
DCREDITS30 Inaky Perez Gonzalez <inaky@peloncho.fis.ucm.es> for starting the
133 - Alberto Menegazzi <flash@flash.iol.it> is starting the
170 - Linus Torvalds, for starting, developing and managing Linux.
Dgadget_printer.txt54 start numbering your products starting with say 0x0001.
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm11351-cpu-method.txt3 This binding defines the enable method used for starting secondary
/linux-4.4.14/scripts/
Ddecodecode84 echo Code starting with the faulting instruction > $T.aa
DKbuild.include239 # Replace >#< with >\#< to avoid starting a comment in the .cmd file
/linux-4.4.14/Documentation/devicetree/bindings/leds/backlight/
Dpwm-backlight.txt7 are in the range from 0 to 255, but any range starting at 0 will do.
/linux-4.4.14/arch/powerpc/boot/dts/
Dcurrituck.dts141 /* Inbound starting at 0 to memsize filled in by zImage */
178 /* Inbound starting at 0 to memsize filled in by zImage */
215 /* Inbound starting at 0 to memsize filled in by zImage */
Dakebono.dts267 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
307 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
347 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
387 /* Inbound starting at 0x0 to 0x40000000000. In order to use MSI
Dkatmai.dts297 /* Inbound 4GB range starting at 0 */
341 /* Inbound 4GB range starting at 0 */
382 /* Inbound 4GB range starting at 0 */
423 /* Inbound 4GB range starting at 0 */
Dredwood.dts257 /* Inbound 2GB range starting at 0 */
298 /* Inbound 2GB range starting at 0 */
339 /* Inbound 2GB range starting at 0 */
Dicon.dts307 /* Inbound 4GB range starting at 0 */
337 /* Inbound 4GB range starting at 0 */
378 /* Inbound 4GB range starting at 0 */
Dmakalu.dts290 /* Inbound 2GB range starting at 0 */
331 /* Inbound 2GB range starting at 0 */
Dcanyonlands.dts444 /* Inbound 2GB range starting at 0 */
475 /* Inbound 2GB range starting at 0 */
517 /* Inbound 2GB range starting at 0 */
Dglacier.dts481 /* Inbound 2GB range starting at 0 */
512 /* Inbound 2GB range starting at 0 */
554 /* Inbound 2GB range starting at 0 */
Dep405.dts215 /* Inbound 2GB range starting at 0 */
Dkilauea.dts344 /* Inbound 2GB range starting at 0 */
385 /* Inbound 2GB range starting at 0 */
Dwalnut.dts222 /* Inbound 2GB range starting at 0 */
Dhotfoot.dts276 /* Inbound 2GB range starting at 0 */
Dsam440ep.dts285 /* Inbound 2GB range starting at 0 */
Dhaleakala.dts259 /* Inbound 2GB range starting at 0 */
Dbamboo.dts276 /* Inbound 2GB range starting at 0 */
Debony.dts313 /* Inbound 2GB range starting at 0 */
Dyosemite.dts318 /* Inbound 2GB range starting at 0 */
Drainier.dts337 /* Inbound 2GB range starting at 0 */
Dsequoia.dts399 /* Inbound 2GB range starting at 0 */
Dbluestone.dts363 /* Inbound 2GB range starting at 0 */
Dtaishan.dts404 /* Inbound 2GB range starting at 0 */
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dst,stm32-rcc.txt32 The secondary index is the bit number within the RCC register bank, starting
Dsamsung,s3c2443-clock.txt5 the s3c24x family starting with the s3c2443.
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dti,tas5086.txt17 waits for this period of time before starting the
Ddavinci-mcasp-audio.txt30 - ti,hwmods : Must be "mcasp<n>", n is controller instance starting 0
/linux-4.4.14/Documentation/fmc/
Dfmc-write-eeprom.txt23 * If the file name ends with `.bin' it is written verbatim starting
59 the image starting at offset 0, it will deregister and register again
Dfmc-fakedev.txt34 own internal fake EEPROM: whenever the image is overwritten starting at
Dcarrier.txt82 * slot_id: the index of this slot (starting from zero).
272 All carriers must map their I/O lines to the sets above starting from
Didentifiers.txt123 example that you may want to use as a starting point (the comments are
/linux-4.4.14/Documentation/
Drobust-futex-ABI.txt71 Each 'lock entry' on the single linked list starting at 'head' consists
109 By keeping its locks linked this way, on a list starting with a 'head'
142 of the 'lock word', to the linked list starting at 'head', and
154 the list starting at 'head'. For each such address, if the bottom 29
Ddell_rbu.txt12 the BIOS on Dell servers (starting from servers sold since 1999), desktops
13 and notebooks (starting from those sold in 2005).
Dunaligned-memory-access.txt13 Unaligned memory accesses occur when you try to read N bytes of data starting
85 starting at address 0x10000. With a basic level of understanding, it would
161 2 bytes (16 bits) to be read from memory starting at address addr1.
Dlzo.txt37 Lengths are always encoded on a variable size starting with a small number
58 are copied before starting the next instruction. The number of literals that
Dfutex-requeue-pi.txt94 starting to run. This is especially true in the uncontended case.
Dmedia-framework.txt237 reached only through enabled links starting at a given entity. The media
321 When starting streaming, drivers must notify all entities in the pipeline to
Dmd-cluster.txt45 Each node has to communicate with other nodes when starting or ending
Dstable_kernel_rules.txt101 For each "-stable" tree starting with the specified version.
Dunicode.txt38 Linux we call it the "Linux Zone"). U+F000 was picked as the starting
Dmd.txt237 array creation it will default to 0, though starting the array as
401 starting the array. It sets or clears the flag.
476 where 'NN' is the position in the array, starting from 0.
Dkmemleak.txt89 2. scan the memory starting with the data section and stacks, checking
Dvfio.txt205 dma_map.iova = 0; /* 1MB starting at 0x0 from device view */
354 dma_map.iova = 0; /* 1MB starting at 0x0 from device view */
Dkobject.txt12 abstraction upon which it is built - is that there is no obvious starting
15 easier, we'll take a multi-pass approach, starting with vague terms and
Dsysfs-rules.txt50 /sys, and always starting with a slash
Dcrc32.txt180 similar solution is used. Instead of starting the CRC computation with
Dintel_txt.txt62 starting at system reset and requires measurement of all code
/linux-4.4.14/drivers/usb/misc/sisusbvga/
DKconfig30 the first and last consoles (starting at 1) as driver parameters.
/linux-4.4.14/tools/perf/Documentation/
Dperf-sched.txt27 via perf sched record. (this is done by starting up mockup threads
Dperf-stat.txt162 After starting the program, wait msecs before measuring. This is useful to
Dperf-record.txt278 After starting the program, wait msecs before measuring. This is useful to
/linux-4.4.14/Documentation/ABI/testing/
Ddev-kmsg74 A line starting with ' ', is a continuation line, adding
84 30,340,5690716,-;udevd[80]: starting version 181
Dsysfs-class-extcon53 state number starting with 0x:
Dsysfs-bus-fcoe66 Notes: ctlr_X (global increment starting at 0)
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dbrcm,kona-gpio.txt19 starting with bank 0. There is always a 1:1 mapping between banks and
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dxgene-pci-msi.txt12 - interrupts: A list of 16 interrupt outputs of the controller, starting from
/linux-4.4.14/Documentation/locking/
Dlocktorture.txt62 torture_runnable to be set via sysfs before starting.
80 onoff_holdoff The number of seconds to wait until starting CPU-hotplug
Dww-mutex-design.txt48 acquired when starting the lock acquisition. This ticket is stored in the
214 a graph from a starting point and then iteratively discovering new edges and
219 as a starting point).
230 list of starting nodes (passed in from userspace) using one of the above
/linux-4.4.14/Documentation/sound/oss/
DVIBRA1613 A good starting point is that the vibra16x chip full-duplex facility
DREADME.OSS97 or before even starting to do any work. Tell me what you suggest to be
368 before starting Linux.
691 card to work by booting DOS before starting Linux (boot DOS, hit ctrl-alt-del
739 (later in this file) before starting to configure. Some cards must be
1028 DOS or isapnptools before starting the driver.
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dpwm-samsung.txt20 - interrupts: list of timer interrupts (one interrupt per timer, starting at
/linux-4.4.14/Documentation/hid/
Dhidraw.txt108 reports, set the first byte to 0. The report will be returned starting at
115 purpose, and can serve as a starting point for developing applications using
Dhiddev.txt33 with the minor numbers starting at 96 and finishing at 111. Therefore,
/linux-4.4.14/Documentation/cris/
DREADME138 Telnetd starting, using port 23.
140 sftpd[15]: sftpd $Revision: 1.7 $ starting up
/linux-4.4.14/arch/alpha/lib/
Dmemchr.S70 or $7, $6, $1 # .. e1 : $1 = quadword starting at $16
Dev6-memchr.S69 or $7, $6, $1 # E : L U L U $1 = quadword starting at $16
/linux-4.4.14/sound/pci/
Dsis7019.c599 int starting; in sis_pcm_trigger() local
611 starting = 1; in sis_pcm_trigger()
616 starting = 0; in sis_pcm_trigger()
643 if (starting) { in sis_pcm_trigger()
/linux-4.4.14/Documentation/w1/slaves/
Dw1_therm59 representing the device index in the bus starting at 0.
/linux-4.4.14/Documentation/video4linux/
Dcpia2_overview.txt37 used by VP4 to load a firmware patch. It contains a starting address and
Dfimc.txt117 starting streaming):
Dvideobuf258 complex, of course, since they will also need to deal with starting and
317 - the one which is filled in the buf_queue() callback. Because starting
DZoran289 LML33 tolerable. Buz starting to get annoying (6-10 frames/hour)
295 LML33 starting to get annoying, Buz poor enough that I have up.
/linux-4.4.14/Documentation/misc-devices/
Dmax687596 To read data starting at offset 0x8100, first set the address:
/linux-4.4.14/tools/build/
DBuild.include46 # Replace >#< with >\#< to avoid starting a comment in the .cmd file
/linux-4.4.14/Documentation/filesystems/
Dpath-lookup.txt6 will be resolved. Paths are resolved by walking the namespace tree, starting
30 are path-walk intensive tend to do path lookups starting from a common dentry
49 the path given by the name's starting point (which we know in advance -- eg.
292 * Take the RCU lock for the entire path walk, starting with the acquiring
293 of the starting path (eg. root/cwd/fd-path). So now dentry refcounts are
Dqnx6.txt107 starting with the superblock longfilename root node pointers.
130 limited to 510 bytes. The first two starting bytes are used as length field
Dvfat.txt246 unsigned char start[2]; // starting cluster number
281 unsigned char start[2]; // starting cluster number
297 2) The starting cluster is always set to 0, an impossible
Dgfs2-glocks.txt132 should have, as far as possible, a sensible starting point.
/linux-4.4.14/arch/m68k/ifpsp060/
Disp.doc96 the address of the corresponding function RELATIVE to the starting address
114 (_060ISP_TOP is the starting address of the "Call-out" section; the "Call-out"
Dfpsp.doc88 the address of the corresponding function RELATIVE to the starting address
105 (_060FPSP_TOP is the starting address of the "Call-out" section; the "Call-out"
DTEST.DOC83 the starting address of the "call-out" section. The "Call-out" section must
100 (_060ISP_TEST is the starting address of the "Call-out" section; the "Call-out"
/linux-4.4.14/fs/
DKconfig.binfmt69 tristate "Kernel support for scripts starting with #!"
72 Say Y here if you want to execute interpreted scripts starting with
/linux-4.4.14/Documentation/networking/
Ddecnet.txt34 o Set the MAC address on your ethernet card before starting _any_ other
93 of your ethernet card to an address starting with "hi-ord" will cause a
156 - Try starting a simple server and client, like the dnping/dnmirror
Dspider_net.txt78 of the ring, starting at the tail pointer, and listing the status
95 The "Have nnn decrs" refers to the descr starting at the tail: in this
96 case, nnn=1 descr, starting at descr 20. The "Last nnn descrs" refers
Dlapb-module.txt158 LAPB_OK LAPB is starting to connect.
167 LAPB_OK LAPB is starting to disconnect.
Dradiotap-headers.txt58 byte isn't defined. So even if the whole radiotap header is starting at, eg,
Dltpc.txt33 Before starting up the netatalk demons (perhaps in rc.local), you
Dray_cs.txt45 when starting. Create the file /etc/pcmcia/ray_cs.opts containing the
Dfib_trie.txt126 starting out at the same as the key length, is reduced one step at a time,
D6pack.txt116 - Do a spattach as you would launch kissattach when starting a KISS port.
De1000e.txt122 systems and is a good starting point, but the optimal value will
Dcxgb.txt175 the correct value. This method is provided as a starting point for the
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS51 Disable backing store by starting X with the option "-bs"
DREADME.quirks78 transaction from starting the same cycle as GNT is de-asserted. This
/linux-4.4.14/Documentation/development-process/
D8.Conclusion6 file is an important starting point; SubmittingPatches and
D7.AdvancedTopics52 (Github, for example) are starting to appear on the net. Established
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/
Dqcom,spmi-vadc.txt78 Definition: Time between AMUX getting configured and the ADC starting
/linux-4.4.14/fs/ntfs/
DKconfig16 the old NTFS code starting with Linux 2.5.11. A backport to
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dmsm-hsusb.txt78 before starting controller using usbcmd run/stop bit.
/linux-4.4.14/arch/mn10300/mm/
Dcache-inv-by-tag.S159 add d0,a0 # starting dcache tag RAM
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-server-gss.txt89 before starting nfsd. Whoever starts nfsd can guarantee this by reading
Dknfsd-stats.txt39 Thread pool ids are a contiguous set of small integers starting
DExporting8 All filesystem operations require a dentry (or two) as a starting
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt41 starting with Release 6.0) over HTTP/S or WS-Management protocol over
179 over HTTP (deprecated starting with Release 6.0) or with WS-Management over
/linux-4.4.14/tools/power/cpupower/bench/
DREADME-BENCH113 -c, --cpu=<unsigned int> CPU Number to use, starting at 0
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-memory.txt40 The registers occupy the 64k space starting at the 0x02000000 offset from BAR0.
Dfw-decoder-regs.txt351 the image on screen. Known starting values are 0x011E0017 (NTSC) &
380 the image on screen. Known starting values are 0x011E0017 (NTSC) &
/linux-4.4.14/Documentation/filesystems/caching/
Dobject.txt174 Look up the object on disk, using the parent as a starting point.
192 Create an object on disk, using the parent as a starting point. This
/linux-4.4.14/Documentation/scheduler/
Dsched-domains.txt36 our CPU is on, starting from its base domain and going up the ->parent chain.
/linux-4.4.14/
DREADME380 just 'grep' the list: the list will, however, give you the starting
382 has a starting address lower than the one you are searching for but
403 disregards the starting offset for which the kernel is compiled.
/linux-4.4.14/Documentation/hwmon/
Dsubmitting-patches115 before starting to write a new driver. Especially for temperature sensors,
Dsysfs-interface70 [0-*] denotes any positive number starting from 0
71 [1-*] denotes any positive number starting from 1
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcci.txt120 starting with the cycle counter overflow
Dtopology.txt91 sequential N value, starting from 0).
/linux-4.4.14/Documentation/input/
Dyealink.txt212 - Olivier Vandorpe, for starting the usbb2k-api project doing much of
Dgameport-programming.txt19 choose which one to program the hardware to, starting from the more exotic
/linux-4.4.14/Documentation/devicetree/
Dusage-model.txt116 The 'compatible' property contains a sorted list of strings starting
355 parameters are all NULL because when starting from the root of the
356 tree, there is no need to provide a starting node (the first NULL), a
/linux-4.4.14/Documentation/laptops/
Dsony-laptop.txt79 /sys/class/rfkill. Check those starting with sony-* in
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dhead.S162 ; Check if starting from DRAM (network->RAM boot or unpacked
/linux-4.4.14/Documentation/gpio/
Dsysfs.txt100 controller implementing GPIOs starting at #42) and have the following
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Diommu.txt179 /* master ID 42, 4 GiB DMA window starting at 0 */
/linux-4.4.14/Documentation/vm/
Didle_page_tracking.txt36 -EINVAL if you are not starting the read/write on an 8-byte boundary, or
Duserfaultfd.txt101 just before starting postcopy live migration, in order to avoid
Dpagemap.txt176 Reading from any of the files will return -EINVAL if you are not starting
Dslub.txt188 This will be a message in the system log starting with
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt105 expressed as an offset from the region's starting address. This allows
114 contains a version, details about the starting offset and size of the
/linux-4.4.14/Documentation/block/
Dbiovecs.txt67 arbitrary range of an existing biovec, both starting and ending midway
/linux-4.4.14/Documentation/ia64/
Dserial.txt7 starting after the ACPI devices.
Dmca.txt63 * The starting point for the unwind depends on whether a task is
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt83 monitor upto 32 queues starting at the base queue #.
/linux-4.4.14/arch/sh/mm/
DKconfig52 map the ROM starting at address zero. But the processor
/linux-4.4.14/drivers/net/
DKconfig128 iproute2 package starting with the iproute2-2.6.23 release:
160 iproute2 package starting with the iproute2-3.19 release:
/linux-4.4.14/Documentation/virtual/kvm/
Dnested-vmx.txt68 but the goal is to eventually support them all, starting with the VMX features
Dapi.txt746 page, and provides the starting address and size of the hypercall
945 Memory for the region is taken starting at the address denoted by the
1813 the vcpu's address space starting at "vcpu_addr". All parameters need to
1832 This ioctl unmaps the memory in the vcpu's address space starting at
2466 Writes to the fd create HPT entries starting at the index given in the
2870 The count field is the number of consecutive frames (starting from start_gfn)
2893 The count field is the number of consecutive frames (starting from start_gfn)
2900 single frame starting at start_gfn for count frames.
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-tpm54 any longer than necessary before starting to poll for a
/linux-4.4.14/Documentation/scsi/
Dscsi-changer.txt51 other linux SCSI device drivers as starting point. The interface
Daic79xx.txt254 Definition: Probe the scsi bus in reverse order, starting
405 * Luns that are not numbered contiguously starting with 0 might not
Din2000.txt178 In later ROMs (starting with 01.3 in April 1994) sw1-8 controls
/linux-4.4.14/arch/metag/
DKconfig200 (starting from HTP265).
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt28 of resuming devices (that is, before starting to execute ->resume_early
Dsuspend-and-cpuhotplug.txt103 beginning, when we are just starting out to suspend, and then released only
Dbasic-pm-debugging.txt97 should try the test modes starting from "freezer", through "devices", "platform"
/linux-4.4.14/Documentation/security/
Dkeys-request-key.txt155 firstly calls key_permission(SEARCH) on the keyring it's starting with,
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dvideo-interfaces.txt109 - lane-polarities: an array of polarities of the lanes starting from the clock
/linux-4.4.14/Documentation/m68k/
DREADME.buddha84 while starting up. If interrupts would
/linux-4.4.14/Documentation/thermal/
Dsysfs-api.txt28 [0-*] denotes any positive number starting from 0
29 [1-*] denotes any positive number starting from 1
/linux-4.4.14/Documentation/s390/
Dmonreader.txt49 Your guest virtual storage has to end below the starting address of the DCSS
D3270.txt187 driver writes terminal output to it, starting at the top line and going
/linux-4.4.14/arch/parisc/kernel/
Dperf_asm.S44 ; starting/stopping the coprocessor with the pmenb/pmdis.
/linux-4.4.14/sound/oss/
DKconfig302 Enter the full pathname of your TRXPRO.HEX file, starting from /.
411 starting from /.
/linux-4.4.14/kernel/trace/
DKconfig222 to be scheduled in, starting from the point it has woken up.
536 as it will write garbage to IO memory starting at a given address.
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt325 are being copied around so much but a starting point would be to take an
/linux-4.4.14/drivers/staging/panel/
DKconfig71 The driver includes an interpreter for escape codes starting with
/linux-4.4.14/arch/arm/boot/dts/
Dtegra30-cardhu.dtsi6 * There is multiple fab version of Cardhu starting from A01 to A07.
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt12 This function verified that the memory area starting at address
/linux-4.4.14/Documentation/i2c/
Dinstantiating-devices220 hexadecimal starting with 0x, but can also be expressed in decimal.)
/linux-4.4.14/Documentation/ioctl/
Dhdio.txt102 start starting sector of this partition.
394 Nice flags are listed in <linux/hdreg.h>, starting with
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-cd.1994-20043 * 1.01 Nov 2, 1994 -- Fixed problem with starting request in
DChangeLog.ide-tape.1995-200216 * popular tape utilities are starting to work with
/linux-4.4.14/Documentation/arm64/
Dbooting.txt54 the 512 MB region starting at text_offset bytes below the kernel Image.
/linux-4.4.14/Documentation/RCU/
DwhatisRCU.txt31 People who prefer starting with a conceptual overview should focus on
68 during the removal phase need be considered, because any reader starting
565 a good starting point.
/linux-4.4.14/drivers/usb/dwc3/
Dgadget.c863 static void dwc3_prepare_trbs(struct dwc3_ep *dep, bool starting) in dwc3_prepare_trbs() argument
888 if (!starting) in dwc3_prepare_trbs()
/linux-4.4.14/arch/xtensa/
DKconfig229 lowermost 128 MB of memory linearly to the areas starting

12