Home
last modified time | relevance | path

Searched refs:implement (Results 1 – 25 of 222) sorted by relevance

123456789

/linux-3.4.99/drivers/staging/media/solo6x10/
DTODO15 * implement a CID control for motion areas/thresholds
16 * implement CID controls for mozaic areas
19 - implement playback via external sound jack
20 - implement loopback of external sound jack with incoming audio?
21 - implement pause/resume
/linux-3.4.99/drivers/staging/quatech_usb2/
DTODO1 Incomplete list of things that this driver does not yet implement completely or
2 at all. some of these may not be possible to implement because the hardware
5 implement them writing.
/linux-3.4.99/Documentation/trace/
Dftrace-design.txt24 STACKTRACE_SUPPORT - implement save_stack_trace()
25 TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
31 You will need to implement the mcount and the ftrace_stub functions.
133 mcount function to check ftrace graph function pointers, as well as implement
187 For information on how to implement prepare_ftrace_return(), simply look at the
251 of addresses of the system calls, implement an arch_syscall_addr to return
255 implement arch_syscall_match_sym_name with the appropriate logic to return
274 Once those are out of the way, you will need to implement:
322 implement your own stuff in assembly:
331 /* implement HAVE_FUNCTION_TRACE_MCOUNT_TEST if you desire */
[all …]
/linux-3.4.99/Documentation/cpu-freq/
Dindex.txt24 cpu-drivers.txt - How to implement a new cpufreq processor driver
27 implement them?
/linux-3.4.99/include/asm-generic/
Dpgalloc.h7 #error need to implement an architecture specific asm/pgalloc.h
Dtlbflush.h9 #error need to implement an architecture specific asm/tlbflush.h
/linux-3.4.99/lib/mpi/
Dmpicoder.c191 #error please implement for this limb size. in mpi_get_buffer()
237 #error please implement for this limb size. in mpi_set_buffer()
267 #error please implement for this limb size. in mpi_set_buffer()
/linux-3.4.99/Documentation/ptp/
Dptp.txt30 author of a clock driver need only implement the details of
46 implement the basic clock operations.
59 registration method. Clock drivers must implement all of the
/linux-3.4.99/Documentation/ioctl/
D00-INDEX10 - how to implement and register device/driver ioctl calls
/linux-3.4.99/Documentation/
DDMA-attributes.txt31 Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
41 Since it is optional for platforms to implement DMA_ATTR_WRITE_COMBINE,
Drfkill.txt58 Drivers for radio transmitters normally implement an rfkill driver.
60 Platform drivers might implement input devices if the rfkill button is just
62 implement an rfkill driver instead. This also applies if the platform provides
/linux-3.4.99/arch/x86/include/asm/
Dpvclock.h53 #error implement me! in pvclock_scale_delta()
/linux-3.4.99/Documentation/networking/caif/
DLinux-CAIF.txt51 The user of the API has to implement two callbacks for receive
91 - Clients must implement PHY layer to access physical HW
94 - Clients must implement CAIF layer to consume/produce
195 Net device and Socket implement the 'receive()' function defined by
/linux-3.4.99/arch/arm/nwfpe/
DChangeLog82 * single_cpdo.c - implement URD, NRM
83 * double_cpdo.c - implement URD, NRM
84 * extended_cpdo.c - implement URD, NRM
/linux-3.4.99/fs/fuse/
DKconfig4 With FUSE it is possible to implement a fully functional filesystem
/linux-3.4.99/Documentation/ABI/testing/
Dsysfs-bus-hsi11 the protocols available in the system. Bus drivers implement
/linux-3.4.99/Documentation/ABI/removed/
Draw13947 to implement sensible device security policies, and its low level
/linux-3.4.99/Documentation/filesystems/nfs/
Dnfs41-server.txt23 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
67 the operations that are mandatory to implement (REQ), optional
68 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
186 persist across client reboots). Thus we need not implement this for
/linux-3.4.99/drivers/scsi/arm/
DKconfig21 implement this properly, so the safe answer is N.
31 don't implement it properly, so the safe answer is N.
/linux-3.4.99/Documentation/usb/
Dauthorization.txt7 not) in a system. This feature will allow you to implement a lock-down
43 Imagine you want to implement a lockdown so only devices of type XYZ
/linux-3.4.99/Documentation/ide/
DChangeLog.ide-floppy.1996-200228 * implement formatting. IOCTls begin with 0x4600,
32 * do not implement IDEFLOPPY_CAPABILITIES_PAGE, and
/linux-3.4.99/Documentation/filesystems/
Dseq_file.txt38 * A set of canned file_operations which implement most operations on
60 Modules implementing a virtual file with seq_file must implement a simple
63 implement - but the interpretation of that position is up to the iterator
101 The next function to implement is called, amazingly, next(); its job is to
209 creation of a set of file_operations which implement the operations on that
211 most of the work. The virtual file author still must implement the open()
/linux-3.4.99/Documentation/arm/
Dswp_emulation24 atomicity. If your system does not implement a global monitor, this option can
/linux-3.4.99/Documentation/hwmon/
Dtmp42125 and TMP423 temperature sensor chips. These chips implement one local
Dadt741116 be other chips that implement this interface.

123456789