Home
last modified time | relevance | path

Searched refs:detail (Results 1 – 133 of 133) sorted by relevance

/linux-4.4.14/net/sunrpc/
Dcache.c44 static void cache_init(struct cache_head *h, struct cache_detail *detail) in cache_init() argument
51 if (now <= detail->flush_time) in cache_init()
53 now = detail->flush_time + 1; in cache_init()
57 struct cache_head *sunrpc_cache_lookup(struct cache_detail *detail, in sunrpc_cache_lookup() argument
63 head = &detail->hash_table[hash]; in sunrpc_cache_lookup()
65 read_lock(&detail->hash_lock); in sunrpc_cache_lookup()
68 if (detail->match(tmp, key)) { in sunrpc_cache_lookup()
69 if (cache_is_expired(detail, tmp)) in sunrpc_cache_lookup()
73 read_unlock(&detail->hash_lock); in sunrpc_cache_lookup()
77 read_unlock(&detail->hash_lock); in sunrpc_cache_lookup()
[all …]
/linux-4.4.14/drivers/net/usb/
Dzaurus.c153 struct usb_cdc_mdlm_detail_desc *detail = NULL; in blan_mdlm_bind() local
183 if (detail) { in blan_mdlm_bind()
187 detail = (void *) buf; in blan_mdlm_bind()
188 switch (detail->bGuidDescriptorType) { in blan_mdlm_bind()
190 if (detail->bLength != (sizeof *detail + 2)) in blan_mdlm_bind()
194 if (detail->bLength != (sizeof *detail + 3)) in blan_mdlm_bind()
214 if ((detail->bDetailData[1] & ~0x02) != 0x01) { in blan_mdlm_bind()
221 detail->bLength, in blan_mdlm_bind()
222 detail->bDetailData[0], in blan_mdlm_bind()
223 detail->bDetailData[2]); in blan_mdlm_bind()
[all …]
Dusbnet.c1978 struct usb_cdc_mdlm_detail_desc *detail = NULL; in cdc_parse_cdc_header() local
2056 if (detail) in cdc_parse_cdc_header()
2058 detail = (struct usb_cdc_mdlm_detail_desc *)buffer; in cdc_parse_cdc_header()
2096 hdr->usb_cdc_mdlm_detail_desc = detail; in cdc_parse_cdc_header()
/linux-4.4.14/include/linux/sunrpc/
Dcache.h182 sunrpc_cache_lookup(struct cache_detail *detail,
185 sunrpc_cache_update(struct cache_detail *detail,
189 sunrpc_cache_pipe_upcall(struct cache_detail *detail, struct cache_head *h);
209 static inline int cache_is_expired(struct cache_detail *detail, struct cache_head *h) in cache_is_expired() argument
212 (detail->flush_time >= h->last_refresh); in cache_is_expired()
215 extern int cache_check(struct cache_detail *detail,
218 extern void cache_purge(struct cache_detail *detail);
/linux-4.4.14/drivers/mmc/host/
Dtoshsd.c295 u32 int_reg, int_mask, int_status, detail; in toshsd_irq() local
332 detail = ioread32(host->ioaddr + SD_ERRORSTATUS0); in toshsd_irq()
334 detail & SD_ERR0_RESP_CMD_ERR ? "RESP_CMD " : "", in toshsd_irq()
335 detail & SD_ERR0_RESP_NON_CMD12_END_BIT_ERR ? "RESP_END_BIT " : "", in toshsd_irq()
336 detail & SD_ERR0_RESP_CMD12_END_BIT_ERR ? "RESP_END_BIT " : "", in toshsd_irq()
337 detail & SD_ERR0_READ_DATA_END_BIT_ERR ? "READ_DATA_END_BIT " : "", in toshsd_irq()
338 detail & SD_ERR0_WRITE_CRC_STATUS_END_BIT_ERR ? "WRITE_CMD_END_BIT " : "", in toshsd_irq()
339 detail & SD_ERR0_RESP_NON_CMD12_CRC_ERR ? "RESP_CRC " : "", in toshsd_irq()
340 detail & SD_ERR0_RESP_CMD12_CRC_ERR ? "RESP_CRC " : "", in toshsd_irq()
341 detail & SD_ERR0_READ_DATA_CRC_ERR ? "READ_DATA_CRC " : "", in toshsd_irq()
[all …]
/linux-4.4.14/tools/testing/selftests/powerpc/
Dsubunit.h14 static inline void test_failure_detail(char *name, char *detail) in test_failure_detail() argument
16 printf("failure: %s [%s]\n", name, detail); in test_failure_detail()
/linux-4.4.14/drivers/edac/
Dedac_mc.c990 const char *detail, in edac_ce_error() argument
1008 location, detail, other_detail); in edac_ce_error()
1013 location, detail); in edac_ce_error()
1044 const char *detail, in edac_ue_error() argument
1058 location, detail, other_detail); in edac_ue_error()
1063 location, detail); in edac_ue_error()
1069 msg, msg_aux, label, location, detail, other_detail); in edac_ue_error()
1072 msg, msg_aux, label, location, detail); in edac_ue_error()
1094 char detail[80]; in edac_raw_mc_handle_error() local
1099 snprintf(detail, sizeof(detail), in edac_raw_mc_handle_error()
[all …]
Di5100_edac.c445 char detail[80]; in i5100_handle_ce() local
448 snprintf(detail, sizeof(detail), in i5100_handle_ce()
455 msg, detail); in i5100_handle_ce()
467 char detail[80]; in i5100_handle_ue() local
470 snprintf(detail, sizeof(detail), in i5100_handle_ue()
477 msg, detail); in i5100_handle_ue()
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Drenesas,rsnd.txt19 see below for detail.
22 see below for detail.
25 see below for detail.
28 see below for detail.
31 see below for detail.
34 see below for detail.
/linux-4.4.14/fs/nfsd/
Dnfs4idmap.c169 warn_no_idmapd(struct cache_detail *detail, int has_died) in warn_no_idmapd() argument
493 struct ent *key, struct cache_detail *detail, struct ent **item) in idmap_lookup() argument
497 *item = lookup_fn(detail, key); in idmap_lookup()
501 ret = cache_check(detail, &(*item)->h, &rqstp->rq_chandle); in idmap_lookup()
505 *item = lookup_fn(detail, key); in idmap_lookup()
508 cache_put(&(*item)->h, detail); in idmap_lookup()
DKconfig21 package, available from http://linux-nfs.org/. More detail about
/linux-4.4.14/Documentation/acpi/
Ddsdt-override.txt5 When to use this method is described in detail on the
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Darm-versatile.txt8 address space. See partition.txt for more detail.
Datmel-dataflash.txt7 address space. See partition.txt for more detail.
Ddenali-nand.txt11 address space. See partition.txt for more detail.
Dflctl-nand.txt18 address space. See partition.txt for more detail.
Dorion-nand.txt16 address space. See partition.txt for more detail.
Dhisi504-nand.txt25 the address space. See partition.txt for more detail.
Dfsl-upm-nand.txt24 detail.
Dgpio-control-nand.txt29 address space. See partition.txt for more detail.
Dgpmi-nand.txt40 address space. See partition.txt for more detail.
Ddavinci-nand.txt71 the address space. See partition.txt for more detail. The NAND Flash timing
Dmtd-physmap.txt45 address space. See partition.txt for more detail.
Dbrcm,brcmnand.txt114 partition mapping. See partition.txt for more detail.
/linux-4.4.14/drivers/md/
Ddm-cache-target.c1679 struct inc_detail *detail = context; in inc_fn() local
1680 struct cache *cache = detail->cache; in inc_fn()
1684 detail->any_writes = true; in inc_fn()
1688 bio_list_add(&detail->unhandled_bios, bio); in inc_fn()
1693 detail->any_writes = true; in inc_fn()
1695 bio_list_add(&detail->bios_for_issue, bio); in inc_fn()
1707 struct inc_detail detail; in remap_cell_to_origin_clear_discard() local
1709 detail.cache = cache; in remap_cell_to_origin_clear_discard()
1710 bio_list_init(&detail.bios_for_issue); in remap_cell_to_origin_clear_discard()
1711 bio_list_init(&detail.unhandled_bios); in remap_cell_to_origin_clear_discard()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dssd1289fb.txt6 - reg: Should contain address of the controller on the LBC bus. The detail
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dspear13xx-pcie.txt1 SPEAr13XX PCIe DT detail:
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Dfsl-imx-wdt.txt11 detail please see: Documentation/devicetree/bindings/regmap/regmap.txt.
/linux-4.4.14/lib/
Dlru_cache.c653 void (*detail) (struct seq_file *, struct lc_element *)) in lc_seq_dump_details()
668 if (detail) in lc_seq_dump_details()
669 detail(seq, e); in lc_seq_dump_details()
/linux-4.4.14/include/linux/
Dlru_cache.h270 void (*detail) (struct seq_file *, struct lc_element *));
/linux-4.4.14/drivers/pci/hotplug/
Dacpiphp_ibm.c254 u8 detail = event & 0x0f; in ibm_handle_events() local
264 note->event, detail); in ibm_handle_events()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-fpga-manager12 The intent is to provide enough detail that if something goes
Dsysfs-driver-ppi9 'find /sys/ -name 'pcrs''. For the detail information of PPI,
Dsysfs-class-regulator58 imply "on", but provide more detail.
/linux-4.4.14/Documentation/hwmon/
Dlm7727 This implementation detail implies the following:
Demc140348 This implementation detail implies the following:
/linux-4.4.14/Documentation/networking/
Ddctcp.txt23 The algorithm is further described in detail in the following two
Dbatman-adv.txt141 times necessary to see more detail debug messages. This must be
Dlapb-module.txt48 be described in detail below. If a callback is not required (!!) then a NULL
Dnetdev-FAQ.txt212 A: Attention to detail. Re-read your own work as if you were the
Dopenvswitch.txt65 the following sections go into detail.
DLICENSE.qlcnic249 be similar in spirit to the present version, but may differ in detail to
DLICENSE.qlge249 be similar in spirit to the present version, but may differ in detail to
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Dspi-fsl-dspi.txt17 detail please see: Documentation/devicetree/bindings/regmap/regmap.txt.
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt33 For more detail about files under nfsd/ and what they control, see
/linux-4.4.14/Documentation/video4linux/
Domap4_camera.txt17 As of Revision AB, the ISS is described in detail in section 8.
Dsi476x.txt100 | | (see datasheet for more detail)
Duvcvideo.txt31 Both mechanisms complement each other and are described in more detail below.
Dvivid.txt38 These features will be described in more detail below.
259 input, one input for each input type. Those are described in more detail
376 HDMI input, one output for each output type. Those are described in more detail
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dpwm-fsl-ftm.txt14 Please see ../regmap/regmap.txt for more detail about how to specify endian
/linux-4.4.14/Documentation/mtd/
Dspi-nor.txt61 drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to fsl-quadspi.c
/linux-4.4.14/Documentation/development-process/
D5.Posting8 document will attempt to cover these expectations in reasonable detail;
150 the author of the patch. Tags will be described in more detail below.
173 changed, detail those changes and how other developers should respond. In
192 detail in the SubmittingPatches document; what follows here is a brief
214 detail.
236 be examined in any detail. If there is any doubt at all, mail the patch
D8.Conclusion14 Various web sites discuss kernel development at all levels of detail. Your
D1.Intro136 discussed in greater detail later in this document. Consider:
D2.Process42 detail later on).
/linux-4.4.14/drivers/scsi/
Ddpt_i2o.c391 sprintf(pHba->detail, "Adaptec I2O RAID"); in adpt_inquiry()
396 memset(pHba->detail, 0, sizeof(pHba->detail)); in adpt_inquiry()
397 memcpy(&(pHba->detail), "Vendor: Adaptec ", 16); in adpt_inquiry()
398 memcpy(&(pHba->detail[16]), " Model: ", 8); in adpt_inquiry()
399 memcpy(&(pHba->detail[24]), (u8*) &buf[16], 16); in adpt_inquiry()
400 memcpy(&(pHba->detail[40]), " FW: ", 4); in adpt_inquiry()
401 memcpy(&(pHba->detail[44]), (u8*) &buf[32], 4); in adpt_inquiry()
402 pHba->detail[48] = '\0'; /* precautionary */ in adpt_inquiry()
540 return (char *) (pHba->detail); in adpt_info()
565 seq_printf(m, "%s\n", pHba->detail); in adpt_show_info()
Ddpti.h218 char detail[55]; member
/linux-4.4.14/tools/perf/Documentation/
Dperf-probe.txt61 Define a probe event (see PROBE SYNTAX for detail).
75 which specifies a range of the source code. (see LINE SYNTAX for detail)
98 pattern, see FILTER PATTERN for detail.
Dperf-script-python.txt83 general-purpose scripts to drill down and get more detail about
/linux-4.4.14/Documentation/devicetree/bindings/nios2/
Dnios2.txt7 Qsys system. See more detail in: http://www.alterawiki.com/wiki/Sopc2dts
/linux-4.4.14/Documentation/leds/
Dleds-lm3556.txt51 Please refer datasheet for more detail about N-Blank, Pulse time and N Period.
/linux-4.4.14/Documentation/block/
Dstat.txt19 following table, and described in more detail below.
Dqueue-sysfs.txt4 This text file will detail the queue files that are located in the sysfs tree
Ddata-integrity.txt96 However, this level of detail is required when preparing the
Dbiodoc.txt58 2.2 The bio struct in detail (multi-page io unit)
/linux-4.4.14/drivers/net/can/sja1000/
DKconfig97 http://www.embeddedarm.com/products/board-detail.php?product=TS-CAN1
/linux-4.4.14/Documentation/vm/
Dpage_owner.txt51 There is one notice that is caused by implementation detail. page owner
/linux-4.4.14/Documentation/accounting/
Ddelay-accounting.txt38 in detail in a separate document in this directory. Taskstats returns a
Dtaskstats.txt39 explained in more detail below.
/linux-4.4.14/Documentation/w1/masters/
Dds249047 detail, but my observation is if fewer bytes are requested than are
/linux-4.4.14/Documentation/cpu-freq/
Dcpufreq-stats.txt32 cpufreq stats provides following statistics (explained in detail below).
/linux-4.4.14/Documentation/scheduler/
Dsched-design-CFS.txt35 [ small detail: on "ideal" hardware, at any time all tasks would have the same
89 other HZ detail. Thus the CFS scheduler has no notion of "timeslices" in the
Dsched-bwc.txt43 more detail below.
/linux-4.4.14/Documentation/scsi/
DChangeLog.arcmsr50 ** and detail description
Dlibsas.txt383 All this process is shown in detail in the function do_smp_func()
DLICENSE.qla4xxx250 be similar in spirit to the present version, but may differ in detail to
DLICENSE.qla2xxx251 be similar in spirit to the present version, but may differ in detail to
DChangeLog.megaraid_sas48 4. Free event detail memory without device ID check.
Dscsi_mid_low_api.txt735 In some cases more detail is given in scsi_host.h than below.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio-rmu.txt37 SoC will detail which and how many of these sub-controllers are implemented.
/linux-4.4.14/Documentation/s390/
D3270.txt73 Here are the installation steps in detail:
130 Here are the testing steps in detail:
Dcds.txt25 every detail.This information can be obtained from the ESA/390 Principles of
DDebugging390.txt13 390 IO in any detail. It is intended to complement the documents in the
/linux-4.4.14/Documentation/input/
Dsentelic.txt469 section A for packet parsing detail(ignore byte 4, bit ~ 7)
473 section B for packet parsing detail
477 section A for packet parsing detail
481 section A for packet parsing detail (ignore byte 4, bit ~ 7)
/linux-4.4.14/fs/nfs/
DKconfig17 mount(8) man page. More detail about the Linux NFS client
/linux-4.4.14/Documentation/video4linux/bttv/
DSound-FAQ38 How sound works in detail
/linux-4.4.14/Documentation/virtual/kvm/
Dnested-vmx.txt17 We describe in much greater detail the theory behind the nested VMX feature,
Dtimekeeping.txt274 avoid repetition of the detail here. It should be pointed out that the APIC
/linux-4.4.14/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.txt154 necessary information for the framework. The struct is also explained in detail
/linux-4.4.14/Documentation/i2c/
Dslave-interface50 described in detail. After that, some implementation hints for extending bus
/linux-4.4.14/Documentation/locking/
Dspinlocks.txt77 attention to design detail (see Documentation/RCU/listRCU.txt).
Drt-mutex-design.txt80 blocked on one of its locks. This is described in more detail
322 in more detail, but is set whenever there are waiters on a mutex.
/linux-4.4.14/Documentation/laptops/
Ddisk-shock-protection.txt80 There is a technical detail of this implementation that may cause some
Dthinkpad-acpi.txt777 The ThinkPad LED sysfs interface is described in detail by the LED class
/linux-4.4.14/fs/cifs/
DKconfig79 /proc/fs/cifs (see fs/cifs/README for more detail) or via an
/linux-4.4.14/drivers/cpufreq/
DKconfig44 This will show detail CPU frequency translation table in sysfs file
/linux-4.4.14/Documentation/filesystems/
Dnilfs2.txt270 For detail on the format of each file, please see include/linux/nilfs2_fs.h.
Dautofs4-mount-control.txt100 somewhat more detail to the implementation but it isn't needed for the
101 sake of the problem explanation. The one important detail is that these
Dcoda.txt189 kernel should be documented in great detail. This is the aim of this
/linux-4.4.14/Documentation/
Dkobject.txt16 adding detail as we go. To that end, here are some quick definitions of
39 safely ignore that implementation detail as the kset core code handles
Dsysfs-rules.txt84 Everything else is just a kernel driver-core implementation detail
DSubmittingPatches134 about it in technical detail. It's important to describe the change
327 Contact detail and documentation fixes
456 point out some special detail about the sign-off.
DHOWTO104 These files describe in explicit detail how to successfully create
379 already discussed in detail are only recorded at the mailing list
Dkernel-per-CPU-kthreads.txt27 echo 1 > max_graph_depth # Increase the "1" for more detail
Dadding-syscalls.txt489 implementation paths in detail for v3.14:
Dkernel-docs.txt334 different types of devices and their properties. Going into detail
/linux-4.4.14/scripts/
Danalyze_suspend.py2472 detail = ' var devtable = [];\n'
2475 detail += ' devtable[%d] = "%s";\n' % (data.testnumber, topo)
2476 detail += ' var bounds = [%f,%f];\n' % (t0, tMax)
2479 '<script type="text/javascript">\n'+detail+\
/linux-4.4.14/Documentation/isdn/
DINTERFACE463 para = protocol and function specific. See isdnif.h for detail.
717 para = protocol and function specific. See isdnif.h for detail.
/linux-4.4.14/Documentation/serial/
Dtty.txt32 about to enter and exit although this detail matters not).
Dmoxa-smartio77 Public License announcement in each source code file for more detail.
/linux-4.4.14/drivers/power/
DKconfig400 documentation for more detail. The base name for this driver is
/linux-4.4.14/Documentation/powerpc/
Dcxlflash.txt159 detail in the description for the DK_CXLFLASH_DETACH ioctl.
/linux-4.4.14/Documentation/arm/
Dcluster-pm-race-avoidance.txt442 detail in vlocks.txt.
/linux-4.4.14/Documentation/ioctl/
Dcdrom.txt586 4-bit value used to control spindown (TODO: more detail here)
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt308 structure pointer as an argument, that will detail which
/linux-4.4.14/arch/x86/math-emu/
DREADME128 detail from the way an 80486 does.
/linux-4.4.14/Documentation/trace/
Devents.txt313 which can take various forms and are described in detail below;
Dftrace.txt1891 need to see what happens in detail on any areas (or specific
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt73 in full gory detail (ALT_ECB is a libdes variant):
/linux-4.4.14/drivers/staging/rtl8192u/
Dcopying239 be similar in spirit to the present version, but may differ in detail to
/linux-4.4.14/tools/usb/usbip/
DCOPYING239 be similar in spirit to the present version, but may differ in detail to
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt373 for additional detail on real-life experience of the causes of
/linux-4.4.14/drivers/staging/rtl8192e/
Dlicense239 similar in spirit to the present version, but may differ in detail to
/linux-4.4.14/
DCOPYING255 be similar in spirit to the present version, but may differ in detail to
/linux-4.4.14/kernel/trace/
DKconfig326 is to be analyzed in much detail.
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt136 The main requirement that will be defined in more detail below is
141 and properties to be present. This will be described in detail in
514 the storage format. This chapter does _not_ describe the detail of the
/linux-4.4.14/net/ipv4/
DKconfig507 For more detail see http://www.icir.org/floyd/hstcp.html
/linux-4.4.14/Documentation/nvdimm/
Dnvdimm.txt133 distinction. The different device-types are an implementation detail
/linux-4.4.14/Documentation/RCU/
DRTFP.txt260 not described in great detail -- one could imagine using process
293 not described in great detail -- one could imagine using process
DwhatisRCU.txt192 and is described in more detail in a later section. Instead of
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt984 The sections below describe this in more detail.
1182 forge.net/> and explains these in detail, as well as
/linux-4.4.14/arch/arm/
DKconfig1597 The problem is described in more detail at:
/linux-4.4.14/drivers/staging/speakup/
Dspkguide.txt1533 differ in detail to address new problems or concerns. See