/linux-4.1.27/lib/mpi/ |
D | mpicoder.c | 171 #error please implement for this limb size. in mpi_get_buffer() 217 #error please implement for this limb size. in mpi_set_buffer() 247 #error please implement for this limb size. in mpi_set_buffer()
|
/linux-4.1.27/Documentation/cpu-freq/ |
D | index.txt | 24 cpu-drivers.txt - How to implement a new cpufreq processor driver 27 implement them?
|
D | intel-pstate.txt | 12 setpolicy() instead of target(). Scaling drivers that implement 13 setpolicy() are assumed to implement internal governors by the cpufreq
|
D | pcc-cpufreq.txt | 120 Currently, certain HP ProLiant platforms implement the PCC interface. On those 200 PCC do not implement SW_ALL. So OSPM doesn't need to perform any coordination
|
D | user-guide.txt | 135 a yet-to-implement userspace program - to decide what specific speed
|
/linux-4.1.27/include/asm-generic/ |
D | pgalloc.h | 7 #error need to implement an architecture specific asm/pgalloc.h
|
D | tlbflush.h | 9 #error need to implement an architecture specific asm/tlbflush.h
|
/linux-4.1.27/Documentation/trace/ |
D | ftrace-design.txt | 24 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. 109 mcount function to check ftrace graph function pointers, as well as implement 163 For information on how to implement prepare_ftrace_return(), simply look at the 227 of addresses of the system calls, implement an arch_syscall_addr to return 231 implement arch_syscall_match_sym_name with the appropriate logic to return 250 Once those are out of the way, you will need to implement: 298 implement your own stuff in assembly: 369 - implement:
|
/linux-4.1.27/drivers/staging/rts5208/ |
D | TODO | 4 - We will use the stack in drivers/mmc to implement
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | nfs41-server.txt | 23 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing 28 the operations that are mandatory to implement (REQ), optional 29 (OPT), and NFSv4.0 operations that are required not to implement (MNI) 155 persist across client reboots). Thus we need not implement this for
|
D | rpc-server-gss.txt | 6 implement RPCGSS authentication in kernel RPC servers such as the NFS
|
D | pnfs.txt | 63 table which are called by the nfs-client pnfs-core to implement the
|
D | Exporting | 53 To implement these features, the dcache has:
|
/linux-4.1.27/Documentation/ptp/ |
D | ptp.txt | 30 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-4.1.27/Documentation/ioctl/ |
D | 00-INDEX | 12 - how to implement and register device/driver ioctl calls
|
/linux-4.1.27/Documentation/hwmon/ |
D | emc1403 | 41 The chips implement three limits for each sensor: low (tempX_min), high 42 (tempX_max) and critical (tempX_crit.) The chips also implement an
|
D | adt7411 | 16 be other chips that implement this interface.
|
D | tmp421 | 34 implement one local and up to one (TMP421, TMP441), up to two (TMP422,
|
D | nct6683 | 18 The chips implement up to shared 32 temperature and voltage sensors.
|
D | tmp401 | 34 TMP431, TMP432 and TMP435 chips. These chips implement one or two remote
|
D | adt7470 | 16 be other chips that implement this interface.
|
D | adm1021 | 71 ADM1021-clones implement two temperature sensors. One of them is internal,
|
D | w83627ehf | 53 The chips implement 3 to 4 temperature sensors (9 for NCT6775F and NCT6776F),
|
D | lm90 | 236 Semiconductor chips (NCT1008) do not implement the SMBus alert protocol
|
D | sysfs-interface | 7 implement the standard sysfs interface described in this document. 30 will have to implement conversion, labeling and hiding of inputs. For
|
D | dme1737 | 46 1 internal) and up to 6 fan speeds fan[1-6]. Additionally, the chips implement
|
/linux-4.1.27/arch/arm/nwfpe/ |
D | ChangeLog | 82 * single_cpdo.c - implement URD, NRM 83 * double_cpdo.c - implement URD, NRM 84 * extended_cpdo.c - implement URD, NRM
|
/linux-4.1.27/Documentation/filesystems/ |
D | dax.txt | 28 To support DAX in your block driver, implement the 'direct_access' 42 implement direct_access. Equally, if your device can occasionally 44 implement direct_access.
|
D | seq_file.txt | 38 * A set of canned file_operations which implement most operations on 69 Modules implementing a virtual file with seq_file must implement a simple 72 implement - but the interpretation of that position is up to the iterator 110 The next function to implement is called, amazingly, next(); its job is to 222 creation of a set of file_operations which implement the operations on that 224 most of the work. The virtual file author still must implement the open()
|
D | inotify.txt | 32 thousand times is silly. If we can implement user-space's preferences 75 device file or a family of new system calls. We decided to implement a
|
D | spufs.txt | 10 The SPU file system is used on PowerPC machines that implement the Cell 294 The spu_run system call is used on PowerPC machines that implement the 376 spu_run is meant to be used from libraries that implement a more 388 The code does not yet fully implement all features lined out here. 418 The spu_create system call is used on PowerPC machines that implement 493 spu_create is meant to be used from libraries that implement a more 510 The code does not yet fully implement all features lined out here.
|
D | relay.txt | 21 buffer data. The relay interface doesn't implement any form of data 92 you'll have to implement communication between userspace and kernel, 263 easily implement random-access-on-buffer-boundary schemes, which can 340 To implement 'no-overwrite' mode, the userspace client would provide
|
D | sysv-fs.txt | 189 * How to implement symbolic links such that the host fsck doesn't scream:
|
D | ntfs.txt | 77 compatibility, we implement access to files using their short file names if 90 file and we do not implement directory modifications yet. 98 the file and we do not implement directory modifications yet.
|
D | coda.txt | 184 To implement Coda on these systems some reverse engineering of the 214 The FS layer for Coda must expose and implement several interfaces. 426 Unix the CodaCred has proven sufficient to implement good security 1017 deal with the Windows case. It might be best to implement two 1227 NNOOTTEE Linux does not implement this call. It should. 1517 zapfile routine takes different arguments. Linux does not implement
|
D | debugfs.txt | 49 implement the file's behavior. At a minimum, the read() and/or write()
|
D | romfs.txt | 167 solutions: implement write access as a compile-time option, or a new,
|
D | autofs4-mount-control.txt | 119 implement an isolated operation it was decided to re-implement the
|
D | fiemap.txt | 177 File systems wishing to support fiemap must implement a ->fiemap callback on
|
D | sysfs.txt | 123 When a subsystem defines a new attribute type, it must implement a
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-bus-hsi | 11 the protocols available in the system. Bus drivers implement
|
D | sysfs-class-net | 100 Note: This attribute is only valid for interfaces that implement 207 Note: this attribute is only valid for interfaces that implement
|
/linux-4.1.27/Documentation/ |
D | DMA-attributes.txt | 31 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, 67 Since it is optional for platforms to implement
|
D | rfkill.txt | 61 Drivers for radio transmitters normally implement an rfkill driver. 63 Platform drivers might implement input devices if the rfkill button is just 65 implement an rfkill driver instead. This also applies if the platform provides
|
D | IRQ-domain.txt | 204 the hierarchy. A child irq_chip may implement a required action by 215 2) Optionally implement irq_domain_ops.activate and 217 3) Optionally implement an irq_chip to manage the interrupt controller 219 4) No need to implement irq_domain_ops.map and irq_domain_ops.unmap,
|
D | pwm.txt | 89 Currently there are two ways to implement pwm drivers. Traditionally 91 to implement the pwm_*() functions itself. This means that it's impossible
|
D | hsi.txt | 45 implement a protocol used on the HSI interface. These client drivers can
|
D | irqflags-tracing.txt | 27 and then a couple of functional changes are needed as well to implement
|
D | SAK.txt | 39 systems which implement C2 level security. This author does not
|
D | unshare.txt | 48 addition to the set of available primitives on Linux that implement 63 unshare can be used to implement polyinstantiated directories using 95 stable code to implement a new feature that may not get exercised
|
D | cputopology.txt | 38 To implement it in an architecture-neutral way, a new source file,
|
D | mailbox.txt | 8 proprietary and implement non-standard protocol. So even if two
|
D | atomic_ops.txt | 7 maintainers on how to implement atomic counter, bitops, and spinlock 25 The first operations to implement for atomic_t's are the initializers and 314 kernel. It is the use of atomic counters to implement reference
|
D | local_ops.txt | 7 to implement them for any given architecture and shows how they can be used
|
D | media-framework.txt | 277 the media controller does not implement power management. However, the 308 Entity drivers must implement the link_setup operation if any of their links
|
D | SubmittingDrivers | 66 If you need to implement a common API over Linux and NT
|
D | eisa.txt | 30 EISA code. This is the part to implement in order to have EISA
|
D | circular-buffers.txt | 9 Linux provides a number of features that can be used to implement circular
|
D | pinctrl.txt | 737 All the above functions are mandatory to implement for a pinmux driver. 758 controlled e.g. muxed in. Instead, implement a proper gpiolib driver and have 768 For this reason there are two functions a pin control driver can implement 777 GPIO pin shall be used for input or output you can implement the 1319 and the use cases involve multiplexing, you MUST implement the pin controller
|
D | static-keys.txt | 145 There are a few functions and macros that architectures must implement in order
|
D | coccinelle.txt | 61 Note that not all semantic patches implement all modes. For easy use
|
D | sysfs-rules.txt | 13 implement this and users are encouraged to plug, if possible, into the
|
D | Changes | 255 which is not always easy, particularly when trying to implement
|
D | robust-futexes.txt | 216 Architectures need to implement the new futex_atomic_cmpxchg_inatomic()
|
/linux-4.1.27/Documentation/ABI/removed/ |
D | raw1394 | 7 to implement sensible device security policies, and its low level
|
/linux-4.1.27/Documentation/usb/ |
D | authorization.txt | 7 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-4.1.27/drivers/scsi/arm/ |
D | Kconfig | 21 implement this properly, so the safe answer is N. 31 don't implement it properly, so the safe answer is N.
|
/linux-4.1.27/net/nfc/ |
D | Kconfig | 25 This is needed by NFC chipsets whose firmware only implement
|
/linux-4.1.27/Documentation/ide/ |
D | ChangeLog.ide-floppy.1996-2002 | 28 * implement formatting. IOCTls begin with 0x4600, 32 * do not implement IDEFLOPPY_CAPABILITIES_PAGE, and
|
D | ide-tape.txt | 58 implement the ATAPI overlap protocol, which is used for the
|
/linux-4.1.27/security/ |
D | Kconfig | 49 implement socket and networking access controls. 58 implement per-packet access controls based on labels 71 implement pathname based access controls.
|
/linux-4.1.27/arch/x86/include/asm/ |
D | pvclock.h | 56 #error implement me! in pvclock_scale_delta()
|
/linux-4.1.27/fs/fuse/ |
D | Kconfig | 4 With FUSE it is possible to implement a fully functional filesystem
|
/linux-4.1.27/tools/testing/selftests/powerpc/primitives/ |
D | load_unaligned_zeropad.c | 64 #error implement UCONTEXT_NIA
|
/linux-4.1.27/Documentation/arm/ |
D | swp_emulation | 24 atomicity. If your system does not implement a global monitor, this option can
|
D | kernel_user_helpers.txt | 23 User space is expected to bypass those helpers and implement those things
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/ |
D | vexpress-scc.txt | 4 Test chips for ARM Versatile Express platform implement SCC (Serial
|
/linux-4.1.27/drivers/net/wireless/ti/wlcore/ |
D | Kconfig | 8 Each chipset family needs to implement its own lower-level module
|
/linux-4.1.27/drivers/staging/media/bcm2048/ |
D | TODO | 5 The main thing you need to do is to implement all the controls using the
|
/linux-4.1.27/Documentation/devicetree/bindings/net/ |
D | phy.txt | 18 PHYs that implement IEEE802.3 clause 22 or IEEE802.3 clause 45
|
/linux-4.1.27/Documentation/leds/ |
D | leds-class.txt | 62 support this feature, a LED driver can optionally implement the 65 will check and implement software fallback if necessary.
|
D | ledtrig-transient.txt | 10 gets deactivated. There is no provision for one time activation to implement
|
/linux-4.1.27/Documentation/xtensa/ |
D | atomctl.txt | 16 which can implement RCW transactions. For FPGA cards with an External
|
/linux-4.1.27/Documentation/scsi/ |
D | ChangeLog.arcmsr | 57 ** 1.implement PCI-Express error recovery function and AER capability 58 ** 2.implement the selection of ARCMSR_MAX_XFER_SECTORS_B=4096
|
D | bnx2fc.txt | 70 ** Broadcom FCoE capable devices implement a DCBX/LLDP client on-chip. Only one
|
D | libsas.txt | 173 A SAS LLDD should also implement at least one of the Task 193 A SAS LLDD should implement at least one of those. 308 This function should implement the Execute Command SCSI RPC,
|
D | scsi_eh.txt | 165 LLDD's can implement SCSI EH actions in one of the following two 169 LLDD can implement fine-grained EH callbacks and let SCSI
|
D | BusLogic.txt | 135 BusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so 149 firmware version is known not to implement it correctly, or whenever a tagged 423 Tagged Queuing on Target Devices that do not implement it correctly. The
|
D | ChangeLog.ncr53c8xx | 32 that implement a weak memory ordering. 460 - implement a minimal done queue (1 entry :-) ).
|
/linux-4.1.27/Documentation/i2c/ |
D | functionality | 60 When you write a new adapter driver, you will have to implement a 121 i2c-core will transparently implement SMBus transactions on top of I2C
|
D | summary | 21 implement all the common SMBus protocol semantics or messages.
|
D | instantiating-devices | 175 * The I2C device driver must implement the detect() method, which 244 drivers implement. Being implemented in i2c-core rather than in each
|
D | slave-interface | 131 * implement calls to register/unregister the slave and add those to the
|
D | smbus-protocol | 236 * I2C drivers for devices which can trigger SMBus alerts should implement
|
D | dev-interface | 200 directly. This means that I2C bus drivers don't need to implement
|
/linux-4.1.27/drivers/mtd/chips/ |
D | Kconfig | 177 sets which a CFI-compliant chip may claim to implement. This code 187 sets which a CFI-compliant chip may claim to implement. This code 197 sets which a CFI-compliant chip may claim to implement. This code
|
/linux-4.1.27/Documentation/networking/caif/ |
D | Linux-CAIF.txt | 68 - Clients must implement CAIF layer to consume/produce 162 Net device and Socket implement the 'receive()' function defined by
|
D | spi_porting.txt | 26 In order to implement a SPI device you will, as a minimum, 27 need to implement the following
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-piix4 | 70 The PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use 76 The AMD SB700, SB800, SP5100 and Hudson-2 chipsets implement two
|
D | i2c-viapro | 73 this driver doesn't implement it yet.
|
/linux-4.1.27/Documentation/w1/masters/ |
D | omap-hdq | 14 The HDQ/1-Wire module of TI OMAP2430/3430 platforms implement the hardware
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-nice-design.txt | 7 Unfortunately that was not that easy to implement under the old 89 it was possible to implement better and more consistent nice +19
|
D | sched-deadline.txt | 46 from the beginning of the period. In order to implement this behaviour, 297 and the cpuset mechanism is used to implement partitioned scheduling (see
|
/linux-4.1.27/lib/ |
D | atomic64_test.c | 134 #warning Please implement atomic64_dec_if_positive for your architecture and select the above Kconf… in test_atomic64()
|
D | Kconfig | 489 It is used to implement RSA digital signature verification,
|
/linux-4.1.27/Documentation/networking/ |
D | x25.txt | 7 implement LAPB on the card itself, and unintelligent ones that simply do
|
D | openvswitch.txt | 6 used to implement a plain Ethernet switch, network device bonding, 111 that the kernel does not implement will simply result in additional flow setups. 164 did not already implement VLAN parsing. Instead, it just interpreted
|
D | nfc.txt | 74 Generic netlink is used to implement the interface to the control operations.
|
D | timestamping.txt | 201 implement retransmissions. 203 It is essential that all timestamps implement the same semantics, 216 implement and reason about. An implementation that has to take into
|
D | ieee802154.txt | 64 See the header include/net/ieee802154_netdev.h. You have to implement Linux
|
D | rds.txt | 122 to implement async I/O. 243 is much easier to implement than some finer-grained
|
D | netdev-features.txt | 134 NETIF_F_LLTX should be set in drivers that implement their own locking in
|
D | fib_trie.txt | 78 to implement level compression.
|
D | stmmac.txt | 284 o stmmac_main.c: to implement the main network device driver; 288 o stmmac_ethtool.c: to implement the ethtool support;
|
D | baycom.txt | 130 The modem simply does not provide enough information to implement
|
D | README.sb1000 | 96 You may also wish to modify the firewall script to implement a different
|
/linux-4.1.27/Documentation/s390/ |
D | driver-model.txt | 218 not need to implement anything beyond normal removal routines). 225 To implement a ccwgroup driver, please refer to include/asm/ccwgroup.h. Keep in 226 mind that most drivers will need to implement both a ccwgroup and a ccw
|
D | DASD | 30 We currently implement one partition per volume, which is the whole
|
D | kvm.txt | 56 implement this one in the future.
|
D | cds.txt | 19 either every single device driver needs to implement the hardware I/O 33 below. Some of them implement common Linux device driver interfaces, while
|
/linux-4.1.27/Documentation/hid/ |
D | hid-transport.txt | 84 required on asynchronous channels, a transport-driver must implement that via 274 The transport driver is free to implement this asynchronously. 296 Perform SET/GET_IDLE request. Only used by USB-HID, do not implement! 302 handle any I/O-related state-tracking themselves. HID core does not implement
|
D | hid-sensor.txt | 4 HID sensor framework provides necessary interfaces to implement sensor drivers,
|
D | uhid.txt | 4 UHID allows user-space to implement HID transport drivers. Please see
|
/linux-4.1.27/Documentation/video4linux/ |
D | v4l2-controls.txt | 5 implement correctly in drivers. But much of the code needed to handle controls 20 The control framework was created in order to implement all the rules of the 233 4) Finally: implement the v4l2_ctrl_ops 261 to do any validation of control values, or implement QUERYCTRL, QUERY_EXT_CTRL 332 that most drivers do not need to implement the g_volatile_ctrl() op. The 335 implement g_volatile_ctrl like this: 347 controls that need to implement g_volatile_ctrl are read-only controls. If they
|
D | soc-camera.txt | 80 supports non-standard pixel format conversion, it should implement a 136 support cropping, it may choose to not implement .s_crop(), but to enable
|
D | README.pvrusb2 | 135 pvrusb2-i2c-chips-*.c - These modules implement the glue logic to 139 implement just the logic that makes sense for a pure V4L
|
D | videobuf | 8 to implement many of the standard POSIX I/O system calls, including read(), 10 implement the bulk of the V4L2 ioctl() calls related to streaming I/O, 182 easy to do that with the same code. To implement read(), the driver need
|
D | v4l2-framework.txt | 242 implement (or leave NULL if it is not applicable). Since sub-devices can do 317 framework, it must implement format related functionality using 662 - prio: keeps track of the priorities. Used to implement VIDIOC_G/S_PRIORITY. 739 In the case of videobuf2 you will need to implement the wait_prepare and 913 for dealing with video buffers. Those methods allow a driver to implement 928 since it is also used to implement priority handling (VIDIOC_G/S_PRIORITY).
|
/linux-4.1.27/Documentation/devicetree/bindings/timer/ |
D | renesas,cmt.txt | 7 are independent. A particular CMT instance can implement only a subset of the
|
/linux-4.1.27/Documentation/PCI/ |
D | pci-error-recovery.txt | 102 A driver does not have to implement all of these callbacks; however, 103 if it implements any, it must implement error_detected(). If a callback 137 All drivers participating in this system must implement this call. 253 >>> The current powerpc implementation does not implement this callback. 264 Powerpc platforms implement two levels of slot reset:
|
/linux-4.1.27/Documentation/laptops/ |
D | disk-shock-protection.txt | 23 conjunction with accelerometers and appropriate software to implement 28 implement a generic disk head parking interface in the Linux kernel.
|
/linux-4.1.27/Documentation/dmaengine/ |
D | provider.txt | 54 implement it in software, or we have a more advanced DMA controller, 239 order to implement the actual logic, now that we described what 243 implement, obviously depend on the transaction types you reported as 281 + tx_submit: A pointer to a function you have to implement,
|
/linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
D | samsung,sysmmu.txt | 27 to implement child devices or sub-devices which are the client devices of the
|
/linux-4.1.27/drivers/bus/ |
D | Kconfig | 68 platform code needs to implement mips_cdmm_phys_base() (see
|
/linux-4.1.27/drivers/ptp/ |
D | Kconfig | 73 implement the skb_tx_timestamp() function.
|
/linux-4.1.27/Documentation/wimax/ |
D | README.wimax | 21 stack will call in order to implement control operations requested by
|
/linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
D | nvidia,tegra20-i2c.txt | 21 Continue Transfer Support. This feature helps to implement M_NO_START
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | hdspm.txt | 102 needed some driver-guru can implement a memory-mapping of mixer 112 implement it here.
|
D | serial-u16550.txt | 74 timing constraints, so it would be a bit more complicated to implement than
|
D | compress_offload.txt | 216 stream, or even implement transcoding capabilities. This routing
|
/linux-4.1.27/drivers/pci/host/ |
D | Kconfig | 78 implement the driver.
|
/linux-4.1.27/Documentation/acpi/ |
D | method-customizing.txt | 66 But each individual write to debugfs can implement a SINGLE
|
D | enumeration.txt | 36 connected to any physical bus we only need to implement a platform driver 74 and implement custom xlate function if needed (usually acpi_dma_simple_xlate()
|
D | video_extension.txt | 4 This driver implement the ACPI Extensions For Display Adapters for
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | firewire-cdev | 43 userland implement different access permission models, some
|
/linux-4.1.27/Documentation/block/ |
D | writeback_cache_control.txt | 60 devices with volatile caches need to implement the support for these
|
D | data-integrity.txt | 21 Current storage controllers and devices implement various protective
|
/linux-4.1.27/Documentation/mmc/ |
D | mmc-async-req.txt | 48 post_req() -- that the host driver may implement in order to move work
|
/linux-4.1.27/drivers/usb/gadget/ |
D | Kconfig | 218 not be able work with that controller, or might need to implement 262 since the kernel itself doesn't implement the OBEX protocol. 294 On hardware that can't implement the full protocol,
|
/linux-4.1.27/Documentation/security/ |
D | IMA-templates.txt | 27 a new data type, developers define the field identifier and implement
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | TODO | 47 k) implement support for security and trusted categories of xattrs
|
/linux-4.1.27/Documentation/cdrom/ |
D | packet-writing.txt | 42 shall implement "true random writes with 2KB granularity", which means
|
D | cdrom-standard.tex | 63 drivers should implement them. Currently (as of the \linux\ 2.1.$x$ 189 drivers. These routines simply implement certain {\em capabilities\/} 393 function through $cdrom_media_changed()$, we can implement separate 458 This function should implement the old corresponding $ioctl()$. For 662 implemented (some drivers implement checking for write-related flags, 702 implement such a user-program for \linux, I came across the 1010 Gerd Knorr, who were the first to implement this interface for SCSI
|
/linux-4.1.27/drivers/usb/gadget/legacy/ |
D | Kconfig | 100 - On hardware can't implement that protocol, a simple CDC subset 180 programs implement a single-configuration USB device, including 276 itself doesn't implement the OBEX protocol.
|
/linux-4.1.27/arch/arm/boot/dts/ |
D | imx6qdl-cubox-i.dtsi | 105 /* IMX6 doesn't implement this yet */
|
D | imx6qdl-hummingboard.dtsi | 108 /* IMX6 doesn't implement this yet */
|
/linux-4.1.27/Documentation/w1/ |
D | w1.generic | 62 What does a w1 master driver need to implement?
|
/linux-4.1.27/Documentation/frv/ |
D | atomic-ops.txt | 6 instruction. Unfortunately, this alone can't be used to implement the following operations:
|
/linux-4.1.27/drivers/net/ethernet/smsc/ |
D | Kconfig | 113 If the arch enables this, it allows the arch to implement various
|
/linux-4.1.27/Documentation/power/ |
D | pm_qos_interface.txt | 23 parameter. The set of parameters implement is defined by pm_qos_power_init() 198 structure should be populated. The routine pointed to by it is should implement
|
D | states.txt | 6 of them depend on the platform support code to implement the low-level details
|
D | userland-swsusp.txt | 93 is needed to implement the suspend-to-both mechanism in which the
|
D | charger-manager.txt | 42 requires tasks other than cm_suspend_again, it may implement its own
|
D | pci.txt | 140 majority of x86-based systems, it is supposed to implement device power 484 PCI device drivers (that don't implement legacy power management callbacks) are 971 drivers implement it at least in the cases where there is a reliable way of 975 To support the PCI runtime PM the driver first needs to implement the 976 runtime_suspend() and runtime_resume() callbacks. It also may need to implement
|
/linux-4.1.27/arch/tile/ |
D | Kconfig | 76 # FIXME: tilegx can implement a more efficient rwsem. 205 to implement the "mboot" Tilera booter.
|
/linux-4.1.27/drivers/firmware/ |
D | Kconfig | 18 not yet implement this feature.
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | srio-rmu.txt | 3 For SRIO controllers that implement the message unit as part of the controller
|
/linux-4.1.27/Documentation/isdn/ |
D | README.avmb1 | 6 The lowlevel interface can be used to implement a CAPI2.0
|
/linux-4.1.27/Documentation/locking/ |
D | rt-mutex-design.txt | 17 decisions that were made to implement PI in the manner that was done. 76 the design that is used to implement PI. 83 mutex - In this document, to differentiate from locks that implement 328 Some architectures implement an atomic cmpxchg (Compare and Exchange). This 387 Note that rt_mutex_setprio is defined in kernel/sched/core.c to implement the 579 does not implement CMPXCHG would always grab the lock (if there's no
|
/linux-4.1.27/Documentation/sound/oss/ |
D | SoundPro | 103 - implement mixer support for surround, loud, digital CD switches.
|
/linux-4.1.27/Documentation/driver-model/ |
D | porting.txt | 322 already set. This allows the drivers to implement their own generic 387 consume. To do this, a bus must implement the 'hotplug' method in
|
/linux-4.1.27/sound/soc/blackfin/ |
D | Kconfig | 134 AC97 codecs which do not implement the slot-16 mode will not function
|
/linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
D | mmc.txt | 2 that requires the respective functionality should implement them using
|
/linux-4.1.27/Documentation/fmc/ |
D | mezzanine.txt | 79 package includes support to implement common parameters by means of
|
/linux-4.1.27/Documentation/serial/ |
D | driver | 140 This is used to implement XON/XOFF flow control and tcflow(). If 141 the serial driver does not implement this function, the tty core
|
/linux-4.1.27/Documentation/watchdog/ |
D | convert_drivers_to_kernel_api.txt | 6 implement the API on its own. Now, as the framework factored out the common
|
D | watchdog-api.txt | 29 drivers implement different, and sometimes incompatible, parts of it.
|
/linux-4.1.27/fs/cramfs/ |
D | README | 146 Option 3 is easy to implement if we don't mind being CPU-inefficient:
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-script-perl.txt | 130 can implement a set of optional functions:
|
/linux-4.1.27/arch/parisc/ |
D | Kconfig | 85 # unless you want to implement ACPI on PA-RISC ... ;-)
|
/linux-4.1.27/Documentation/fb/ |
D | sstfb.txt | 164 - try to implement accel on voodoo2, this board can actually do a
|
D | api.txt | 283 formats. Drivers are also encouraged to implement the FOURCC-based API for RGB
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | pinctrl-single.txt | 50 pinctrl-single,bias-disable. Because pinctrl single driver could implement
|
/linux-4.1.27/arch/arm/mm/ |
D | Kconfig | 412 # There are no CPUs available with MMU that don't implement an ARM ISA: 693 implement a global monitor, this option can cause programs that 836 clock_gettime. Systems that implement the ARM architected
|
/linux-4.1.27/Documentation/cgroups/ |
D | cgroups.txt | 90 mechanisms required to efficiently implement such groups. It has 558 callback can be used to implement reliable state sharing and 621 function, so that the subsystem can implement a rollback. If not, not necessary.
|
/linux-4.1.27/drivers/xen/ |
D | Kconfig | 154 to other domains. This can be used to implement frontend drivers
|
/linux-4.1.27/Documentation/devicetree/bindings/ |
D | xilinx.txt | 89 Some IP cores actually implement 2 or more logical devices. In
|
/linux-4.1.27/drivers/net/usb/ |
D | Kconfig | 197 implement in device firmware. The CDC specifications are available 224 implement in device firmware. The CDC EEM specifications are available
|
/linux-4.1.27/drivers/hid/ |
D | hid-core.c | 1088 static void implement(const struct hid_device *hid, __u8 *report, in implement() function 1272 implement(hid, data, offset + n * size, size, in hid_output_field() 1275 implement(hid, data, offset + n * size, size, in hid_output_field()
|
/linux-4.1.27/Documentation/arm64/ |
D | booting.txt | 62 bootloaders that do not implement this requirement, the uncompressed
|
D | arm-acpi.txt | 53 and an OS is important. Hardware vendors would not be required to implement 443 as closely as possible, and to only implement functionality that complies with
|
/linux-4.1.27/Documentation/dvb/ |
D | README.dvb-usb | 206 root-shells on their machines to implement support for new devices.
|
/linux-4.1.27/Documentation/input/ |
D | input-programming.txt | 266 and implement sparse keycode maps.
|
/linux-4.1.27/Documentation/sound/alsa/soc/ |
D | DPCM.txt | 274 implement :-
|
/linux-4.1.27/arch/m68k/ |
D | Kconfig.cpu | 13 to stand alone CPUs. They implement a subset of the original 68000
|
/linux-4.1.27/Documentation/thermal/ |
D | intel_powerclamp.txt | 128 it is up to the user of this driver to implement algorithms where
|
/linux-4.1.27/Documentation/gpio/ |
D | gpio-legacy.txt | 67 One platform might implement it as simple inline functions accessing chip 68 registers; another might implement it by delegating through abstractions 286 to implement a workaround on signals typically driven by a non-GPIO HW block.
|
/linux-4.1.27/Documentation/powerpc/ |
D | cxl.txt | 44 (AFU). The AFU is used to implement specific functionality behind
|
/linux-4.1.27/Documentation/development-process/ |
D | 3.Early-stage | 172 which are only reviewed when somebody actually tries to implement those
|
/linux-4.1.27/Documentation/crypto/ |
D | asymmetric-keys.txt | 213 given -ENOTSUPP. The subtype may do anything it likes to implement an
|