| /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/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/media/rc/ |
| H A D | serial_ir.c | 66 static struct serial_ir_hw hardware[] = { variable
68 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_HOMEBREW].lock),
82 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO].lock),
93 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IRDEO_REMOTE].lock),
104 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_ANIMAX].lock),
112 .lock = __SPIN_LOCK_UNLOCKED(hardware[IR_IGOR].lock),
163 soutp(UART_MCR, hardware[type].off); in on()
165 soutp(UART_MCR, hardware[type].on); in on()
171 soutp(UART_MCR, hardware[type].on); in off()
173 soutp(UART_MCR, hardware[type].off); in off()
[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/sound/isa/wss/ |
| H A D | wss_lib.c | 409 if ((timeout & CS4231_MCE) == 0 || !(chip->hardware & hw_mask)) in snd_wss_mce_down()
589 if (!(chip->hardware & WSS_HW_AD1848_MASK)) { in snd_wss_calibrate_mute()
597 if (chip->hardware == WSS_HW_INTERWAVE) { in snd_wss_calibrate_mute()
619 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_playback_format()
620 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_playback_format()
634 } else if (chip->hardware == WSS_HW_AD1845) { in snd_wss_playback_format()
656 if (chip->hardware != WSS_HW_INTERWAVE && !chip->single_dma) { in snd_wss_playback_format()
665 if (chip->hardware == WSS_HW_OPL3SA2) in snd_wss_playback_format()
680 if (chip->hardware == WSS_HW_CS4231A || in snd_wss_capture_format()
681 (chip->hardware & WSS_HW_CS4232_MASK)) { in snd_wss_capture_format()
[all …]
|
| /OK3568_Linux_fs/kernel/arch/mips/boot/dts/brcm/ |
| H A D | bcm63268-comtrend-vr-3032u.dts | 29 brcm,hardware-controlled;
35 brcm,hardware-controlled;
66 brcm,hardware-controlled;
71 brcm,hardware-controlled;
76 brcm,hardware-controlled;
81 brcm,hardware-controlled;
86 brcm,hardware-controlled;
91 brcm,hardware-controlled;
96 brcm,hardware-controlled;
|
| /OK3568_Linux_fs/kernel/sound/isa/sb/ |
| H A D | sb_common.c | 118 switch (chip->hardware) { in snd_sbdsp_probe()
122 chip->hardware = SB_HW_10; in snd_sbdsp_probe()
127 chip->hardware = SB_HW_201; in snd_sbdsp_probe()
130 chip->hardware = SB_HW_20; in snd_sbdsp_probe()
135 chip->hardware = SB_HW_PRO; in snd_sbdsp_probe()
139 chip->hardware = SB_HW_16; in snd_sbdsp_probe()
202 unsigned short hardware, in snd_sbdsp_create() argument
227 (hardware == SB_HW_ALS4000 || in snd_sbdsp_create()
228 hardware == SB_HW_CS5530) ? in snd_sbdsp_create()
238 if (hardware == SB_HW_ALS4000) in snd_sbdsp_create()
[all …]
|
| /OK3568_Linux_fs/external/linux-rga/samples/allocator_demo/ |
| H A D | Android.mk | 13 hardware/rockchip/librga \
14 hardware/rockchip/librga/include \
15 hardware/rockchip/librga/im2d_api
18 hardware/rockchip/librga/samples/utils \
19 hardware/rockchip/librga/samples/3rdparty \
20 hardware/rockchip/librga/samples/3rdparty/libdrm/include \
21 hardware/rockchip/librga/samples/3rdparty/libdrm/include/libdrm \
|
| /OK3568_Linux_fs/external/linux-rga/samples/alpha_demo/ |
| H A D | Android.mk | 13 hardware/rockchip/librga \
14 hardware/rockchip/librga/include \
15 hardware/rockchip/librga/im2d_api
18 hardware/rockchip/librga/samples/utils \
19 hardware/rockchip/librga/samples/3rdparty \
20 hardware/rockchip/librga/samples/3rdparty/libdrm/include \
21 hardware/rockchip/librga/samples/3rdparty/libdrm/include/libdrm
|
| /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/external/mpp/doc/design/ |
| H A D | 1.mpp_design.txt | 8 The design target of mpp is to connect different Rockchip hardware kernel driver
11 Rockchip has two sets of hardware kernel driver.
14 performance stateless frame base hardware kernel driver. This driver supports
15 all available codecs that hardware can provide. This driver is used on Android/
34 mpp internally make hardware and software run parallelly. When hardware is
35 running sofware will prepare next hardware task at the same time.
88 provide basic components including memory, time, thread, log and hardware memory
101 be separated from hardware specified process. The software will communicate with
102 hardware with a common task interface which combines the buffer information and
107 different hardware. For decoder parser provide the video stream parse function
[all …]
|
| H A D | 2.kernel_driver.txt | 4 Rockchip has two sets of hardware kernel driver.
7 performance stateless frame base hardware kernel driver. This driver supports
8 all available codecs that hardware can provide. This driver is used on Android/
56 The principle of this design is to separate user task handling and hardware
58 hardware process operation.
61 will have a kernel session. Client will commit tasks to session. Then hardware
67 get task from waiting list to running list and run. When hardware finishs a task
|
| /OK3568_Linux_fs/kernel/drivers/char/hw_random/ |
| H A D | Kconfig | 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.
107 hardware found on the Broadcom iProc and STB SoCs.
120 Generator hardware found on the AMD Geode LX.
133 Generator hardware found on Niagara2 cpus.
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/tty/ipwireless/ |
| H A D | tty.c | 49 struct ipw_hardware *hardware; member
218 ret = ipwireless_send_packet(tty->hardware, IPW_CHANNEL_RAS, in ipw_write()
312 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 1); in set_control_lines()
316 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
323 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 1); in set_control_lines()
327 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
334 ret = ipwireless_set_RTS(tty->hardware, tty->channel_idx, 0); in set_control_lines()
336 ret = ipwireless_set_RTS(tty->hardware, in set_control_lines()
343 ret = ipwireless_set_DTR(tty->hardware, tty->channel_idx, 0); in set_control_lines()
345 ret = ipwireless_set_DTR(tty->hardware, in set_control_lines()
[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
134 and clear bits indicate the transparent part. If your hardware
140 the mask. If the hardware needs this order reversed then this
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | ethernet-driver.rst | 20 Unlike regular NICs, in the DPAA2 architecture there is no single hardware block
21 representing network interfaces; instead, several separate hardware resources
29 All hardware resources are allocated and configured through the Management
32 hardware resources, like queues, do not have a corresponding MC object and
58 . . . hardware
60 | MC hardware portals |
69 DPBPs represent hardware buffer pools. Packet I/O is performed in the context
71 hardware resources.
90 | | | | | hardware
92 | I/O hardware portals |
[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/Documentation/devicetree/bindings/crypto/ |
| H A D | brcm,spu-crypto.txt | 1 The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
2 cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
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
48 identified a potential hardware flaw.
53 The current team of hardware security officers:
[all …]
|
| /OK3568_Linux_fs/external/linux-rga/ |
| H A D | Android.mk | 47 LOCAL_C_INCLUDES += hardware/rockchip/libgralloc
48 LOCAL_C_INCLUDES += hardware/rk29/libgralloc_ump
49 LOCAL_C_INCLUDES += hardware/libhardware/include/hardware
54 LOCAL_C_INCLUDES += $(LOCAL_PATH)/core/hardware
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.bus_vcxk | 25 The driver needs some defines to describe the target hardware:
29 base address of VCxK hardware memory
46 describes the acknowledge line from vcxk hardware
49 describes the enable line to vcxk hardware
52 describes the invert line to vcxk hardware
55 describes the reset line to vcxk hardware
58 describes the request line to vcxk hardware
|
| /OK3568_Linux_fs/kernel/Documentation/powerpc/ |
| H A D | ptrace.rst | 5 GDB intends to support the following hardware debug features of BookE
8 4 hardware breakpoints (IAC)
9 2 hardware watchpoints (read, write and read-write) (DAC)
10 2 value conditions for the hardware watchpoints (DVC)
21 Query for GDB to discover the hardware debug features. The main info to
22 be returned here is the minimum alignment for the hardware watchpoints.
24 an 8-byte alignment restriction for hardware watchpoints. We'd like to avoid
28 GDB: this query will return the number of hardware breakpoints, hardware
53 Sets a hardware breakpoint or watchpoint, according to the provided structure::
86 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/isdn/mISDN/ |
| H A D | dsp_dtmf.c | 52 int hardware = 1; in dsp_dtmf_hardware() local
58 hardware = 0; in dsp_dtmf_hardware()
66 hardware = 0; in dsp_dtmf_hardware()
73 hardware = 0; in dsp_dtmf_hardware()
81 hardware = 0; in dsp_dtmf_hardware()
89 hardware = 0; in dsp_dtmf_hardware()
92 dsp->dtmf.hardware = hardware; in dsp_dtmf_hardware()
93 dsp->dtmf.software = !hardware; in dsp_dtmf_hardware()
|
| /OK3568_Linux_fs/u-boot/lib/avb/libavb_user/ |
| H A D | Kconfig | 2 bool "Android AVB read/write hardware"
5 read/write hardware image, like vbmeta, misc, and
21 bool "Android AVB read/write hardware for spl"
24 read/write hardware image, like vbmeta, misc, and
29 bool "Android AVB read/write hardware for tpl"
32 read/write hardware image, like vbmeta, misc, and
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-trigger-pattern | 19 Specify a hardware pattern for the LED, for LED hardware that
21 to some preprogrammed hardware patterns. It deactivates any active
24 Since different LED hardware can have different semantics of
25 hardware patterns, each driver is expected to provide its own
26 description for the hardware patterns in their documentation
|