| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/leds/ |
| H A D | leds-bcm6328.txt | 4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
8 by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 should be controlled by a hardware signal instead of the MODE register value,
15 with 0 meaning hardware control enabled and 1 hardware control disabled. This
16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
20 but you can't turn it off if the hardware decides to light it up. For this
21 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/char/hw_random/ |
| H A D | Kconfig | 3 # Hardware Random Number Generator (RNG) configuration
7 tristate "Hardware Random Number Generator Core support"
10 Hardware Random Number Generator Core infrastructure.
15 of possibly several hardware random number generators.
17 These hardware random number generators do feed into the
44 Generator hardware found on Intel i8xx-based motherboards.
57 Generator hardware found on AMD 76x-based motherboards.
70 Generator hardware found on Atmel AT91 devices.
82 Generator hardware based on Silex Insight BA431 IP.
94 Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/hwmon/pmbus/ |
| H A D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
34 If you say yes here you get hardware monitoring support for Analog
43 If you say yes here you get hardware monitoring support for Analog
53 If you say yes here you get hardware monitoring support for BEL
63 If you say yes here you get hardware monitoring support for the IBM
72 If you say yes here you get hardware monitoring support for the INSPUR
81 If you say yes here you get hardware monitoring support for the
90 If you say yes here you get hardware monitoring support for Infineon
99 If you say yes here you get hardware monitoring support for the
108 If you say yes here you get hardware monitoring support for Renesas
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/hwspinlock/ |
| H A D | Kconfig | 7 bool "Hardware Spinlock drivers"
12 tristate "OMAP Hardware Spinlock device"
15 Say y here to support the OMAP Hardware Spinlock device (firstly
21 tristate "Qualcomm Hardware Spinlock device"
25 Say y here to support the Qualcomm Hardware Mutex functionality, which
32 tristate "Rockchip Hardware Spinlock device"
35 Say y here to support the Rockchip Hardware Spinlock device, which
42 tristate "SIRF Hardware Spinlock device"
45 Say y here to support the SIRF Hardware Spinlock device, which
49 It's safe to say n here if you're not interested in SIRF hardware
[all …]
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/net/forwarding/ |
| H A D | fib_offload_lib.sh | 69 check_err $? "Route not in hardware when should"
73 check_err $? "Appended route in hardware when should not"
77 check_err $? "Prepended route not in hardware when should"
80 check_err $? "Route was not replaced in hardware by prepended one"
100 check_err $? "Route not in hardware when should"
104 check_err $? "Highest TOS route not in hardware when should"
107 check_err $? "Lowest TOS route still in hardware when should not"
111 check_err $? "Middle TOS route in hardware when should not"
129 check_err $? "Route not in hardware when should"
133 check_err $? "Lowest metric route not in hardware when should"
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/spi/ |
| H A D | spi-sprd-adi.txt | 5 framework for its hardware implementation is alike to SPI bus and its timing
9 48 hardware channels to access analog chip. For 2 software read/write channels,
10 users should set ADI registers to access analog chip. For hardware channels,
11 we can configure them to allow other hardware components to use it independently,
12 which means we can just link one analog chip address to one hardware channel,
13 then users can access the mapped analog chip address by this hardware channel
14 triggered by hardware components instead of ADI software channels.
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
17 channels, the first value specifies the hardware channel id which is used to
18 transfer data triggered by hardware automatically, and the second value specifies
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 18 media hardware.
29 Part of the Linux Kernel that implements support for a hardware
39 An API designed to control a subset of the :term:`Media Hardware`
58 Hardware Component
59 A subset of the :term:`Media Hardware`. For example an :term:`I²C` or
63 Hardware Peripheral
64 A group of :term:`hardware components <Hardware Component>` that
67 and the external camera sensors together make a camera hardware
76 serial computer bus used to control some hardware components
77 like sub-device hardware components.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
16 hardware vendors and other parties. For some of the issues, software
25 The Linux kernel hardware security team is separate from the regular Linux
28 The team only handles the coordination of embargoed hardware security
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
46 While hardware security issues are often handled by the affected hardware
[all …]
|
| /OK3568_Linux_fs/yocto/poky/documentation/kernel-dev/ |
| H A D | concepts-appx.rst | 35 needs for targeted hardware.
337 Determining Hardware and Non-Hardware Features for the Kernel Configuration Audit Phase
354 warnings, the system only reports missing "hardware" options as they
355 could result in a boot failure or indicate that important hardware is
358 To determine whether or not a given option is "hardware" or
359 "non-hardware", the kernel Metadata in ``yocto-kernel-cache`` contains
360 files that classify individual or groups of options as either hardware
361 or non-hardware. To better show this, consider a situation where the
364 yocto-kernel-cache/features/drm-psb/hardware.cfg
365 yocto-kernel-cache/features/kgdb/hardware.cfg
[all …]
|
| /OK3568_Linux_fs/external/xserver/hw/xfree86/ramdac/ |
| H A D | CURSOR.NOTES | 3 This file describes how to add hardware cursor support to a chipset
24 The driver informs the ramdac module of it's hardware cursor capablities by
55 LoadCursorImage is how the hardware cursor bits computed by the
67 provide this function if the hardware cursor format is not one of
73 If the driver is unable to use a hardware cursor for reasons
78 mode changes. This is useful for when the hardware cursor cannot
87 These indicate the largest sized cursor that can be a hardware
118 the LoadCursorImage entry is to be called to load a new hardware cursor
124 Hardware cursor data consists of two pieces, a source and a mask.
134 and clear bits indicate the transparent part. If your hardware
[all …]
|
| /OK3568_Linux_fs/kernel/crypto/ |
| H A D | crypto_engine.c | 3 * Handle async block request by crypto hardware engine.
21 * @engine: the hardware engine
34 * If hardware cannot enqueue more requests in crypto_finalize_request()
63 * @engine: the hardware engine
67 * needs processing and if so call out to the driver to initialize hardware
109 dev_err(engine->dev, "failed to unprepare crypt hardware\n"); in crypto_pump_requests()
124 * If hardware doesn't support the retry mechanism, in crypto_pump_requests()
145 dev_err(engine->dev, "failed to prepare crypt hardware\n"); in crypto_pump_requests()
168 /* Request unsuccessfully executed by hardware */ in crypto_pump_requests()
171 * If hardware queue is full (-ENOSPC), requeue request in crypto_pump_requests()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/usb/ |
| H A D | gadget.rst | 22 they're easy to port to new hardware.
36 - Minimalist, so it's easier to support new device controller hardware.
41 USB ``host`` hardware in a PC, workstation, or server. Linux users with
42 embedded systems are more likely to have USB peripheral hardware. To
43 distinguish drivers running inside such hardware from the more familiar
58 necessarily different (one side is a hardware-neutral master, the other
59 is a hardware-aware slave), the endpoint I/0 API used here should also
69 hardware).
75 to hardware, through registers, fifos, dma, irqs, and the like. The
77 endpoint hardware. That hardware is exposed through endpoint
[all …]
|
| H A D | writing_musb_glue_layer.rst | 35 hardware level. A couple of wiki pages by Texas Instruments and Analog
43 hardware sits at the lowest. The MUSB controller driver abstract the
44 MUSB controller hardware to the Linux USB stack::
65 | MUSB Controller Hardware |
69 sitting in between the controller driver and the controller hardware.
97 goes through a few steps, basically allocating the controller hardware
256 * Set dyn_fifo to avoid reading EP config from hardware.
266 driver data of the MUSB controller hardware and pass it on to the MUSB
268 controller hardware responsible for sending/receiving the USB data.
287 PHY driver when the controller hardware itself is about to be released.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/x86/ |
| H A D | sva.rst | 31 Shared Hardware Workqueues
36 Machines (VM's). This allows better hardware utilization vs. hard
38 allow the hardware to distinguish the context for which work is being
39 executed in the hardware by SWQ interface, SIOV uses Process Address Space
56 command was accepted by hardware. This allows the submitter to know if the
61 to the hardware and also permits hardware to be aware of application context
68 user processes and the rest of the hardware. When an application first
94 platform hardware. ENQCMD uses the PASID stored in this MSR to tag requests
124 * Devices have a limited number (~10's to 1000's) of hardware workqueues.
125 The device driver manages allocating hardware workqueues.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/devlink/ |
| H A D | devlink-dpipe.rst | 10 While performing the hardware offloading process, much of the hardware
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
38 information about the underlying hardware, this debugging can be made
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/hwcnt/ |
| H A D | mali_kbase_hwcnt_context.h | 23 * Hardware counter context API.
36 * kbase_hwcnt_context_init() - Initialise a hardware counter context.
37 * @iface: Non-NULL pointer to a hardware counter backend interface.
42 * A hardware counter accumulator can be acquired using a created context.
50 * kbase_hwcnt_context_term() - Terminate a hardware counter context.
56 * kbase_hwcnt_context_metadata() - Get the hardware counter metadata used by
59 * @hctx: Non-NULL pointer to the hardware counter context.
67 * @hctx: Non-NULL pointer to the hardware counter context.
85 * @hctx: Non-NULL pointer to the hardware counter context.
87 * This function will only succeed if hardware counters are effectively already
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/librknn_api_android_demo/ |
| H A D | README.md | 7 对于使用Android HIDL实现的RKNN API的代码位于RK3566_RK3568/RK3588 Android系统SDK的vendor/rockchip/hardware/interfac…
22 mmm vendor/rockchip/hardware/interfaces/neuralnetworks/ -j16
33 /vendor/lib64/rockchip.hardware.neuralnetworks@1.0.so
34 /vendor/lib64/rockchip.hardware.neuralnetworks@1.0-adapter-helper.so
35 /vendor/lib64/hw/rockchip.hardware.neuralnetworks@1.0-impl.so
36 /vendor/bin/hw/rockchip.hardware.neuralnetworks@1.0-service
57 - 确保板子的rockchip.hardware.neuralnetworks@1.0-service已经运行
67 - rockchip.hardware.neuralnetworks@1.0-service服务没有运行怎么办
69 …如果该服务没有运行，从Android SDK确保vendor/rockchip/hardware/interfaces/neuralnetworks/目录存在，并且重新编译系统固件，并重新烧写到板…
71 - 遇到sizeof(rknn_tensor_attr) != sizeof(::rockchip::hardware::neuralnetworks::V1_0::RKNNTensorAttr)的…
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/crypto/ |
| H A D | Kconfig | 4 bool "Hardware crypto devices"
7 Say Y here to get to see options for hardware crypto devices and
104 down the use of the available crypto hardware.
130 This is the s390 hardware accelerated implementation of the
141 This is the s390 hardware accelerated implementation of the
151 This is the s390 hardware accelerated implementation of the
161 This is the s390 hardware accelerated implementation of the
171 This is the s390 hardware accelerated implementation of the
181 This is the s390 hardware accelerated implementation of the
193 This is the s390 hardware accelerated implementation of the
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/iio/pressure/ |
| H A D | zpa2326.c | 15 * A internal hardware trigger is also implemented to dispatch registered IIO
18 * ZPA2326 hardware supports 2 sampling mode: one shot and continuous.
29 * The continuous mode works according to a periodic hardware measurement
30 * process continuously pushing samples into an internal hardware FIFO (for
35 * - setup hardware sampling period,
37 * hardware FIFO and fetch temperature sample
41 * declares a valid interrupt line. In this case, the internal hardware trigger
44 * Note that hardware sampling frequency is taken into account only when
45 * internal hardware trigger is attached as the highest sampling rate seems to
51 * hardware samples averaging.
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/predef/hardware/ |
| H A D | simd.h | 9 #include <boost/predef/hardware/simd/x86.h>
10 #include <boost/predef/hardware/simd/x86_amd.h>
11 #include <boost/predef/hardware/simd/arm.h>
12 #include <boost/predef/hardware/simd/ppc.h>
42 [include ../include/boost/predef/hardware/simd/x86.h]
43 [include ../include/boost/predef/hardware/simd/x86_amd.h]
44 [include ../include/boost/predef/hardware/simd/arm.h]
45 [include ../include/boost/predef/hardware/simd/ppc.h]
52 [include ../include/boost/predef/hardware/simd/x86/versions.h]
56 [include ../include/boost/predef/hardware/simd/x86_amd/versions.h]
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/block/ |
| H A D | inline-encryption.rst | 10 Inline encryption hardware sits logically between memory and the disk, and can
11 en/decrypt data as it goes in/out of the disk. Inline encryption hardware has a
16 the inline encryption hardware will en/decrypt the data in the request with the
28 IE hardware is absent. We also want IE to work with layered devices
29 like dm and loopback (i.e. we want to be able to use the IE hardware
37 - IE hardware has a limited number of "keyslots" that can be programmed
60 While IE hardware works on the notion of keyslots, the FS layer has no
65 encryption contexts specified by the FS to keyslots on the IE hardware.
66 This KSM also serves as the way IE hardware can expose its capabilities to
94 blissfully unaware of whether or not real inline encryption hardware is present
[all …]
|
| H A D | blk-mq.rst | 49 blk-mq has two group of queues: software staging queues and hardware dispatch
51 path possible: send it directly to the hardware queue. However, there are two
57 at the hardware queue, a second stage queue were the hardware has direct access
58 to process those requests. However, if the hardware does not have enough
60 queue, to be sent in the future, when the hardware is able.
95 eligible to be sent to the hardware. One of the possible schedulers to be
98 any reordering. When the device starts processing requests in the hardware
99 queue (a.k.a. run the hardware queue), the software queues mapped to that
100 hardware queue will be drained in sequence according to their mapping.
102 Hardware dispatch queues
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/media/ |
| H A D | cec-core.rst | 7 hardware. It is designed to handle a multiple types of hardware (receivers,
35 The struct cec_adapter represents the CEC adapter hardware. It is created by
61 capabilities of the hardware and which parts are to be handled
125 hardware:
128 To enable/disable the hardware::
132 This callback enables or disables the CEC hardware. Enabling the CEC hardware
146 that not for us. Not all hardware supports this and this function is only
148 (some hardware may always be in 'monitor all' mode).
158 changes. Not all hardware supports this and this function is only called if
160 (some hardware may always be in 'monitor pin' mode).
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/toshiba/ |
| H A D | spider_net.rst | 30 to receive data from the hardware. A "full" descriptor has data in it,
38 ring is handed off to the hardware, which sequentially fills in the
43 and "tail" pointers, managed by the OS, and a hardware current
45 currently being filled. When this descr is filled, the hardware
48 and everything in front of it should be "empty". If the hardware
52 The tail pointer tails or trails the hardware pointer. When the
53 hardware is ahead, the tail pointer will be pointing at a "full"
58 flowing, then the tail pointer can catch up to the hardware pointer.
66 dma-mapping it so as to make it visible to the hardware. The OS will
93 In the above, the hardware has filled in one descr, number 20. Both
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/watchdog/ |
| H A D | Kconfig | 18 reboot the machine) and a driver for hardware watchdog boards, which
66 care of pinging a hardware watchdog. A value of 0 means infinite. The
149 from some situations that the hardware watchdog will recover
333 This is the driver for the hardware watchdog on Mellanox systems.
374 the second one (WS1) is a real hardware reset.
449 boards have hardware problems that will cause the machine to simply
719 This is the driver for the hardware watchdog
749 This is the driver for the hardware watchdog on the Freescale
1028 This is the driver for the hardware watchdog on Single Board
1051 This is the driver for the hardware watchdog on the ALi M1535 PMU.
[all …]
|