Searched refs:info (Results 1 – 25 of 285) sorted by relevance
12345678910>>...12
/Documentation/driver-api/fpga/ |
D | fpga-programming.rst | 18 * program the FPGA using info passed in :c:expr:`fpga_region->info`. 37 struct fpga_image_info *info; 44 info = fpga_image_info_alloc(dev); 45 if (!info) 49 info->flags = FPGA_MGR_PARTIAL_RECONFIG; 57 info->sgt = [your scatter gather table] 61 info->buf = [your image buffer] 62 info->count = [image buffer size] 66 info->firmware_name = devm_kstrdup(dev, firmware_name, 71 /* Add info to region and do the programming */ [all …]
|
/Documentation/admin-guide/kdump/ |
D | gdbmacros.txt | 31 info symbol *($stackp) 45 info symbol *($stackp) 73 info symbol $addr 168 Run info threads and lookup pid of thread #1 175 set var $info = $arg1 202 if ($next - $begin < $info->text_len) 205 set var $text_len = $info->text_len 211 # prev & LOG_CONT && !(info->flags & LOG_PREIX) 212 if (($prev_flags & 8) && !($info->flags & 4)) 216 # info->flags & LOG_CONT [all …]
|
/Documentation/bpf/ |
D | btf.rst | 8 BTF (BPF Type Format) is the metadata format which encodes the debug info 10 types. The BTF was later extended to include function info for defined 11 subroutines, and line info for source/line information. 13 The debug info is used for map pretty print, function signature, etc. The 15 info helps generate source annotated translated byte code, jited code and 23 verifies the BTF info before using it. The ELF file format is a user space 27 debug info (mostly types related) referenced by the bpf program. These two 88 Note that the type section encodes debug info, not just pure types. 95 /* "info" bits arrangement 103 __u32 info; [all …]
|
/Documentation/fb/ |
D | cmap_xfbdev.rst | 20 info->cmap.red[i] = (((2*i)+1)*(0xFFFF))/16; 21 memcpy(info->cmap.green, info->cmap.red, sizeof(u16)*8); 22 memcpy(info->cmap.blue, info->cmap.red, sizeof(u16)*8); 53 directly from the info->cmap.red that was listed above. The prgb is the rgb
|
D | deferred_io.rst | 64 static void hecubafb_dpy_deferred_io(struct fb_info *info, 74 info->fbdefio = &hecubafb_defio; 75 fb_deferred_io_init(info); 79 fb_deferred_io_cleanup(info);
|
/Documentation/sphinx/ |
D | kernellog.py | 28 def info(app, message): function 30 logger.info(message) 32 app.info(message)
|
/Documentation/devicetree/bindings/soundwire/ |
D | qcom,sdw.txt | 57 More info in MIPI Alliance SoundWire 1.0 Specifications. 64 More info in MIPI Alliance SoundWire 1.0 Specifications. 72 More info in MIPI Alliance SoundWire 1.0 Specifications. 78 More info in MIPI Alliance SoundWire 1.0 Specifications. 87 More info in MIPI Alliance SoundWire 1.0 Specifications. 95 More info in MIPI Alliance SoundWire 1.0 Specifications. 103 More info in MIPI Alliance SoundWire 1.0 Specifications. 112 More info in MIPI Alliance SoundWire 1.0 Specifications. 121 More info in MIPI Alliance SoundWire 1.0 Specifications. 131 More info in MIPI Alliance SoundWire 1.0 Specifications.
|
/Documentation/networking/devlink/ |
D | devlink-flash.rst | 53 ``devlink-info`` allows users to query firmware information (loaded 66 Drivers are expected to implement ``devlink-flash`` and ``devlink-info`` 70 ``devlink-info`` exposes the ``driver`` name and three version groups 89 $hw_id = devlink-dev-info['fixed'] 95 if $want_flash_vers != devlink-dev-info['stored']: 103 if $want_fw_vers != devlink-dev-info['running']: 108 if $want_fw_vers != devlink-dev-info['running']: 112 if $want_fw_vers != devlink-dev-info['running']: 115 Note that each reference to ``devlink-dev-info`` in this pseudo-code
|
D | index.rst | 18 devlink-info 30 parameters, info versions, and other features it supports.
|
D | devlink-info.rst | 7 The ``devlink-info`` mechanism enables device drivers to report device 10 The original motivation for the ``devlink-info`` API was twofold: 18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver 21 .. list-table:: List of top level info objects 59 Data in ``devlink-info`` should be broken into the smallest logical 61 to form the Part Number string, while in ``devlink-info`` all parts
|
/Documentation/networking/ |
D | kcm.rst | 135 struct kcm_clone info; 137 memset(&info, 0, sizeof(info)); 139 err = ioctl(kcmfd, SIOCKCMCLONE, &info); 142 newkcmfd = info.fd; 156 struct kcm_attach info; 158 memset(&info, 0, sizeof(info)); 160 info.fd = tcpfd; 161 info.bpf_fd = bpf_prog_fd; 163 ioctl(kcmfd, SIOCKCMATTACH, &info); 181 struct kcm_unattach info; [all …]
|
/Documentation/userspace-api/media/cec/ |
D | cec-ioc-adap-g-conn-info.rst | 39 by the kernel with the info provided by the adapter's driver. This ioctl 58 - :ref:`cec-drm-connector-info` 83 :ref:`cec-drm-connector-info`. 89 .. _cec-drm-connector-info:
|
/Documentation/userspace-api/media/dvb/ |
D | ca_function_calls.rst | 16 ca-get-slot-info 17 ca-get-descr-info
|
D | ca-get-slot-info.rst | 20 ``int ioctl(fd, CA_GET_SLOT_INFO, struct ca_slot_info *info)`` 28 ``info``
|
D | frontend_fcalls.rst | 14 fe-get-info
|
/Documentation/ABI/testing/ |
D | debugfs-pktcdvd | 13 info 0444 Lots of driver statistics and infos. 18 cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
|
D | sysfs-class-led-driver-el15203000 | 8 For more info, please see:
|
/Documentation/devicetree/bindings/display/tilcdc/ |
D | panel.txt | 5 - panel-info: configuration info to configure LCDC correctly for the panel 39 panel-info {
|
/Documentation/ABI/stable/ |
D | sysfs-bus-mhi | 10 Users: Any userspace application or clients interested in device info. 21 Users: Any userspace application or clients interested in device info.
|
D | sysfs-devices-system-xen_memory | 56 What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb 64 What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb 71 What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb
|
/Documentation/scsi/ |
D | NinjaSCSI.rst | 34 code) to get more info. 41 Jan 2 03:45:06 lindberg cardmgr[78]: product info: "WBT", "NinjaSCSI-3", "R1.0" 45 no product info available 47 product info: "IO DATA", "CBSC16 ", "1"
|
/Documentation/ |
D | watch_queue.rst | 59 __u32 info; 73 "info" indicates a bunch of things, including: 88 Everything in info apart from the length can be used for filtering. 152 u32 info_id; /* ID to be OR'd in to info field */ 162 struct watch_notification::info when and if the notification is written into 217 units of buffer slots is noted in ``n->info & WATCH_INFO_LENGTH``. 275 * ``info_filter`` and ``info_mask`` act as a filter on the info field of the 278 (watch.info & info_mask) == info_filter 327 len = (n->info & WATCH_INFO_LENGTH) >>
|
/Documentation/admin-guide/pm/ |
D | intel-speed-select.rst | 54 To get help on a command, another level of help is provided. For example for the command info "info… 56 # intel-speed-select perf-profile info --help 62 #intel-speed-select --info 66 # intel-speed-select --info 143 # intel-speed-select perf-profile info -l 0 169 understand more, execute "intel-speed-select perf-profile info" for performance 172 # intel-speed-select perf-profile info -l 4 212 "perf-profile info" command for performance level 0(cpufreq frequency is in 273 For example, from the output of "perf-profile info" above, for level 0 and level 365 info" command can be used. For example to check the status of core-power feature [all …]
|
/Documentation/PCI/ |
D | index.rst | 16 acpi-info
|
/Documentation/driver-api/usb/ |
D | usb.rst | 721 in the first 4 columns of each ``T:`` line (topology info: 729 D = Device descriptor info. 730 P = Product ID info. (from Device descriptor, but they won't fit 733 C = Configuration descriptor info. (* = active configuration) 734 I = Interface descriptor info. 735 E = Endpoint descriptor info. 747 Topology info 761 |__Topology info tag 777 Bandwidth info 786 |__Bandwidth info tag [all …]
|
12345678910>>...12