| /linux/arch/microblaze/kernel/cpu/ |
| A D | cpuinfo-pvr-full.c | 34 CI(ver_code, VERSION); in set_cpuinfo_pvr_full()
65 CI(pvr_user1, USER1); in set_cpuinfo_pvr_full()
66 CI(pvr_user2, USER2); in set_cpuinfo_pvr_full()
68 CI(mmu, USE_MMU); in set_cpuinfo_pvr_full()
70 CI(endian, ENDIAN); in set_cpuinfo_pvr_full()
72 CI(use_icache, USE_ICACHE); in set_cpuinfo_pvr_full()
93 CI(use_dopb, D_OPB); in set_cpuinfo_pvr_full()
94 CI(use_iopb, I_OPB); in set_cpuinfo_pvr_full()
95 CI(use_dlmb, D_LMB); in set_cpuinfo_pvr_full()
96 CI(use_ilmb, I_LMB); in set_cpuinfo_pvr_full()
[all …]
|
| /linux/Documentation/userspace-api/media/dvb/ |
| A D | ca_high_level.rst | 3 The High level CI API
10 This document describes the high level CI API as in accordance to the
14 With the High Level CI approach any new card with almost any random
25 Why the need for another CI interface?
31 The CI interface is defined in the DVB API in ca.h as:
39 #define CA_CI 1 /* CI high level interface */
50 This CI interface follows the CI high level interface, which is not
89 APP: CI High level interface
90 APP: CA/CI Module Present
118 /* a message to/from a CI-CAM */
[all …]
|
| A D | ca-get-msg.rst | 34 Receives a message via a CI CA module.
|
| A D | ca-send-msg.rst | 34 Sends a message via a CI CA module.
|
| /linux/Documentation/admin-guide/media/ |
| A D | ci.rst | 11 This document describes the usage of the high level CI API as
13 existing low level CI API.
17 For the Twinhan/Twinhan clones, the dst_ca module handles the CI
18 hardware handling. This module is loaded automatically if a CI
65 CI modules that are supported
68 The CI module support is largely dependent upon the firmware on the cards
69 Some cards do support almost all of the available CI modules. There is
70 nothing much that can be done in order to make additional CI modules
|
| A D | dvb-usb-dvbsky-cardlist.rst | 31 * - TechnoTrend TT-connect CT2-4650 CI
33 * - TechnoTrend TT-connect CT2-4650 CI v1.1
35 * - TechnoTrend TT-connect S2-4650 CI
|
| A D | cx23885-cardlist.rst | 86 - NetUP Dual DVB-S2 CI
138 - NetUP Dual DVB-T/C-CI RF
210 - Technotrend TT-budget CT2-4500 CI
|
| A D | dvb-usb-az6007-cardlist.rst | 17 * - Technisat CableStar Combo HD CI
|
| A D | dvb-usb-pctv452e-cardlist.rst | 19 * - Technotrend TT Connect S2-3650-CI
|
| A D | dvb-usb-az6027-cardlist.rst | 23 * - Technisat SkyStar USB 2 HD CI
|
| /linux/drivers/media/pci/cx23885/ |
| A D | Kconfig | 55 tristate "Altera FPGA based CI module"
59 An Altera FPGA CI module for NetUP Dual DVB-T/C RF CI card.
|
| /linux/Documentation/gpu/ |
| A D | automated_testing.rst | 32 This is the root configuration file for GitLab CI. Among other less interesting
37 Repository that contains the Mesa software infrastructure for CI
100 CI/CD configuration file from .gitlab-ci.yml to
104 necessary privileges to run the CI on https://gitlab.freedesktop.org/drm/ci-ok
106 4. Next time you push to this repository, you will see a CI pipeline being
|
| /linux/kernel/configs/ |
| A D | debug.config | 1 # Help: Debugging for CI systems and finding regressions
3 # The config is based on running daily CI for enterprise Linux distros to
|
| /linux/tools/testing/selftests/bpf/ |
| A D | DENYLIST.riscv64 | 1 # riscv64 deny list for BPF CI and local vmtest
|
| A D | README.rst | 10 BPF CI System
13 BPF employs a continuous integration (CI) system to check patch submission in an
21 The CI system executes tests on multiple architectures. It uses a kernel
30 In such a case tests in CI may fail. An example of such a shortcoming is BPF
54 would be run post-submit in the CI used by the Maintainers, with the exception
58 image from the system used by the CI. It builds the kernel (without overwriting
|
| /linux/Documentation/gpu/amdgpu/display/ |
| A D | index.rst | 23 repository has integration tests with our Internal Linux CI farm, and we run a
25 and APUs). Our CI also checks ARM64/32, PPC64/32, and x86_64/32 compilation
62 In terms of test setup for CI and manual tests, we usually use:
|
| /linux/Documentation/translations/zh_CN/maintainer/ |
| A D | maintainer-entry-profile.rst | 30 - 是否有任何机器人或CI基础设施监视列表，或子系统是否使用自动测试反馈以便把
|
| /linux/drivers/gpu/drm/ci/xfails/ |
| A D | msm-sdm845-skips.txt | 4 # Failing due to a bootloader/fw issue. The workaround in mesa CI involves these two patches
|
| /linux/drivers/media/pci/netup_unidvb/ |
| A D | Kconfig | 18 Two CI slots available for CAM modules.
|
| /linux/Documentation/gpu/rfc/ |
| A D | i915_gem_lmem.rst | 13 start running IGTs which can utilize local-memory in CI
|
| /linux/Documentation/arch/powerpc/ |
| A D | dawr-power9.rst | 6 cause a checkstop if it points to cache inhibited (CI) memory. Currently Linux
7 has no way to distinguish CI memory when configuring the DAWR, so on affected
|
| /linux/Documentation/hwmon/ |
| A D | adm9240.rst | 172 An alarm is asserted when the CI pin goes active high. The ADM9240
180 Clear the CI latch by writing value 0 to the sysfs intrusion0_alarm file.
196 12 Chassis_Error CI pin went high
|
| /linux/Documentation/devicetree/bindings/perf/ |
| A D | arm,cmn.yaml | 41 relevant for newer CMN/CI products.
|
| /linux/Documentation/ABI/testing/ |
| A D | configfs-usb-gadget-midi2 | 50 midi_ci_verison Supported MIDI-CI version number (8 bit)
|
| /linux/drivers/gpu/drm/ci/ |
| A D | gitlab-ci.yml | 175 # When to automatically run the CI for build jobs
183 # When to automatically run the CI for container jobs
207 # Run pipeline by default in the main project if any CI pipeline
|