| /linux/fs/netfs/ |
| A D | write_issue.c | 315 struct netfs_io_stream *upload = &wreq->io_streams[0]; in netfs_write_folio() local
389 netfs_issue_write(wreq, upload); in netfs_write_folio()
395 netfs_issue_write(wreq, upload); in netfs_write_folio()
401 netfs_issue_write(wreq, upload); in netfs_write_folio()
416 netfs_issue_write(wreq, upload); in netfs_write_folio()
421 } else if (!upload->avail && !cache->avail) { in netfs_write_folio()
425 } else if (!upload->construct) { in netfs_write_folio()
694 struct netfs_io_stream *upload = &wreq->io_streams[0]; in netfs_unbuffered_write() local
708 part = netfs_advance_write(wreq, upload, start, len, false); in netfs_unbuffered_write()
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-firmware | 28 upload. This string will be in the form of <STATUS>:<ERROR>,
34 upload status is "idle". If this file is read while a firmware
53 Description: Read-only. For firmware upload, this file contains the size
59 upload.
67 a firmware upload. The string will be one of the following:
|
| A D | sysfs-class-chromeos-driver-cros-ec-lightbar | 49 This allows you to upload and run custom lightbar sequences.
|
| /linux/Documentation/driver-api/firmware/ |
| A D | fw_upload.rst | 11 upload uses the same *loading* and *data* sysfs files described in the
15 Register for firmware upload
18 A device driver registers for firmware upload by calling
21 firmware upload by echoing a 1 to the *loading* sysfs file for the target
28 To use the firmware upload API, write a driver that implements a set of
|
| A D | fallback-mechanisms.rst | 68 In order to help device drivers upload firmware using a fallback mechanism
84 and a file upload firmware into:
89 To upload firmware you will echo 1 onto the loading file to indicate
|
| /linux/drivers/input/misc/ |
| A D | uinput.c | 52 } upload; member
254 request.u.upload.effect = effect; in uinput_dev_upload_effect()
255 request.u.upload.old = old; in uinput_dev_upload_effect()
348 dev->ff->upload = uinput_dev_upload_effect; in uinput_create_device()
994 !req->u.upload.effect) { in uinput_ioctl_handler()
1000 ff_up.effect = *req->u.upload.effect; in uinput_ioctl_handler()
1001 if (req->u.upload.old) in uinput_ioctl_handler()
1002 ff_up.old = *req->u.upload.old; in uinput_ioctl_handler()
1037 !req->u.upload.effect) { in uinput_ioctl_handler()
|
| A D | cs40l50-vibra.c | 517 vib->input->ff->upload = cs40l50_add; in cs40l50_vibra_probe()
|
| A D | da7280.c | 1240 ff->upload = da7280_haptics_upload_effect; in da7280_probe()
|
| /linux/Documentation/driver-api/pm/ |
| A D | notifiers.rst | 19 For example, device drivers may want to upload firmware to their devices after
23 into memory before processes are frozen and upload it from there in the
|
| /linux/Documentation/devicetree/bindings/iio/light/ |
| A D | liteon,ltr390.yaml | 14 … https://optoelectronics.liteon.com/upload/download/DS86-2015-0004/LTR-390UV_Final_%20DS_V1%201.pdf
|
| /linux/Documentation/devicetree/bindings/iio/proximity/ |
| A D | tyhx,hx9023s.yaml | 14 http://www.tianyihexin.com/ueditor/php/upload/file/20240614/1718336303992081.pdf
|
| /linux/Documentation/devicetree/bindings/net/bluetooth/ |
| A D | realtek,bluetooth.yaml | 16 H5 protocol with few extra commands to upload firmware and change
|
| /linux/drivers/xen/ |
| A D | xen-acpi-processor.c | 400 goto upload; in check_acpi_ids()
428 upload: in check_acpi_ids()
|
| /linux/Documentation/arch/powerpc/ |
| A D | qe_firmware.rst | 51 2) describes how and where to upload the microcode
177 function, which parses the blob and performs everything necessary to upload
213 only upload the microcode if there's a match. However, this check is not
|
| /linux/Documentation/input/ |
| A D | ff.rst | 119 "effect" points to a structure describing the effect to upload. The effect is
227 Proceed as if you wanted to upload a new effect, except that instead of
|
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| A D | ucc.txt | 21 broken UART hardware. Soft-UART is provided via a microcode upload.
|
| /linux/drivers/input/ |
| A D | ff-core.c | 152 ret = ff->upload(dev, effect, old); in input_ff_upload()
|
| A D | ff-memless.c | 535 ff->upload = ml_ff_upload; in input_ff_create_memless()
|
| /linux/Documentation/arch/arm/sa1100/ |
| A D | assabet.rst | 93 If you rather want to use Y-Modem upload over the serial port::
110 Again, Y-Modem upload can be used instead of TFTP by replacing the file name
|
| /linux/include/linux/ |
| A D | input.h | 556 int (*upload)(struct input_dev *dev, struct ff_effect *effect, member
|
| /linux/drivers/input/joystick/iforce/ |
| A D | iforce-main.c | 380 ff->upload = iforce_upload_effect; in iforce_init_device()
|
| /linux/Documentation/input/devices/ |
| A D | yealink.rst | 104 ringtone Write, upload binary representation of a ringtone,
|
| /linux/Documentation/networking/ |
| A D | regulatory.rst | 18 in userspace and provide a framework for userspace to upload
|
| /linux/Documentation/userspace-api/media/drivers/ |
| A D | uvcvideo.rst | 60 purposes, firmware upload, or accessing binary controls, a second mechanism to
|
| /linux/drivers/hid/usbhid/ |
| A D | hid-pidff.c | 1307 ff->upload = pidff_upload_effect; in hid_pidff_init()
|