Home
last modified time | relevance | path

Searched refs:what (Results 1 – 200 of 786) sorted by relevance

1234

/linux-4.4.14/drivers/usb/storage/
Ddebug.c59 char *what = NULL; in usb_stor_show_command() local
63 case TEST_UNIT_READY: what = "TEST_UNIT_READY"; break; in usb_stor_show_command()
64 case REZERO_UNIT: what = "REZERO_UNIT"; break; in usb_stor_show_command()
65 case REQUEST_SENSE: what = "REQUEST_SENSE"; break; in usb_stor_show_command()
66 case FORMAT_UNIT: what = "FORMAT_UNIT"; break; in usb_stor_show_command()
67 case READ_BLOCK_LIMITS: what = "READ_BLOCK_LIMITS"; break; in usb_stor_show_command()
68 case REASSIGN_BLOCKS: what = "REASSIGN_BLOCKS"; break; in usb_stor_show_command()
69 case READ_6: what = "READ_6"; break; in usb_stor_show_command()
70 case WRITE_6: what = "WRITE_6"; break; in usb_stor_show_command()
71 case SEEK_6: what = "SEEK_6"; break; in usb_stor_show_command()
[all …]
/linux-4.4.14/drivers/usb/image/
Dmicrotek.c227 char *what = NULL; in mts_show_command() local
230 case TEST_UNIT_READY: what = "TEST_UNIT_READY"; break; in mts_show_command()
231 case REZERO_UNIT: what = "REZERO_UNIT"; break; in mts_show_command()
232 case REQUEST_SENSE: what = "REQUEST_SENSE"; break; in mts_show_command()
233 case FORMAT_UNIT: what = "FORMAT_UNIT"; break; in mts_show_command()
234 case READ_BLOCK_LIMITS: what = "READ_BLOCK_LIMITS"; break; in mts_show_command()
235 case REASSIGN_BLOCKS: what = "REASSIGN_BLOCKS"; break; in mts_show_command()
236 case READ_6: what = "READ_6"; break; in mts_show_command()
237 case WRITE_6: what = "WRITE_6"; break; in mts_show_command()
238 case SEEK_6: what = "SEEK_6"; break; in mts_show_command()
[all …]
/linux-4.4.14/net/netfilter/
Dxt_connbytes.c26 u_int64_t what = 0; /* initialize to make gcc happy */ in connbytes_mt() local
41 switch (sinfo->what) { in connbytes_mt()
45 what = atomic64_read(&counters[IP_CT_DIR_ORIGINAL].packets); in connbytes_mt()
48 what = atomic64_read(&counters[IP_CT_DIR_REPLY].packets); in connbytes_mt()
51 what = atomic64_read(&counters[IP_CT_DIR_ORIGINAL].packets); in connbytes_mt()
52 what += atomic64_read(&counters[IP_CT_DIR_REPLY].packets); in connbytes_mt()
59 what = atomic64_read(&counters[IP_CT_DIR_ORIGINAL].bytes); in connbytes_mt()
62 what = atomic64_read(&counters[IP_CT_DIR_REPLY].bytes); in connbytes_mt()
65 what = atomic64_read(&counters[IP_CT_DIR_ORIGINAL].bytes); in connbytes_mt()
66 what += atomic64_read(&counters[IP_CT_DIR_REPLY].bytes); in connbytes_mt()
[all …]
/linux-4.4.14/drivers/isdn/mISDN/
Ddsp_dtmf.c120 u8 what; in dsp_dtmf_goertzel_decode() local
221 what = 0; in dsp_dtmf_goertzel_decode()
279 what = 0; in dsp_dtmf_goertzel_decode()
281 what = dtmf_matrix[lowgroup][highgroup]; in dsp_dtmf_goertzel_decode()
284 if (what && (dsp_debug & DEBUG_DSP_DTMF)) in dsp_dtmf_goertzel_decode()
285 printk(KERN_DEBUG "DTMF what: %c\n", what); in dsp_dtmf_goertzel_decode()
287 if (dsp->dtmf.lastwhat != what) in dsp_dtmf_goertzel_decode()
292 if (dsp->dtmf.lastdigit != what) { in dsp_dtmf_goertzel_decode()
293 dsp->dtmf.lastdigit = what; in dsp_dtmf_goertzel_decode()
294 if (what) { in dsp_dtmf_goertzel_decode()
[all …]
/linux-4.4.14/drivers/isdn/i4l/
Disdn_audio.c505 char what; in isdn_audio_eval_dtmf() local
524 what = ' '; in isdn_audio_eval_dtmf()
552 what = dtmf_matrix[grp[LOGRP]][grp[HIGRP]]; in isdn_audio_eval_dtmf()
554 s->last = what; /* min. 1 non-DTMF between DTMF */ in isdn_audio_eval_dtmf()
556 what = '.'; in isdn_audio_eval_dtmf()
559 what = '.'; in isdn_audio_eval_dtmf()
561 if ((what != s->last) && (what != ' ') && (what != '.')) { in isdn_audio_eval_dtmf()
562 printk(KERN_DEBUG "dtmf: tt='%c'\n", what); in isdn_audio_eval_dtmf()
565 *p = what; in isdn_audio_eval_dtmf()
579 s->last = what; in isdn_audio_eval_dtmf()
[all …]
/linux-4.4.14/include/net/
Dinet_connection_sock.h196 static inline void inet_csk_clear_xmit_timer(struct sock *sk, const int what) in inet_csk_clear_xmit_timer() argument
200 if (what == ICSK_TIME_RETRANS || what == ICSK_TIME_PROBE0) { in inet_csk_clear_xmit_timer()
205 } else if (what == ICSK_TIME_DACK) { in inet_csk_clear_xmit_timer()
221 static inline void inet_csk_reset_xmit_timer(struct sock *sk, const int what, in inet_csk_reset_xmit_timer() argument
230 sk, what, when, current_text_addr()); in inet_csk_reset_xmit_timer()
235 if (what == ICSK_TIME_RETRANS || what == ICSK_TIME_PROBE0 || in inet_csk_reset_xmit_timer()
236 what == ICSK_TIME_EARLY_RETRANS || what == ICSK_TIME_LOSS_PROBE) { in inet_csk_reset_xmit_timer()
237 icsk->icsk_pending = what; in inet_csk_reset_xmit_timer()
240 } else if (what == ICSK_TIME_DACK) { in inet_csk_reset_xmit_timer()
/linux-4.4.14/drivers/staging/rts5208/
Drtsx_scsi.c36 char *what = NULL; in scsi_show_command() local
42 what = "TEST_UNIT_READY"; in scsi_show_command()
45 what = "REZERO_UNIT"; in scsi_show_command()
48 what = "REQUEST_SENSE"; in scsi_show_command()
51 what = "FORMAT_UNIT"; in scsi_show_command()
54 what = "READ_BLOCK_LIMITS"; in scsi_show_command()
57 what = "REASSIGN_BLOCKS"; in scsi_show_command()
60 what = "READ_6"; in scsi_show_command()
63 what = "WRITE_6"; in scsi_show_command()
66 what = "SEEK_6"; in scsi_show_command()
[all …]
/linux-4.4.14/drivers/ide/
Dide-timings.c123 struct ide_timing *m, unsigned int what) in ide_timing_merge() argument
125 if (what & IDE_TIMING_SETUP) in ide_timing_merge()
127 if (what & IDE_TIMING_ACT8B) in ide_timing_merge()
129 if (what & IDE_TIMING_REC8B) in ide_timing_merge()
131 if (what & IDE_TIMING_CYC8B) in ide_timing_merge()
133 if (what & IDE_TIMING_ACTIVE) in ide_timing_merge()
135 if (what & IDE_TIMING_RECOVER) in ide_timing_merge()
137 if (what & IDE_TIMING_CYCLE) in ide_timing_merge()
139 if (what & IDE_TIMING_UDMA) in ide_timing_merge()
/linux-4.4.14/drivers/block/drbd/
Ddrbd_req.h284 extern int __req_mod(struct drbd_request *req, enum drbd_req_event what,
289 extern void tl_restart(struct drbd_connection *connection, enum drbd_req_event what);
290 extern void _tl_restart(struct drbd_connection *connection, enum drbd_req_event what);
298 static inline int _req_mod(struct drbd_request *req, enum drbd_req_event what) in _req_mod() argument
305 rv = __req_mod(req, what, &m); in _req_mod()
317 enum drbd_req_event what) in req_mod() argument
325 rv = __req_mod(req, what, &m); in req_mod()
/linux-4.4.14/arch/arm/mach-ixp4xx/include/mach/
Dnpe.h32 int npe_send_message(struct npe *npe, const void *msg, const char *what);
33 int npe_recv_message(struct npe *npe, void *msg, const char *what);
34 int npe_send_recv_message(struct npe *npe, void *msg, const char *what);
/linux-4.4.14/kernel/trace/
Dblktrace.c172 static int act_log_check(struct blk_trace *bt, u32 what, sector_t sector, in act_log_check() argument
175 if (((bt->act_mask << BLK_TC_SHIFT) & what) == 0) in act_log_check()
202 int rw, u32 what, int error, int pdu_len, void *pdu_data) in __blk_add_trace() argument
217 what |= ddir_act[rw & WRITE]; in __blk_add_trace()
218 what |= MASK_TC_BIT(rw, SYNC); in __blk_add_trace()
219 what |= MASK_TC_BIT(rw, RAHEAD); in __blk_add_trace()
220 what |= MASK_TC_BIT(rw, META); in __blk_add_trace()
221 what |= MASK_TC_BIT(rw, DISCARD); in __blk_add_trace()
222 what |= MASK_TC_BIT(rw, FLUSH); in __blk_add_trace()
223 what |= MASK_TC_BIT(rw, FUA); in __blk_add_trace()
[all …]
/linux-4.4.14/sound/isa/gus/
Dgus_reset.c72 void snd_gf1_set_default_handlers(struct snd_gus_card * gus, unsigned int what) in snd_gf1_set_default_handlers() argument
74 if (what & SNDRV_GF1_HANDLER_MIDI_OUT) in snd_gf1_set_default_handlers()
76 if (what & SNDRV_GF1_HANDLER_MIDI_IN) in snd_gf1_set_default_handlers()
78 if (what & SNDRV_GF1_HANDLER_TIMER1) in snd_gf1_set_default_handlers()
80 if (what & SNDRV_GF1_HANDLER_TIMER2) in snd_gf1_set_default_handlers()
82 if (what & SNDRV_GF1_HANDLER_VOICE) { in snd_gf1_set_default_handlers()
85 voice = &gus->gf1.voices[what & 0xffff]; in snd_gf1_set_default_handlers()
91 if (what & SNDRV_GF1_HANDLER_DMA_WRITE) in snd_gf1_set_default_handlers()
93 if (what & SNDRV_GF1_HANDLER_DMA_READ) in snd_gf1_set_default_handlers()
/linux-4.4.14/drivers/connector/
Dcn_proc.c82 ev->what = PROC_EVENT_FORK; in proc_fork_connector()
113 ev->what = PROC_EVENT_EXEC; in proc_exec_connector()
137 ev->what = which_id; in proc_id_connector()
177 ev->what = PROC_EVENT_SID; in proc_sid_connector()
202 ev->what = PROC_EVENT_PTRACE; in proc_ptrace_connector()
235 ev->what = PROC_EVENT_COMM; in proc_comm_connector()
261 ev->what = PROC_EVENT_COREDUMP; in proc_coredump_connector()
286 ev->what = PROC_EVENT_EXIT; in proc_exit_connector()
322 ev->what = PROC_EVENT_NONE; in cn_proc_ack()
/linux-4.4.14/drivers/net/phy/
Dmdio-gpio.c104 static void mdio_set(struct mdiobb_ctrl *ctrl, int what) in mdio_set() argument
111 what ^ bitbang->mdo_active_low); in mdio_set()
114 what ^ bitbang->mdio_active_low); in mdio_set()
117 static void mdc_set(struct mdiobb_ctrl *ctrl, int what) in mdc_set() argument
122 gpio_set_value_cansleep(bitbang->mdc, what ^ bitbang->mdc_active_low); in mdc_set()
/linux-4.4.14/Documentation/
DIRQ.txt10 array, but except for what linux/interrupt.h implements the details
14 machine. Typically what is enumerated is the number of input pins on
16 what is enumerated are the 16 input pins on the two i8259 interrupt
DManagementStyle25 to what the answer is.
51 makes you look like you know what you're doing, so what a kernel manager
86 - having somebody tell you that what you worked on for the last year
90 engineer. And remember: "irrevocable" was what we tried to avoid in
108 sure as hell shouldn't encourage them by promising them that what they
115 healthy dose of critical thinking on what they do.
188 which is what the game is all about.
192 good idea - go wild", or "That sounds good, but what about xxx?". The
199 specific directions, but let's face it, they might be good at what they
201 naturally gravitate back to what they are good at, so it's not like you
[all …]
DHOWTO49 been created over time based on what they have found to work best for
87 what is necessary to do to configure and build the kernel. People
144 happen, and what to do if you want to get a change into one of these
149 development. Please consult this list if you do not find what you
153 A good introduction describing exactly what a patch is and how to
195 and possibly be pointed in the direction of what to go work on next, if
259 It is worth mentioning what Andrew Morton wrote on the linux-kernel
285 documents what kinds of changes are acceptable for the -stable tree, and
300 development in source repositories. That way, others can see what is
328 This way, the -next kernel gives a summary outlook onto what will be
[all …]
Dkref.txt98 This way, it doesn't matter what order the two threads handle the
116 Don't assume you know what you are doing and use the above construct.
117 First of all, you may not know what you are doing. Second, you may
118 know what you are doing (there are some situations where locking is
120 know what they are doing may change the code or copy the code. It's
Dvolatile-considered-harmful.txt12 to suppress optimization, which is almost never what one really wants to
37 compiler might think it knows what will be in shared_data, but the
98 volatile should take a step back and think about what they are truly trying
Doops-tracing.txt12 what you were doing. If it occurs repeatably try and describe how to recreate
86 and do a replace of spaces to "\x" - that's what I do, as I'm too lazy
108 and then you get a better idea of what happens than with the gdb
112 sources (and general knowledge of what it _should_ do), the assembly
119 Essentially, you just look at what doesn't match (in this case it was the
120 "Code" disassembly that didn't match with what the compiler generated).
Drobust-futex-ABI.txt9 The interesting data as to what futexes a thread is holding is kept on a
12 kernel intervention required for robust_futexes above and beyond what is
59 address of the associated 'lock entry', plus or minus, of what will
102 robust_futex mechanism doesn't care what else is in that structure, so
DCodeOfConflict20 information on who is on the Technical Advisory Board and what their
Dapplying-patches.txt10 a patch to the kernel or, more specifically, what base kernel a patch for
24 To correctly apply a patch you need to know what base it was generated from
25 and what new version the patch will change the source tree into. These
42 local machine (but is often useful info to see what version an otherwise
78 (what I assume you've done in the examples below), then you simply run
89 what would happen, but doesn't actually make any changes. Finally --verbose
121 read this file to see exactly what change couldn't be applied, so you can
312 development branches and is also what will eventually turn into the next
Dvgaarbiter.txt58 diagnostic only). "decodes" indicate what the card currently
59 decodes, "owns" indicates what is currently enabled on it, and
60 "locks" indicates what is locked by this card. If the card is
D00-INDEX2 This is a brief list of all the files in ./linux/Documentation and what
45 - description of what an IRQ is.
229 - what to do when the kernel can't find the 1st process to run.
385 - info on what red-black trees are and what they are for.
393 - a description of what robust futexes are.
/linux-4.4.14/arch/cris/mm/
Dinit.c38 void free_init_pages(const char *what, unsigned long begin, unsigned long end) in free_init_pages() argument
49 printk(KERN_INFO "Freeing %s: %ldk freed\n", what, (end - begin) >> 10); in free_init_pages()
/linux-4.4.14/Documentation/kbuild/
DKconfig.recursion-issue-019 # understand why this recursive dependency issue occurs lets consider what
10 # Kconfig needs to address. We iterate over what Kconfig needs to address
30 # what values are possible for CORE we ended up needing to address questions
32 # question of what are the possible values of CORE would make the kconfig
Dkconfig.txt17 for you, so you may find that you need to see what NEW kernel
155 names, so you have to know something close to what you are
212 names, so you have to know something close to what you are
/linux-4.4.14/drivers/net/ethernet/freescale/fs_enet/
Dmii-bitbang.c77 static inline void mdio(struct mdiobb_ctrl *ctrl, int what) in mdio() argument
81 if (what) in mdio()
90 static inline void mdc(struct mdiobb_ctrl *ctrl, int what) in mdc() argument
94 if (what) in mdc()
/linux-4.4.14/drivers/vfio/platform/reset/
DKconfig7 If you don't know what to do here, say N.
15 If you don't know what to do here, say N.
/linux-4.4.14/arch/arm/plat-samsung/
Dpm-check.c144 static inline int in_region(void *ptr, int size, void *what, size_t whatsz) in in_region() argument
146 if ((what+whatsz) < ptr) in in_region()
149 if (what > (ptr+size)) in in_region()
/linux-4.4.14/include/uapi/linux/
Dcn_proc.h46 enum what { enum
63 } what; member
/linux-4.4.14/drivers/vfio/platform/
DKconfig10 If you don't know what to do here, say N.
20 If you don't know what to do here, say N.
/linux-4.4.14/arch/arm/mach-ixp4xx/
Dixp4xx_npe.c412 int npe_send_message(struct npe *npe, const void *msg, const char *what) in npe_send_message() argument
418 what, send[0], send[1]); in npe_send_message()
451 int npe_recv_message(struct npe *npe, void *msg, const char *what) in npe_recv_message() argument
456 debug_msg(npe, "Trying to receive message %s\n", what); in npe_recv_message()
489 int npe_send_recv_message(struct npe *npe, void *msg, const char *what) in npe_send_recv_message() argument
494 if ((result = npe_send_message(npe, msg, what)) != 0) in npe_send_recv_message()
496 if ((result = npe_recv_message(npe, recv, what)) != 0) in npe_send_recv_message()
501 what); in npe_send_recv_message()
/linux-4.4.14/drivers/vfio/pci/
DKconfig10 If you don't know what to do here, say N.
20 If you don't know what to do here, say N.
/linux-4.4.14/net/caif/
Dcaif_usb.c123 static int cfusbl_device_notify(struct notifier_block *me, unsigned long what, in cfusbl_device_notify() argument
149 if (what == NETDEV_UNREGISTER) in cfusbl_device_notify()
152 if (what != NETDEV_REGISTER) in cfusbl_device_notify()
/linux-4.4.14/drivers/power/reset/
Dvexpress-poweroff.c23 static void vexpress_reset_do(struct device *dev, const char *what) in vexpress_reset_do() argument
34 dev_emerg(dev, "Unable to %s (%d)\n", what, err); in vexpress_reset_do()
/linux-4.4.14/arch/um/os-Linux/
Dfile.c463 int what, err; in os_shutdown_socket() local
466 what = SHUT_RDWR; in os_shutdown_socket()
468 what = SHUT_RD; in os_shutdown_socket()
470 what = SHUT_WR; in os_shutdown_socket()
474 err = shutdown(fd, what); in os_shutdown_socket()
/linux-4.4.14/arch/cris/arch-v32/mach-fs/
DKconfig81 SDRAM command. Should be 0 unless you really know what
96 stuff. If you don't know what to use, it is always safe to put all
118 stuff. If you don't know what to use, it is always safe to put all
140 stuff. If you don't know what to use, it is always safe to put all
162 stuff. If you don't know what to use, it is always safe to put all
184 stuff. If you don't know what to use, it is always safe to put all
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/i2c/
Dbus.c138 nvkm_i2c_bus_probe(struct nvkm_i2c_bus *bus, const char *what, in nvkm_i2c_bus_probe() argument
145 BUS_DBG(bus, "probing %ss", what); in nvkm_i2c_bus_probe()
160 what, info[i].dev.type); in nvkm_i2c_bus_probe()
/linux-4.4.14/arch/cris/arch-v32/
DKconfig96 SDRAM command. Should be 0 unless you really know what
111 stuff. If you don't know what to use, it is always safe to put all
133 stuff. If you don't know what to use, it is always safe to put all
155 stuff. If you don't know what to use, it is always safe to put all
177 stuff. If you don't know what to use, it is always safe to put all
199 stuff. If you don't know what to use, it is always safe to put all
/linux-4.4.14/drivers/staging/olpc_dcon/
DKconfig24 have an XO-1 (or if you're unsure what model you have), you should
34 have an XO-1.5 (or if you're unsure what model you have), you
/linux-4.4.14/Documentation/filesystems/
Dgfs2-uevents.txt5 This document explains what the events are and what they are used
58 information about what the error is, which is something that needs to
82 The LOCKPROTO is a string, and its value depends on what is set
Dxfs-self-describing-metadata.txt17 validating and repairing the structure, there are limits to what they can
40 magic number in the metadata block, we have no other way of identifying what it
49 pointers in a btree end up with loops in them) are the key to understanding what
50 went wrong, but it is impossible to tell what order the blocks were linked into
105 object, we don't know what inode it belongs to and hence have to walk the entire
153 modification process, and seeks only to check that the metadata is what it says
164 object matches what was expected. If the verification process fails, then it
Dhpfs.txt94 chgrp symlinks but I don't know what is it good for. chmoding symlink results
114 really what IBM developers wanted? But problems continued. When I created in
126 lowercasing no matter what's file codepage index. Usually all file names are in
127 this codepage - if you don't try to do what I described above :-)
160 You can't rename over directories (what is it good for?).
173 anybody know what does it mean?
/linux-4.4.14/arch/cris/arch-v32/mach-a3/
DKconfig58 stuff. If you don't know what to use, it is always safe to put all
78 stuff. If you don't know what to use, it is always safe to put all
98 stuff. If you don't know what to use, it is always safe to put all
/linux-4.4.14/Documentation/isdn/
D00-INDEX14 - general info on what you need and what to do for Linux ISDN.
DREADME.diversion29 (Or what can the i4l diversion services do for me)
42 (Or what can the i4l diversion services do for me)
119 specify during a certain amount of time (normally 4 to 10 seconds) what
DsyncPPP.FAQ4 Q01: what's pppd, ipppd, syncPPP, asyncPPP ??
19 Q01: pppd, ipppd, syncPPP, asyncPPP .. what is that ?
20 what should I use?
/linux-4.4.14/drivers/i2c/
DKconfig111 If you don't know what to do here, definitely say N.
128 problem with I2C support and want to see more of what is going on.
135 a problem with I2C support and want to see more of what is going
144 a problem with I2C support and want to see more of what is going
/linux-4.4.14/include/uapi/linux/netfilter/
Dxt_connbytes.h23 __u8 what; /* ipt_connbytes_what */ member
/linux-4.4.14/arch/x86/kernel/
Dverify_cpu.S102 movl $0x1,%eax # Does the cpu have what it takes
113 movl $0x80000001,%eax # Does the cpu have what it takes
/linux-4.4.14/drivers/mmc/host/
Dcb710-mmc.c113 static int cb710_check_event(struct cb710_slot *slot, u8 what) in cb710_check_event() argument
138 if ((status >> 8) & what) { in cb710_check_event()
139 cb710_write_port_8(slot, CB710_MMC_STATUS1_PORT, what); in cb710_check_event()
146 static int cb710_wait_for_event(struct cb710_slot *slot, u8 what) in cb710_wait_for_event() argument
156 while (!(err = cb710_check_event(slot, what))) { in cb710_wait_for_event()
173 limit, what, e, x); in cb710_wait_for_event()
/linux-4.4.14/Documentation/security/
DLSM.txt27 what it tries to protect against and in what cases one would expect to
/linux-4.4.14/drivers/auxdisplay/
DKconfig49 If you don't know what I'm talking about, load the parport module,
68 If you don't know what I'm talking about, ignore it.
117 If you don't know what I'm talking about, ignore it.
/linux-4.4.14/Documentation/device-mapper/
Dlog-writes.txt18 log in a way that correlates to what is on disk and not what is in cache, to
34 Again this is to simulate what is actually on disk, this allows us to detect
51 which isn't quite what happened and wouldn't be caught during the log replay.
/linux-4.4.14/fs/reiserfs/
Dprints.c160 static char *is_there_reiserfs_struct(char *fmt, int *what) in is_there_reiserfs_struct() argument
167 *what = k[1]; in is_there_reiserfs_struct()
194 int what; in prepare_error_buf() local
200 while ((k = is_there_reiserfs_struct(fmt1, &what)) != NULL) { in prepare_error_buf()
205 switch (what) { in prepare_error_buf()
Ddir.c51 #define store_ih(where,what) copy_item_head (where, what) argument
/linux-4.4.14/Documentation/i2c/
Ddev-interface6 examine /sys/class/i2c-dev/ to see what number corresponds to which adapter.
42 /* ERROR HANDLING; you can check errno to see what went wrong */
46 When you have opened the device, you must specify with what device
52 /* ERROR HANDLING; you can check errno to see what went wrong */
161 what happened. The 'write' transactions return 0 on success; the
169 want to know what happens behind the screens.
Dinstantiating-devices6 I2C bus segment, and what address these devices are using. For this
190 kernels will find out that this method 3 is essentially similar to what
211 what addresses they live at. However, in certain cases, it does not, so a
248 available, and you don't need to know what driver the device needs.
Dsummary13 SMBus, but some SMBus protocols add semantics beyond what is required to
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-devices1 # Note: This documents additional properties of any device beyond what
Dsysfs-module20 what they accomplish.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt3 This binding specifies what properties must be available in the device tree
25 - mpic-msgr-receive-mask: Specifies what registers in the containing block
/linux-4.4.14/kernel/irq/
DKconfig88 If you don't know what this means you don't need it.
105 If you don't know what to do here, say N.
/linux-4.4.14/Documentation/fb/
Dmetronomefb.txt27 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
30 I neither have access to nor know exactly what the waveform does in terms of
Dtridentfb.txt48 look at the driver output to see what it says when initializing.
60 800 or 1280) and it is not what the driver seems to detect use it.
Dcmap_xfbdev.txt50 that the app wants to match to. The above code is doing what looks like a least
/linux-4.4.14/drivers/isdn/hardware/eicon/
Ddiva.c153 static diva_os_xdi_adapter_t *diva_q_get_next(struct list_head *what) in diva_q_get_next() argument
157 if (what && (what->next != &adapter_queue)) in diva_q_get_next()
158 a = list_entry(what->next, diva_os_xdi_adapter_t, link); in diva_q_get_next()
/linux-4.4.14/drivers/usb/core/
DKconfig11 let users know what specific device was added to the machine
12 in what location.
32 if you know exactly what you are doing.
/linux-4.4.14/Documentation/ABI/testing/
Ddebugfs-ideapad8 capability and what graphic component within the machine.
Dsysfs-bus-i2c-devices-fsa94805 show what device is attached
Dsysfs-ibft14 target name, and what NIC it is associated with. It can also
Ddebugfs-ec18 what you are doing! Rebooting afterwards also is a good idea.
Dsysfs-devices-edac101 Description: This attribute file will display what type of DRAM device is
108 Description: This attribute file will display what type of Error detection
138 Description: This attribute file will display what type of memory is
/linux-4.4.14/drivers/usb/
DREADME23 Here is a list of what each subdirectory here is, and what is contained in
/linux-4.4.14/arch/um/drivers/
Dnet_user.c206 static void change(char *dev, char *what, unsigned char *addr, in change() argument
212 char *argv[] = { "uml_net", version, what, dev, addr_buf, in change()
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt28 framework needs to supply at least basic details of what is required.
61 information with the core driver to provide information about what the
DSuspend.txt54 the maintainer and discuss what is required.
110 the actual suspend, giving detailed information on what is
/linux-4.4.14/Documentation/devicetree/
D00-INDEX12 - How Linux uses DT and what DT aims to solve.
Dusage-model.txt34 about what already exists. There are currently two different,
134 product line, and it is hard to nail down exactly what is meant when one
142 property must be documented as to what it indicates. Add
320 However, looking at the tree, it is not immediately obvious what kind
327 together to create the audio subsystem. I know what each device is
329 know what to do with each node?
363 what about the children of the SoC node? Shouldn't they be registered
/linux-4.4.14/Documentation/ioctl/
Dhdio.txt158 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
196 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
250 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
296 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
858 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
880 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
900 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
920 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
991 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
1011 EINVAL (bdev != bdev->bd_contains) (not sure what this means)
[all …]
/linux-4.4.14/drivers/hwmon/
Dasus_atk0110.c407 char const *what; in atk_sensor_type() local
411 what = "voltage"; in atk_sensor_type()
414 what = "temperature"; in atk_sensor_type()
417 what = "fan"; in atk_sensor_type()
420 what = "unknown"; in atk_sensor_type()
424 return what; in atk_sensor_type()
437 char const *what; in atk_print_sensor() local
445 what = atk_sensor_type(flags); in atk_print_sensor()
447 dev_dbg(dev, "%s: %#llx %s [%llu-%llu] %s\n", what, in atk_print_sensor()
Dsmm665.c375 #define SMM665_SHOW(what) \ argument
376 static ssize_t smm665_show_##what(struct device *dev, \
380 const int val = smm665_get_##what(dev, attr->index); \
/linux-4.4.14/arch/powerpc/include/asm/
Drheap.h80 extern int rh_get_stats(rh_info_t * info, int what, int max_stats,
/linux-4.4.14/arch/mips/include/asm/
Dbootinfo.h115 extern void free_init_pages(const char *what,
/linux-4.4.14/arch/um/os-Linux/drivers/
Dethertap_user.c31 enum { ADD_ADDR, DEL_ADDR } what; member
43 change.what = op; in etap_change()
/linux-4.4.14/arch/nios2/
DKconfig163 Say N here unless you know what you are doing.
177 Say N here unless you know what you are doing.
189 Say N here unless you know what you are doing.
/linux-4.4.14/drivers/staging/rdma/hfi1/
Dfirmware.c363 static int invalid_header(struct hfi1_devdata *dd, const char *what, in invalid_header() argument
371 what, expected, actual); in invalid_header()
644 static void write_rsa_data(struct hfi1_devdata *dd, int what, in write_rsa_data() argument
655 write_csr(dd, what + (8*i), *ptr); in write_rsa_data()
662 write_csr(dd, what + (8*i), value); in write_rsa_data()
671 static void write_streamed_rsa_data(struct hfi1_devdata *dd, int what, in write_streamed_rsa_data() argument
678 write_csr(dd, what, *ptr); in write_streamed_rsa_data()
/linux-4.4.14/arch/cris/arch-v10/
DKconfig28 what YOU choose in this option. The actual bits used are configured
38 what YOU choose in this option. The actual bits used are configured
48 what YOU choose in this option. The actual bits used are configured
333 stuff. If you don't know what to use, it is always safe to put all
362 If you don't know what to use, it is always safe to put all as
386 Configure what pin on CSPO-port that is used for controlling power
/linux-4.4.14/arch/microblaze/
DKconfig145 Unless you know what you are doing, say N here.
182 Say N here unless you know what you are doing.
208 Say N here unless you know what you are doing.
223 Say N here unless you know what you are doing.
/linux-4.4.14/drivers/vfio/
DKconfig32 If you don't know what to do here, say N.
/linux-4.4.14/fs/efs/
DKconfig10 what all this is about, it's safe to say N. For more information
/linux-4.4.14/drivers/ssb/
Dssb_private.h51 extern int ssb_pci_xtal(struct ssb_bus *bus, u32 what,
71 static inline int ssb_pci_xtal(struct ssb_bus *bus, u32 what, in ssb_pci_xtal() argument
Dpci.c85 int ssb_pci_xtal(struct ssb_bus *bus, u32 what, int turn_on) in ssb_pci_xtal() argument
104 outenable |= what; in ssb_pci_xtal()
112 if (what & SSB_GPIO_XTAL) { in ssb_pci_xtal()
115 if (what & SSB_GPIO_PLL) in ssb_pci_xtal()
126 if (what & SSB_GPIO_PLL) { in ssb_pci_xtal()
144 if (what & SSB_GPIO_XTAL) { in ssb_pci_xtal()
148 if (what & SSB_GPIO_PLL) { in ssb_pci_xtal()
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dfsl-sec2.txt15 - fsl,exec-units-mask : The bitmask representing what execution units
33 - fsl,descriptor-types-mask : The bitmask representing what descriptors
/linux-4.4.14/Documentation/sysctl/
DREADME20 1. you get what you pay for
50 - knowledge of what all those values mean
/linux-4.4.14/drivers/hid/usbhid/
DKconfig58 This is almost certainly not what you want. This is mostly
74 This is almost certainly not what you want. This is mostly
/linux-4.4.14/Documentation/devicetree/bindings/metag/
Dmeta.txt3 This binding specifies what properties must be available in the device tree
/linux-4.4.14/arch/arm/firmware/
DKconfig27 Say n if you don't know what this is about.
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-davinci.txt3 This file provides information, what the device node for the
/linux-4.4.14/Documentation/input/
Diforce-protocol.txt2 This document describes what I managed to discover about the protocol used to
4 from Immerse. That's why you should not trust what is written in this
11 send data to your I-Force device based on what you read in this document.
242 3. Play the effect, and watch what happens on the spy screen.
/linux-4.4.14/Documentation/networking/
Ddecnet.txt16 CONFIG_PROC_FS (to see what's going on)
108 There is a list of what the other files under /proc/sys/net/decnet/ do
114 pages for details on what the various options do) or through the iproute2
135 Here is a quick guide of what to look for in order to know if your DECnet
168 you can do to help me work out exactly what it is that is wrong. Useful
229 documentation above and beyond what was previously publicly available.
Dipddp.txt18 EtherTalk and PPPTalk. The only limit on the protocol is that of what
32 select what mode you want it to run in via a module loading param.
Dnf_conntrack-sysctl.txt117 Be conservative in what you do, be liberal in what you accept from others.
Dtlan.txt58 interface. This is also what to do if you want to use the BNC
67 to force 100Mbs operation. (I'm not sure what will happen
/linux-4.4.14/sound/isa/sb/
Dsb16_main.c670 static int snd_sb16_set_dma_mode(struct snd_sb *chip, int what) in snd_sb16_set_dma_mode() argument
673 if (snd_BUG_ON(what)) in snd_sb16_set_dma_mode()
677 if (what == 0) { in snd_sb16_set_dma_mode()
679 } else if (what == 1) { in snd_sb16_set_dma_mode()
681 } else if (what == 2) { in snd_sb16_set_dma_mode()
/linux-4.4.14/drivers/hwtracing/stm/
DKconfig18 If you don't know what this is, say N.
/linux-4.4.14/Documentation/video4linux/bttv/
DTHANKS20 - Hauppauge for telling how the sound input is selected and what components
/linux-4.4.14/Documentation/power/
Dtricks.txt26 When you make it work, try to find out what exactly was it that broke
Dinterface.txt5 userspace, regardless of what architecture or platform one is
10 returns what states are supported, which is hard-coded to 'freeze',
/linux-4.4.14/include/linux/ceph/
Dmon_client.h113 const char *what, u64 *newest);
/linux-4.4.14/drivers/staging/rtl8188eu/
DTODO12 - figure out what to do with this code in rtw_recv_indicatepkt():
/linux-4.4.14/drivers/uio/
DKconfig11 If you don't know what to do here, say N.
38 If you don't know what to do here, say N.
55 If you don't know what to do here, say N.
/linux-4.4.14/Documentation/cpuidle/
Dgovernor.txt11 cpuidle governor is policy routine that decides what idle state to enter at
/linux-4.4.14/Documentation/wimax/
DREADME.wimax14 Because currently there is only one and we don't know what would be the
80 what is printed and the available levels, check the source. The code
/linux-4.4.14/Documentation/development-process/
D8.Conclusion57 project is no more than the sum of what its contributors put into it. The
60 working to make it better. The kernel is a premier example of what can be
D6.Followthrough29 will not keep them from asking a fundamental question: what will it be
54 understand what the reviewer is trying to say. If possible, fix the things
60 explain what is really going on. If you have a technical objection to a
84 through list archives to familiarize themselves with what was said last
165 the problems if at all possible. That's what the stabilization period is
191 possible, tell the author what changes need to be made to make the patch
D5.Posting44 benchmarks showing what the impact (or benefit) of your change is; a
69 on the area of your patch and what is going on elsewhere, basing a patch
91 verified to do what it says it does.
136 - A one-line description of what the patch does. This message should be
147 what the patch does and why it should be applied to the kernel.
192 detail in the SubmittingPatches document; what follows here is a brief
245 embodiment of a fair amount of thought about what kernel patches should
/linux-4.4.14/Documentation/filesystems/nfs/
Dfault_injection.txt40 The NFS server keeps a list of what files are currently opened and who
45 The NFS server keeps a list of what files are currently locked in the VFS.
Dnfsd-admin-interfaces.txt33 For more detail about files under nfsd/ and what they control, see
/linux-4.4.14/arch/sh/cchips/
DKconfig35 Do not change this unless you know what you are doing.
/linux-4.4.14/Documentation/misc-devices/
Dics932s40120 frequency. If spread spectrum mode is enabled, the driver also reports by what
/linux-4.4.14/Documentation/s390/
Dconfig3270.sh51 echo what=config > $P
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Defm32-spi.txt16 If this property is not provided, keeping what is
/linux-4.4.14/fs/ceph/
DKconfig40 If you don't know what Access Control Lists are, say N
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.txt15 - regulator-type : Specifies what is being regulated, must be either
/linux-4.4.14/fs/bfs/
DKconfig15 If you don't know what this is about, say N.
/linux-4.4.14/net/unix/
DKconfig20 Say Y unless you know what you are doing.
/linux-4.4.14/fs/befs/
DKconfig16 If you don't know what this is about, say N.
/linux-4.4.14/drivers/staging/iio/Documentation/
Dtrigger.txt22 triggers to keep track of what they have created.
/linux-4.4.14/Documentation/aoe/
Dudev.txt1 # These rules tell udev what device nodes to create for aoe support.
/linux-4.4.14/drivers/pci/
DKconfig22 If you don't know what to do here, say Y.
35 problem with PCI support and want to see more of what is going on.
/linux-4.4.14/Documentation/laptops/
Dsony-laptop.txt15 subsystem. See the logs of /proc/bus/input/devices to find out what those
120 Your mission, should you accept it, is to try finding out what
122 files and find out what is the impact on your laptop.
/linux-4.4.14/Documentation/cpu-freq/
Duser-guide.txt133 what speed the processor shall run within the boundaries. One such
135 a yet-to-implement userspace program - to decide what specific speed
166 scaling_driver : this file shows what cpufreq driver is
Dgovernors.txt47 How to decide what frequency within the CPUfreq policy should be used?
70 / what target_freq to set within
119 what to do about the frequency. Typically this is set to values of
143 up_threshold: defines what the average CPU usage between the samplings
203 freq_step: this describes what percentage steps the cpu freq should be
/linux-4.4.14/sound/sparc/
Dcs4231.c443 unsigned int what, int on) in cs4231_dma_trigger() argument
448 if (what & CS4231_PLAYBACK_ENABLE) { in cs4231_dma_trigger()
460 if (what & CS4231_RECORD_ENABLE) { in cs4231_dma_trigger()
483 unsigned int what = 0; in snd_cs4231_trigger() local
489 what |= CS4231_PLAYBACK_ENABLE; in snd_cs4231_trigger()
492 what |= CS4231_RECORD_ENABLE; in snd_cs4231_trigger()
499 cs4231_dma_trigger(substream, what, 1); in snd_cs4231_trigger()
500 chip->image[CS4231_IFACE_CTRL] |= what; in snd_cs4231_trigger()
502 cs4231_dma_trigger(substream, what, 0); in snd_cs4231_trigger()
503 chip->image[CS4231_IFACE_CTRL] &= ~what; in snd_cs4231_trigger()
/linux-4.4.14/arch/cris/boot/compressed/
DREADME13 They can also be catted together and compressed with gzip, which is what
/linux-4.4.14/drivers/usb/wusbcore/
DKconfig38 CBA support and want to see more of what is going on.
/linux-4.4.14/arch/h8300/lib/
Dmodsi3.S25 ; examine what the sign should be
Dmoddivsi3.S25 ; examine what the sign should be
/linux-4.4.14/fs/hfsplus/
DKconfig31 If you don't know what Access Control Lists are, say N
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx-pinctrl.txt47 what pinmux functions this SoC supports.
50 The function node's name should represent well about what function
Dberlin,pinctrl.txt13 Be aware the Marvell Berlin datasheets use the keyword 'mode' for what
Dfsl,mxs-pinctrl.txt29 different configuration than what is defined in group node. The binding
120 adjusting the configuration for pins card-detection and clock from what group
/linux-4.4.14/Documentation/timers/
Dtimers-howto.txt73 msleep(1~20) may not do what the caller intends, and
91 be balanced with what is an acceptable upper bound on
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME33 The file README.FPE contains a description of what has been implemented
34 so far in the emulator. The file TODO contains a information on what
/linux-4.4.14/Documentation/arm/
DInterrupts93 - flags indicating what we can do with this IRQ (valid, probe,
103 The "level" handler is what we currently have - its pretty simple.
111 So, what's changed?
DREADME45 explanation as to what the patch does and why it is needed.
53 the problem, what you were doing, etc.
135 I've just got 240K/s off it (a dd with bs=128k); thats about half of what
/linux-4.4.14/Documentation/usb/
Dgadget_configfs.txt26 Creating a gadget means deciding what configurations there will be
300 which can be read-only or read-write, depending on what they represent.
327 two functions to decide what they actually do.
375 4. Each USB function naturally has its own view of what it wants
/linux-4.4.14/drivers/pinctrl/
Dcore.c1339 static int pinctrl_pins_show(struct seq_file *s, void *what) in pinctrl_pins_show() argument
1374 static int pinctrl_groups_show(struct seq_file *s, void *what) in pinctrl_groups_show() argument
1419 static int pinctrl_gpioranges_show(struct seq_file *s, void *what) in pinctrl_gpioranges_show() argument
1452 static int pinctrl_devices_show(struct seq_file *s, void *what) in pinctrl_devices_show() argument
1494 static int pinctrl_maps_show(struct seq_file *s, void *what) in pinctrl_maps_show() argument
1531 static int pinctrl_show(struct seq_file *s, void *what) in pinctrl_show() argument
/linux-4.4.14/drivers/lightnvm/
DKconfig15 only do this if you know what you are doing.
/linux-4.4.14/arch/mips/sgi-ip22/
DPlatform25 # Simplified: what IP22 does at 128MB+ in ksegN, IP28 does at 512MB+ in xkphys
/linux-4.4.14/Documentation/vm/
D00-INDEX16 - explains what hwpoison is
/linux-4.4.14/fs/9p/
DKconfig31 If you don't know what Access Control Lists are, say N
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Datmel-sama5d4-wdt.txt21 not what you want.
Datmel-wdt.txt34 not what you want.
/linux-4.4.14/Documentation/devicetree/bindings/net/
Ddavinci_emac.txt3 This file provides information, what the device node
Dsti-dwmac.txt5 and what is needed on STi platforms to program the stmmac glue logic.
/linux-4.4.14/sound/pci/
Dens1370.c817 unsigned int what = 0; in snd_ensoniq_trigger() local
821 what |= ES_P1_PAUSE; in snd_ensoniq_trigger()
824 what |= ES_P2_PAUSE; in snd_ensoniq_trigger()
831 ensoniq->sctrl |= what; in snd_ensoniq_trigger()
833 ensoniq->sctrl &= ~what; in snd_ensoniq_trigger()
841 unsigned int what = 0; in snd_ensoniq_trigger() local
845 what |= ES_DAC1_EN; in snd_ensoniq_trigger()
848 what |= ES_DAC2_EN; in snd_ensoniq_trigger()
851 what |= ES_ADC_EN; in snd_ensoniq_trigger()
857 ensoniq->ctrl |= what; in snd_ensoniq_trigger()
[all …]
/linux-4.4.14/sound/drivers/
DKconfig52 what you want. To make this driver play nicely with other
63 Say Y only if you really know what you do.
107 If you don't know what MIDI is, say N here.
/linux-4.4.14/fs/ext2/
DKconfig32 If you don't know what Access Control Lists are, say N
/linux-4.4.14/drivers/usb/serial/
Dwhiteheat.h163 __u8 what; /* bit pattern of what to purge */ member
/linux-4.4.14/arch/alpha/
DKconfig.debug40 order to debug the code. Say Y unless you know what you are doing.
/linux-4.4.14/drivers/media/i2c/smiapp/
Dsmiapp-quirk.c54 smiapp_reg_limits[limit].what, val, val); in smiapp_replace_limit()
Dsmiapp.h134 char *what; member
/linux-4.4.14/drivers/pps/
DKconfig30 problem with PPS support and want to see more of what is going on.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmfd.txt24 probe registers to figure out what child devices exist etc, this should not
/linux-4.4.14/arch/arm/kernel/
Dhyp-stub.S60 strne \reg1, [\reg2, \reg3] @ record what happened and give up
/linux-4.4.14/arch/powerpc/
DKconfig42 can manage. Virtual interrupt numbers are what you see in
582 Say N unless you know what you are doing.
793 # Platforms that what PCI turned unconditionally just do select PCI
877 Unless you know what you are doing, say N here.
892 Say N here unless you know what you are doing.
908 Say N here unless you know what you are doing.
964 Say N here unless you know what you are doing.
979 Say N here unless you know what you are doing.
993 Say N here unless you know what you are doing.
1016 Say N here unless you know what you are doing.
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt15 what is going on within the system. There are a large number of methods for
68 call. The following is an example that reports every 5 seconds what processes
145 to know what the standard deviation is. By and large, this is left to the
218 There may also be a requirement to identify what functions within a program
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt126 see what code gcc generates:
155 memory. But what does the .section stuff do?????
183 file. But first we want to find out what happened to our code in the
260 So, what actually happens if a fault from kernel mode with no suitable
/linux-4.4.14/security/smack/
DKconfig26 identify which rules are necessary and what accesses
/linux-4.4.14/scripts/coccinelle/null/
Dkmerr.cocci4 /// in determining what the error handling code for the call to kmalloc etc
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Drcar-gen2-phy.txt3 This file provides information on what the device node for the R-Car generation
/linux-4.4.14/Documentation/arm/SA1100/
DADSBitsy37 - 16bpp mode requires a different cable than what ships with the board.
/linux-4.4.14/Documentation/devicetree/bindings/iio/
Dst-sensors.txt4 SPI devices, all sharing the same device tree descriptions no matter what
/linux-4.4.14/arch/cris/arch-v32/lib/
Dchecksum.S47 ;; to prepare for what is needed after mloop.
/linux-4.4.14/Documentation/i2c/busses/
Di2c-sis63021 what your BIOS use). DANGEROUS! This should be a bit
/linux-4.4.14/arch/sparc/mm/
Dsrmmu.c751 int what; /* 0 = normal-pte, 1 = pmd-level pte, 2 = pgd-level pte */ in srmmu_inherit_prom_mappings() local
766 what = 0; in srmmu_inherit_prom_mappings()
771 what = 1; in srmmu_inherit_prom_mappings()
776 what = 2; in srmmu_inherit_prom_mappings()
780 if (what == 2) { in srmmu_inherit_prom_mappings()
801 if (what == 1) { in srmmu_inherit_prom_mappings()
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt22 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
23 ACPI and what ACPI can expect of Linux.
42 -- ACPI’s OSPM defines a power management model that constrains what the
78 in place. DT does exactly what Linux needs it to when working with vertically
79 integrated devices, but there are no good processes for supporting what the
81 really just duplicates something that already works. ACPI already does what
220 invoke the method and not concern itself with what the method needs to do
222 by changing what the ACPI method does, and not the driver.
271 what has been previously defined.
/linux-4.4.14/Documentation/hwmon/
Dabituguru-datasheet4 First of all, what I know about uGuru is no fact based on any help, hints or
33 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two
95 This step can be skipped, but it is undetermined what happens if the uGuru has
197 seem to know (be programmed with) what kindoff sensor is attached see Sensor
232 Note with some trickery this can be used to find out what kinda sensor is
Duserspace-tools28 2) run sensors-detect script, it will tell you what modules you need to load.
/linux-4.4.14/net/dccp/
DKconfig49 what was just said, you don't need it: say N.
/linux-4.4.14/fs/jfs/
DKconfig22 If you don't know what Access Control Lists are, say N
/linux-4.4.14/drivers/video/fbdev/i810/
Di810_accel.c196 int rop, int what, int blit_bpp, in color_blit() argument
207 PUT_RING(what); in color_blit()
/linux-4.4.14/net/phonet/
Dpn_dev.c294 static int phonet_device_notify(struct notifier_block *me, unsigned long what, in phonet_device_notify() argument
299 switch (what) { in phonet_device_notify()
/linux-4.4.14/arch/cris/arch-v10/drivers/
DKconfig427 you know exactly what you are doing. The only valid reason
525 This is a bitmask with information of what bits in PA that a user
535 This is a bitmask with information of what bits in PA that a user
545 This is a bitmask with information of what bits in PB that a user
555 This is a bitmask with information of what bits in PB that a user
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-api.txt145 available to ask what the device can do:
154 options a flags describing what the device supports
156 the options field can have the following bits set, and describes what
/linux-4.4.14/Documentation/virtual/kvm/
Dppc-pv.txt12 This is what the PPC PV interface helps with. It takes privileged instructions
107 of something. This is what we call "flags".
178 Some instructions require more logic to determine what's going on than a load
/linux-4.4.14/Documentation/m68k/
DREADME.buddha89 (what for? Write to me if it's necessary!).
102 determine what driver has to serve the INT2. Buddha and
176 what you have selected in the speed register:
/linux-4.4.14/Documentation/scsi/
Din2000.txt65 in2000.c file to get an understanding of what it's all
116 reselect. The driver defaults to what I'm calling
138 to see what happens: my tests showed little difference either way.
/linux-4.4.14/arch/mips/mm/
Dinit.c479 void free_init_pages(const char *what, unsigned long begin, unsigned long end) in free_init_pages() argument
490 printk(KERN_INFO "Freeing %s: %ldk freed\n", what, (end - begin) >> 10); in free_init_pages()
/linux-4.4.14/Documentation/driver-model/
Doverview.txt43 Other bus layers are encouraged to do what has been done for the PCI layer.
57 front of the pci_dev structure. This is to make people think about what
/linux-4.4.14/
DREADME4 as they tell you what this is all about, explain how to install the
5 kernel, and what to do if something goes wrong.
48 drivers for example. See Documentation/00-INDEX for a list of what
330 - In all bug-reports, *please* tell what kernel you are talking about,
331 how to duplicate the problem, and what your setup is (use your common
362 look up what the EIP value means. The hex value as such doesn't help
/linux-4.4.14/sound/isa/wss/
Dwss_lib.c485 unsigned int what; in snd_wss_trigger() local
500 what = 0; in snd_wss_trigger()
503 what |= CS4231_PLAYBACK_ENABLE; in snd_wss_trigger()
506 what |= CS4231_RECORD_ENABLE; in snd_wss_trigger()
512 chip->image[CS4231_IFACE_CTRL] |= what; in snd_wss_trigger()
514 chip->trigger(chip, what, 1); in snd_wss_trigger()
516 chip->image[CS4231_IFACE_CTRL] &= ~what; in snd_wss_trigger()
518 chip->trigger(chip, what, 0); in snd_wss_trigger()
/linux-4.4.14/Documentation/devicetree/bindings/
DABI.txt7 "That still leaves the question of, what does a stable binding look
/linux-4.4.14/net/xfrm/
DKconfig68 Say Y unless you know what you are doing.
/linux-4.4.14/arch/arc/include/asm/
Dentry-arcv2.h115 ; Now do what ISR prologue does (manually save r12, sp, fp, gp, r25)
/linux-4.4.14/Documentation/video4linux/
DREADME.saa713441 forget to tell me what it changes / which problem it fixes / whatever

1234