Home
last modified time | relevance | path

Searched refs:keyword (Results 1 – 38 of 38) sorted by relevance

/linux-4.1.27/drivers/staging/speakup/
Dvarhandlers.c61 int spk_chartab_get_value(char *keyword) in spk_chartab_get_value() argument
65 if (!strcmp(keyword, "ALPHA")) in spk_chartab_get_value()
67 else if (!strcmp(keyword, "B_CTL")) in spk_chartab_get_value()
69 else if (!strcmp(keyword, "WDLM")) in spk_chartab_get_value()
71 else if (!strcmp(keyword, "A_PUNC")) in spk_chartab_get_value()
73 else if (!strcmp(keyword, "PUNC")) in spk_chartab_get_value()
75 else if (!strcmp(keyword, "NUM")) in spk_chartab_get_value()
77 else if (!strcmp(keyword, "A_CAP")) in spk_chartab_get_value()
79 else if (!strcmp(keyword, "B_CAPSYM")) in spk_chartab_get_value()
81 else if (!strcmp(keyword, "B_SYM")) in spk_chartab_get_value()
Dspeakup.h57 extern int spk_chartab_get_value(char *keyword);
Dkobjects.c114 char keyword[MAX_DESC_LEN + 1]; in chars_chartab_store() local
181 outptr = keyword; in chars_chartab_store()
194 charclass = spk_chartab_get_value(keyword); in chars_chartab_store()
Dspkguide.txt66 DoubleTalk LT at boot up. You may replace the ltlk synthesizer keyword
67 with the keyword for whatever synthesizer you wish to use. The
423 to the device whose keyword is KWD.
511 # Replace KWD with the keyword for your synthesizer, E.G., ltlk for LiteTalk.
530 synthesizer keyword to the /speakup/synth sys entry.
533 a second one is connected in its place. Then echo the keyword for the
536 keywords in section 1 to find the keyword which matches your synth.
554 named speakup_<keyword>, where <keyword> is the keyword for the
569 were using a different synth, then you would substitute its keyword in
587 of by simply echoing the synthesizer keyword into the
[all …]
/linux-4.1.27/scripts/
Dunifdef.c191 static char *keyword; /* used for editing #elif's */ variable
453 static void Mpass (void) { strncpy(keyword, "if ", 4); Pelif(); } in Mpass()
522 snprintf(keyword, tline + sizeof(tline) - keyword, in keywordedit()
669 keyword = tline + (cp - tline); in parseline()
671 kwlen = cp - keyword; in parseline()
676 if (strlcmp("ifdef", keyword, kwlen) == 0 || in parseline()
677 strlcmp("ifndef", keyword, kwlen) == 0) { in parseline()
682 retval = (keyword[2] == 'n') in parseline()
692 } else if (strlcmp("if", keyword, kwlen) == 0) in parseline()
694 else if (strlcmp("elif", keyword, kwlen) == 0) in parseline()
[all …]
/linux-4.1.27/drivers/media/usb/pvrusb2/
Dpvrusb2-debugifc.c120 const char *keyword) in debugifc_match_keyword() argument
123 if (!keyword) return 0; in debugifc_match_keyword()
124 kl = strlen(keyword); in debugifc_match_keyword()
126 return !memcmp(buf,keyword,kl); in debugifc_match_keyword()
/linux-4.1.27/security/keys/encrypted-keys/
Dencrypted.c185 char *p, *keyword; in datablob_parse() local
187 keyword = strsep(&datablob, " \t"); in datablob_parse()
188 if (!keyword) { in datablob_parse()
192 key_cmd = match_token(keyword, key_tokens, args); in datablob_parse()
236 "when called from .update method\n", keyword); in datablob_parse()
244 "when called from .update method\n", keyword); in datablob_parse()
258 keyword); in datablob_parse()
265 keyword); in datablob_parse()
/linux-4.1.27/Documentation/fb/
Dsisfb.txt56 described above or the vesa keyword instead of mode). If compiled as a module,
74 The desired display mode can be specified using the keyword "mode" with
87 Additionally, sisfb understands the keyword "vesa" followed by a VESA mode
105 You should *not* compile-in vesafb. And please do not use the "vga=" keyword
Dframebuffer.txt139 still have to specify the color depth (using the Depth keyword) and virtual
140 resolution (using the Virtual keyword) though. This is the default for the
/linux-4.1.27/scripts/genksyms/
Dkeywords.gperf37 # field name which breaks the genksyms parser. It is not a gcc keyword anyway.
Dlex.lex.c_shipped1906 /* Bring in the keyword recognizer. */
/linux-4.1.27/tools/power/acpi/os_specific/service_layers/
Doslinuxtbl.c81 osl_find_rsdp_via_efi_by_keyword(FILE * file, const char *keyword);
436 osl_find_rsdp_via_efi_by_keyword(FILE * file, const char *keyword) in osl_find_rsdp_via_efi_by_keyword() argument
442 snprintf(format, 32, "%s=%s", keyword, "%llx"); in osl_find_rsdp_via_efi_by_keyword()
/linux-4.1.27/drivers/usb/misc/sisusbvga/
DKconfig37 the "options" keyword, such as eg.
/linux-4.1.27/scripts/kconfig/
DMakefile60 --add-comments --keyword=_ --keyword=N_ \
/linux-4.1.27/Documentation/filesystems/
Djfs.txt17 read-write. The resize keyword with no value will grow
/linux-4.1.27/security/tomoyo/
Dutil.c131 bool tomoyo_permstr(const char *string, const char *keyword) in tomoyo_permstr() argument
133 const char *cp = strstr(string, keyword); in tomoyo_permstr()
Dcommon.h941 bool tomoyo_permstr(const char *string, const char *keyword);
Dcommon.c1111 const char *keyword; in tomoyo_write_domain2() member
1124 tomoyo_callback[i].keyword)) in tomoyo_write_domain2()
/linux-4.1.27/Documentation/trace/
Dmmiotrace.txt126 one line in the log. A record starts with a keyword, followed by keyword-
/linux-4.1.27/Documentation/scsi/
Din2000.txt98 search for the 'nosync' keyword in the command-line
145 'period' keyword.
Dst.txt266 to use the same keyword used when loading as module but prepended
273 the driver as module. If several parameters are set, the keyword-value
Dncr53c8xx.txt649 Each string argument must be specified as "keyword:value". Only lower-case
653 specified driver on each adapter. To exclude a chip use the 'excl' keyword.
DChangeLog.1992-19971902 * seagate.c: Use volatile keyword for memory-mapped register pointers.
/linux-4.1.27/fs/reiserfs/
DKconfig17 database and keyword search systems than block allocation based file
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dmarvell,berlin.txt102 Be aware the Marvell Berlin datasheets use the keyword 'mode' for what is called
/linux-4.1.27/Documentation/s390/
DCommonIO27 You can use the 'all' keyword to ignore all devices. The 'ipldev' and 'condev'
/linux-4.1.27/Documentation/
Ddynamic-debug-howto.txt127 A match specification comprises a keyword, which controls the
146 The meanings of each keyword are:
Dvolatile-considered-harmful.txt80 keyword to asm statements will prevent this removal.
Dkernel-doc-nano-HOWTO.txt315 This is done by using a DOC: section keyword with a section title. E.g.:
DCodingStyle181 function-versus-keyword usage. Use a space after (most) keywords. The
752 very often is not. Abundant use of the inline keyword leads to a much bigger
Datomic_ops.txt78 Some architectures may choose to use the volatile keyword, barriers, or inline
/linux-4.1.27/Documentation/isdn/
DREADME.hysdn144 keyword LOG. All other lines are output from the driver.
/linux-4.1.27/Documentation/ide/
Dide.txt175 driver using the "options=" keyword to insmod, while replacing any ',' with
/linux-4.1.27/Documentation/sysctl/
Dfs.txt190 http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=/tmp
/linux-4.1.27/drivers/scsi/
DBusLogic.c3619 static bool __init blogic_parse(char **str, char *keyword) in blogic_parse() argument
3622 while (*keyword != '\0') { in blogic_parse()
3624 char keywordch = *keyword++; in blogic_parse()
/linux-4.1.27/Documentation/kbuild/
Dkconfig-language.txt253 line starts with a keyword (except help texts). The following keywords
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.reg55 * from the driver code, and this keyword inhibit generation
Daic79xx.reg84 * from the driver code, and this keyword inhibit generation