Searched refs:filling (Results 1 – 25 of 45) sorted by relevance
12
| /Linux-v5.4/include/linux/ |
| D | fsl-diu-fb.h | 156 __be32 filling; member
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | trigger.txt | 29 Currently triggers are only used for the filling of software
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | configfs-acpi | 27 after the table has been loaded by filling the aml entry:
|
| D | sysfs-devices-edac | 84 userspace tools in order to display the memory filling layout.
|
| /Linux-v5.4/Documentation/arm/ |
| D | firmware.rst | 12 Firmware operations can be specified by filling in a struct firmware_ops
|
| /Linux-v5.4/Documentation/driver-api/serial/ |
| D | serial-rs485.rst | 37 for bindings). The driver is in charge of filling this data structure from
|
| /Linux-v5.4/Documentation/core-api/ |
| D | circular-buffers.rst | 123 producer may still be filling the buffer on another CPU and moving the
146 consumer that empties it. Only one thing should be filling a buffer at any one
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ldm.rst | 95 is a dummy MSDOS partition filling the whole disk. You won't be able to mount
|
| /Linux-v5.4/mm/ |
| D | Kconfig.debug | 70 the patterns before alloc_pages. The filling of the memory helps
|
| /Linux-v5.4/Documentation/infiniband/ |
| D | user_mad.rst | 16 A MAD agent can be created by filling in a struct ib_user_mad_reg_req
|
| /Linux-v5.4/Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 40 This filling and emptying is managed by three pointers, the "head"
134 and is filling the next descrs. Since the OS doesn't see this, there
|
| /Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/ |
| D | omap-gpmc.txt | 33 As this will change in the future, filling correct
|
| /Linux-v5.4/Documentation/networking/ |
| D | checksum-offloads.rst | 48 CRC32c can also be offloaded using this interface, by means of filling
|
| D | udplite.txt | 161 split the payload into several individual packets, filling up the
|
| /Linux-v5.4/Documentation/trace/ |
| D | mmiotrace.rst | 83 Check that mmiotrace did not lose events due to a buffer filling up. Either::
|
| /Linux-v5.4/Documentation/i2c/ |
| D | instantiating-devices.rst | 100 you can instantiate your I2C devices explicitly. This is done by filling
|
| D | writing-clients.rst | 176 you can instantiate that device by simply filling an i2c_board_info
|
| /Linux-v5.4/Documentation/sh/ |
| D | new-machine.txt | 171 example vapor_inb. These will be needed when filling out the machine
|
| /Linux-v5.4/Documentation/networking/device_drivers/ |
| D | sb1000.txt | 168 /var/messages, and/or /var/syslog files, and they're filling up my /var
|
| /Linux-v5.4/Documentation/fb/ |
| D | api.rst | 226 Instead of filling the complete fb_var_screeninfo structure manually,
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | dm-clone.rst | 36 The process of filling a region of the destination device with data from
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | v4l2-videobuf.rst | 311 take care of calling get_user_pages() and filling in the scatterlist array.
|
| D | cec-core.rst | 279 attempt. It will call cec_transmit_done() in turn, filling in 1 for the
|
| D | v4l2-subdev.rst | 435 :c:func:`v4l2_i2c_new_subdev_board`, internally filling a
|
| /Linux-v5.4/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 107 relies on the driver filling a structure and registering against the
|
12
