| /linux/scripts/ |
| H A D | extract-sys-certs.pl | 26 open FD, "objdump -h $vmlinux |" || die $vmlinux; 27 my @lines = <FD>; 28 close(FD) || die $vmlinux; 57 open FD, "nm $vmlinux 2>/dev/null |" || die $vmlinux; 58 @lines = <FD>; 59 close(FD) || die $vmlinux; 83 open FD, "<$sysmap" || die $sysmap; 84 @lines = <FD>; 85 close(FD) || die $sysmap; 103 open FD, "<$vmlinux" || die $vmlinux; [all …]
|
| H A D | extract-module-sig.pl | 30 open FD, "<$modfile" || die $modfile; 31 binmode(FD); 32 my @st = stat(FD); 35 my $len = sysread(FD, $buf, $st[7]); 38 close(FD) || die $modfile;
|
| /linux/drivers/gpu/drm/amd/display/dc/dce120/ |
| H A D | dce120_timing_generator.c | 49 CRTC_REG_UPDATE_N(reg, 1, FD(reg##__##field), val) 52 CRTC_REG_UPDATE_N(reg, 2, FD(reg##__##field1), val1, FD(reg##__##field2), val2) 55 …CRTC_REG_UPDATE_N(reg, 3, FD(reg##__##field1), val1, FD(reg##__##field2), val2, FD(reg##__##field3… 58 …CRTC_REG_UPDATE_N(reg, 3, FD(reg##__##field1), val1, FD(reg##__##field2), val2, FD(reg##__##field3… 61 …REG_UPDATE_N(reg, 3, FD(reg##__##field1), val1, FD(reg##__##field2), val2, FD(reg##__##field3), va… 64 CRTC_REG_SET_N(reg, 1, FD(reg##__##field), val) 67 CRTC_REG_SET_N(reg, 2, FD(reg##__##field1), val1, FD(reg##__##field2), val2) 70 …CRTC_REG_SET_N(reg, 3, FD(reg##__##field1), val1, FD(reg##__##field2), val2, FD(reg##__##field3), … 265 FD(DCP0_DCP_GSL_CONTROL__DCP_GSL0_EN), 1, in dce120_timing_generator_setup_global_swap_lock() 266 FD(DCP0_DCP_GSL_CONTROL__DCP_GSL_MASTER_EN), gsl_params->gsl_master == tg->inst, in dce120_timing_generator_setup_global_swap_lock() [all …]
|
| /linux/drivers/net/can/peak_canfd/ |
| H A D | Kconfig | 4 tristate "PEAK-System PCAN-PCIe FD cards" 6 This driver adds support for the PEAK-System PCI Express FD 7 CAN-FD cards family. 8 These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as 9 CAN-FD access to the CAN bus. Besides the nominal bitrate of up to 10 1 Mbit/s, the data bytes of CAN-FD frames can be transmitted with 13 disturbances of up to 500 Volts. The PCAN-PCI Express FD can be
|
| /linux/drivers/net/can/ctucanfd/ |
| H A D | Kconfig | 2 tristate "CTU CAN-FD IP core" if COMPILE_TEST 4 This driver adds support for the CTU CAN FD open-source IP core. 15 tristate "CTU CAN-FD IP core PCI/PCIe driver" 19 This driver adds PCI/PCIe support for CTU CAN-FD IP core. 25 tristate "CTU CAN-FD IP core platform (FPGA, SoC) driver" 30 modified to be CAN FD frames tolerant on MicroZed Zynq based
|
| /linux/tools/lib/perf/ |
| H A D | evsel.c | 59 #define FD(_evsel, _cpu_map_idx, _thread) \ macro 74 int *fd = FD(evsel, idx, thread); in perf_evsel__alloc_fd() 117 fd = FD(leader, cpu_map_idx, thread); in get_group_fd() 164 evsel_fd = FD(evsel, idx, thread); in perf_evsel__open() 198 int *fd = FD(evsel, cpu_map_idx, thread); in perf_evsel__close_fd_cpu() 245 int *fd = FD(evsel, idx, thread); in perf_evsel__munmap() 274 int *fd = FD(evsel, idx, thread); in perf_evsel__mmap() 297 int *fd = FD(evsel, cpu_map_idx, thread); in perf_evsel__mmap_base() 338 int *fd = FD(evsel, cpu_map_idx, thread); in perf_evsel__read_group() 404 int *fd = FD(evsel, cpu_map_idx, thread); in perf_evsel__read() [all …]
|
| /linux/drivers/net/can/rcar/ |
| H A D | Kconfig | 13 tristate "Renesas R-Car CAN FD controller" 16 Say Y here if you want to use CAN FD controller found on 17 Renesas R-Car SoCs. The driver puts the controller in CAN FD only
|
| /linux/drivers/net/can/rockchip/ |
| H A D | Kconfig | 4 tristate "Rockchip CAN-FD controller" 9 Say Y here if you want to use CAN-FD controller found on
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_zerocopy_epoll_oneshot.pkt | 4 // This is a test to confirm that EPOLLERR is only fired once for an FD when 9 // with MSG_ZEROCOPY. confirm that EPOLLERR is not fired. Rearm the FD and 52 // rearm the FD and verify the EPOLLERR is fired again.
|
| /linux/tools/perf/util/ |
| H A D | tool_pmu.c | 239 #define FD(e, x, y) (*(int *)xyarray__entry(e->core.fd, x, y)) macro 286 FD(evsel, idx, thread) = fd; in evsel__tool_pmu_open() 316 if (FD(evsel, idx, thread) >= 0) in evsel__tool_pmu_open() 317 close(FD(evsel, idx, thread)); in evsel__tool_pmu_open() 318 FD(evsel, idx, thread) = -1; in evsel__tool_pmu_open() 543 int fd = FD(evsel, cpu_map_idx, thread); in evsel__tool_pmu_read()
|
| H A D | bpf_counter_cgroup.c | 45 #define FD(evt, cpu) (*(int *)xyarray__entry(evt->core.fd, cpu, 0)) macro 133 FD(cgrp_switch, i)); in bperf_load_program() 159 int fd = FD(evsel, j); in bperf_load_program()
|
| H A D | hwmon_pmu.c | 756 #define FD(e, x, y) (*(int *)xyarray__entry(e->core.fd, x, y)) macro 782 FD(evsel, idx, thread) = fd; in evsel__hwmon_pmu_open() 797 if (FD(evsel, idx, thread) >= 0) in evsel__hwmon_pmu_open() 798 close(FD(evsel, idx, thread)); in evsel__hwmon_pmu_open() 799 FD(evsel, idx, thread) = -1; in evsel__hwmon_pmu_open() 818 fd = FD(evsel, cpu_map_idx, thread); in evsel__hwmon_pmu_read()
|
| H A D | bpf-filter.c | 68 #define FD(e, x, y) (*(int *)xyarray__entry(e->core.fd, x, y)) macro 300 int ret = ioctl(FD(evsel, x, y), PERF_EVENT_IOC_ID, &id); in create_event_hash() 498 ret = ioctl(FD(evsel, x, y), PERF_EVENT_IOC_SET_BPF, fd); in perf_bpf_filter__prepare() 532 link = bpf_program__attach_perf_event_opts(prog, FD(evsel, x, y), in perf_bpf_filter__prepare()
|
| /linux/Documentation/networking/device_drivers/can/ctu/ |
| H A D | ctucanfd-driver.rst | 3 CTU CAN FD Driver 9 About CTU CAN FD IP Core 12 `CTU CAN FD <https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core>`_ 30 The basic functional model of the CTU CAN FD peripheral has been 32 for CAN FD buses, host connection and CTU CAN FD core emulation. The development 260 CTU CAN FD Driver design 265 CAN FD core driver in particular. 292 independently for both the Nominal bitrate and Data bitrate for CAN FD. 325 sample point is between PHASE_SEG1 and PHASE_SEG2. In CTU CAN FD, 340 An incoming frame may be either a CAN 2.0 frame or a CAN FD frame. The [all …]
|
| /linux/Documentation/networking/ |
| H A D | can.rst | 231 The Classical CAN frame structure (aka CAN 2.0B), the CAN FD frame structure 397 Remark about CAN FD (flexible data rate) support: 399 Generally the handling of CAN FD is very similar to the formerly described 400 examples. The new CAN FD capable CAN controllers support two different 401 bitrates for the arbitration phase and the payload phase of the CAN FD frame 406 switches the socket into a mode that allows the handling of CAN FD frames 416 __u8 flags; /* additional flags for CAN FD */ 434 For details about the distinction of CAN and CAN FD capable devices and 437 The length of the two CAN(FD) frame structures define the maximum transfer 438 unit (MTU) of the CAN(FD) network interface and skbuff data length. Two [all …]
|
| H A D | l2tp.rst | 131 FD N Tunnel socket file descriptor. 132 UDP_CSUM N Enable IPv4 UDP checksums. Used only if FD is 135 if FD is not set. 137 FD is not set. 138 IP_SADDR N IPv4 source address. Used only if FD is not 140 IP_DADDR N IPv4 destination address. Used only if FD is 142 UDP_SPORT N UDP source port. Used only if FD is not set. 143 UDP_DPORT N UDP destination port. Used only if FD is not 145 IP6_SADDR N IPv6 source address. Used only if FD is not 147 IP6_DADDR N IPv6 destination address. Used only if FD is
|
| H A D | iso15765-2.rst | 15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with 276 for classical CAN frames or ``CANFD_MTU`` for CAN FD frames. 279 among: 8, 12, 16, 20, 24, 32, 48, 64. Values above 8 only apply to CAN FD 283 Only applies to CAN FD traffic (i.e.: ``mtu = CANFD_MTU``).
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | fd_array.c | 48 #define Close(FD) do { \ argument 49 if ((FD) >= 0) { \ 50 close(FD); \ 51 FD = -1; \
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-func-poll.rst | 28 List of FD events to be watched 31 Number of FD events at the \*ufds array
|
| /linux/drivers/gpu/drm/amd/display/dmub/src/ |
| H A D | dmub_reg.h | 45 #define FD(reg_field) (REGS)->shift.reg_field, (REGS)->mask.reg_field macro 47 #define FN(reg_name, field) FD(reg_name##__##field)
|
| /linux/net/can/ |
| H A D | Kconfig | 64 (aka Classical CAN, CAN 2.0B) and CAN FD frame types which were 67 (max. 8 bytes for CAN CC and max. 64 bytes for CAN FD) this
|
| /linux/tools/perf/trace/beauty/ |
| H A D | futex_op.c | 40 P_FUTEX_OP(FD); arg->mask |= SCF_VAL3|SCF_UADDR2|SCF_TIMEOUT; break; in syscall_arg__scnprintf_futex_op()
|
| /linux/net/9p/ |
| H A D | Kconfig | 23 tristate "9P FD Transport"
|
| /linux/Documentation/bpf/ |
| H A D | map_xskmap.rst | 100 is attaching to. And the ``value`` parameter is the FD value of that socket. 102 Under the hood, the XSKMAP update function uses the XSK FD value to retrieve the
|
| /linux/drivers/gpu/drm/amd/display/dc/clk_mgr/dcn301/ |
| H A D | dcn301_smu.c | 43 FD(reg_name##__##field)
|