Home
last modified time | relevance | path

Searched refs:hardware (Results 1 – 25 of 137) sorted by relevance

123456

/rk3399_rockchip-uboot/drivers/crypto/rockchip/
H A Drkce_core.c48 #define GET_RKCE_REG(hardware) (((struct rkce_hardware *)(hardware))->rkce_reg) argument
49 #define CHECK_RKCE_INITED(hardware) WARN_ON_ONCE(!(hardware) || \ argument
50 !(((struct rkce_hardware *)(hardware))->rkce_reg))
290 struct rkce_hardware *hardware; in rkce_hardware_alloc() local
297 hardware = malloc(sizeof(*hardware)); in rkce_hardware_alloc()
298 if (!hardware) in rkce_hardware_alloc()
301 hardware->rkce_reg = reg_base; in rkce_hardware_alloc()
303 if (rkce_init(hardware) != 0) { in rkce_hardware_alloc()
304 free(hardware); in rkce_hardware_alloc()
308 rk_debug("hardware = %p", hardware); in rkce_hardware_alloc()
[all …]
H A Dcrypto_ce.c47 void *hardware; member
110 if (!priv->hardware) in rk_crypto_soft_reset()
115 rkce_soft_reset(priv->hardware, reset_sel); in rk_crypto_soft_reset()
190 if (rkce_hw_algo_valid(priv->hardware, algo_type, map[i].rkce, 0)) in rk_load_map()
368 ret = rkce_push_td_sync(priv->hardware, td, RKCE_HASH_TIMEOUT_MS); in rk_sha_update()
829 ret = rkce_push_td_sync(priv->hardware, hw_ctx->td_aad, RKCE_SYMM_TIMEOUT_MS); in rk_crypto_cipher()
860 ret = rkce_push_td_sync(priv->hardware, hw_ctx->td_aad, RKCE_SYMM_TIMEOUT_MS); in rk_crypto_cipher()
879 ret = rkce_push_td_sync(priv->hardware, hw_ctx->td, RKCE_SYMM_TIMEOUT_MS); in rk_crypto_cipher()
937 addr = rkce_get_keytable_addr(priv->hardware); in rockchip_get_keytable_addr()
1257 priv->hardware = rkce_hardware_alloc((void *)priv->reg); in rockchip_crypto_probe()
[all …]
/rk3399_rockchip-uboot/doc/
H A DREADME.bus_vcxk25 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
H A DREADME.drivers.eth70 * if your device has dedicated hardware storage for the
106 < 0 - failure (hardware failure, not probe failure)
113 Other than locating the MAC address in dedicated hardware storage, you should
114 not touch the hardware in anyway. That step is handled in the driver-specific
130 The init function checks the hardware (probing/identifying) and gets it ready
142 The recv function should process packets as long as the hardware has them
143 readily available before returning. i.e. you should drain the hardware fifo.
168 The halt function should turn off / disable the hardware and place it back in
H A DREADME.N121314 interrupt controller with 6 hardware interrupt signals.
25 - Optional hardware page table walker.
H A DREADME.arm645 The initial arm64 U-Boot port was developed before hardware was available,
7 These days U-Boot runs on a variety of 64-bit capable ARM hardware, from
15 classical firmware (like initial hardware setup, CPU errata workarounds
H A DREADME.enetaddr16 Note: only used when mandatory due to hardware design etc...
33 1. Read from hardware in initialize() function
42 4. Program the address into hardware if the following conditions are met:
47 Previous behavior had the MAC address always being programmed into hardware
54 If the hardware design mandates that the MAC address is stored in some special
H A DREADME.atmel_mci1 How to use SD/MMC cards with Atmel SoCs having MCI hardware
5 This is a new approach to use Atmel MCI hardware with the
H A DREADME.memory-test2 hardware, or when using a sloppy port on some board, is memory errors.
3 In most cases these are not caused by failing hardware, but by
14 memory banks on this piece of hardware. The code is supposed to be
17 catch 99% of hardware related (i. e. reliably reproducible) memory
H A DREADME.nand202 hardware ECC correction. This is useful for platforms which have ELM
203 hardware engine and use NAND boot mode.
215 1-bit Hamming code using GPMC hardware.
223 - ecc calculation using GPMC hardware engine,
229 - ecc calculation using GPMC hardware engine,
230 - error detection using ELM hardware engine.
233 - ecc calculation using GPMC hardware engine,
234 - error detection using ELM hardware engine.
240 - hardware engines present in SoC.
/rk3399_rockchip-uboot/lib/avb/libavb_user/
H A DKconfig2 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
/rk3399_rockchip-uboot/lib/avb/rk_avb_user/
H A DKconfig5 read/write hardware image, like vbmeta, misc, and
13 read/write hardware image, like vbmeta, misc, and
21 read/write hardware image, like vbmeta, misc, and
/rk3399_rockchip-uboot/lib/efi_loader/
H A DKconfig16 Some hardware does not support DMA to full 64bit addresses. For this
17 hardware we can create a bounce buffer so that payloads don't have to
/rk3399_rockchip-uboot/doc/device-tree-bindings/leds/
H A Dleds-bcm6328.txt4 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
/rk3399_rockchip-uboot/doc/device-tree-bindings/thermal/
H A Drockchip-thermal.txt16 - rockchip,hw-tshut-temp : The hardware-controlled shutdown temperature value.
17 - rockchip,hw-tshut-mode : The hardware-controlled shutdown mode 0:CRU 1:GPIO.
18 - rockchip,hw-tshut-polarity : The hardware-controlled active polarity 0:LOW
/rk3399_rockchip-uboot/drivers/phy/
H A DKconfig11 devices. PHY devices are dedicated hardware that handle the physical
27 devices. PHY devices are dedicated hardware that handle the physical
51 hardware exists.
60 hardware exists.
/rk3399_rockchip-uboot/drivers/reset/
H A DKconfig7 Enable support for the reset controller driver class. Many hardware
9 reset controller hardware module within the chip. In U-Boot, reset
19 Enable support for the reset controller driver class. Many hardware
21 reset controller hardware module within the chip. In U-Boot, reset
/rk3399_rockchip-uboot/doc/device-tree-bindings/cpu/
H A Dnios2.txt25 - altr,has-mul: Specifies CPU hardware multipy support.
26 - altr,has-div: Specifies CPU hardware divide support
/rk3399_rockchip-uboot/doc/device-tree-bindings/mailbox/
H A Dnvidia,tegra186-hsp.txt4 together. It provides a set of hardware synchronization primitives for
6 protocols can use hardware synchronization primitives, when operating between
/rk3399_rockchip-uboot/doc/device-tree-bindings/pinctrl/
H A Dpinctrl-bindings.txt6 just like any other hardware module.
10 node in device tree, just like any other hardware module.
91 * but in use on an SoC that doesn't have any pin control hardware
160 For hardware where pin multiplexing configurations have to be specified for
188 for all hardware or binding structures. Each individual binding document
231 sleep-hardware-state - indicate this is sleep related state which will be programmed
270 binding for the hardware defines:
274 specific bindings for the hardware defines:
278 - bias-pull-up, -down and -pin-default take as optional argument on hardware
/rk3399_rockchip-uboot/arch/arm/cpu/armv7/
H A DKconfig31 bool "Enable support for hardware virtualization" if EXPERT
51 CPUs in the actual hardware implementation.
/rk3399_rockchip-uboot/drivers/usb/host/
H A DKconfig14 "SuperSpeed" host controller hardware.
74 "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
180 USB 1.1 host controller hardware. It does more in hardware than Intel's
182 say Y. On most non-x86 systems, and on x86 hardware that's not using a
217 accessing the USB hardware in the PC (which is also called the USB
/rk3399_rockchip-uboot/test/
H A DREADME22 allows test to be executed without needing target hardware. The 'sandbox'
30 either on sandbox or on real hardware. It relies on the U-Boot console to
46 Tbot provides a way to execute tests on target hardware. It is intended for
/rk3399_rockchip-uboot/drivers/power/io-domain/
H A DKconfig10 means to control such power management hardware.
/rk3399_rockchip-uboot/doc/device-tree-bindings/video/
H A Dsimple-framebuffer.txt4 with the assumption that the display hardware has already been set up to scan

123456