Home
last modified time | relevance | path

Searched refs:R (Results 1 – 25 of 149) sorted by relevance

123456

/Zephyr-latest/drivers/i2c/
DKconfig.rcar1 # Renesas R-Car Gen3 I2C configuration options
7 bool "Renesas R-Car I2C Driver"
11 Enable Renesas R-Car I2C Driver.
/Zephyr-latest/drivers/pwm/
DKconfig.rcar1 # Reneas R-Car PWM configuration options
7 bool "Renesas R-Car PWM Driver"
13 Enable Renesas R-Car PWM Driver.
/Zephyr-latest/drivers/serial/
DKconfig.rcar1 # Renesas R-Car UART configuration options
7 bool "Renesas R-Car UART Driver"
14 Enable Renesas R-Car UART Driver.
/Zephyr-latest/boards/renesas/rcar_h3ulcb/doc/
Drcar_h3ulcb_a57.rst3 R-CAR H3 ARM CA57 (ARMv8)
8 The R-Car H3 is an SOC that features the basic functions for next-generation
13 The R-Car H3 includes:
80 - `Renesas R-Car Development Support website`_
81 - `eLinux R-Car Starter Kit page`_
83 .. _Renesas R-Car Development Support website:
86 .. _eLinux R-Car Starter Kit page:
87 https://elinux.org/R-Car/Boards/H3SK
Drcar_h3ulcb_r7.rst3 Renesas R-Car H3ULCB
8 …ormance of the R-CAR H3 device from Renesas Electronics and it is also used for developing and eva…
10 - The H3 Starter Kit, based on the R-CAR H3 SIP, comes with LPDDR4 @4GB in 2-channel, each 64-bit w…
16 :alt: R-Car starter kit
20 More information about the board can be found at `Renesas R-Car Starter Kit website`_.
29 :alt: R-Car starter kit features
35 - `Renesas R-Car H3 chip`_
40 Here is the current supported features when running Zephyr Project on the R-Car ULCB CR7:
246 - `Renesas R-Car Starter Kit website`_
247 - `Renesas R-Car H3 chip`_
[all …]
/Zephyr-latest/boards/renesas/rcar_spider_s4/doc/
Drcar_spider_a55.rst3 R-CAR Spider S4 (ARM64)
8 R-Car S4 enables to launch Car Server/CoGW with high performance, high-speed networking,
10 evolve into domains and zones. The R-Car S4 solution allows designers to re-use up to 88
11 percent of software code developed for 3rd generation R-Car SoCs and RH850 MCU applications.
17 The R-Car S4 includes:
31 * R-Switch2 (Ether);
76 - `Renesas R-Car Development Support website`_
79 .. _Renesas R-Car Development Support website:
83 https://elinux.org/R-Car/Boards/Spider
Drcar_spider_r52.rst3 Renesas R-Car Spider
9 | R-Car S4 enables the launch of Car Server/CoGW with high performance, high-speed networking,
13 | The R-Car S4 solution allows designers to re-use up to 88 percent of software code developed
14 | for 3rd generation R-Car SoCs and RH850 MCU applications.\
18 The Renesas R-Car Spider board is the Renesas R-Car S4 reference board and is designed for
23 :alt: R-Car S4 Spider
25 More information about the board can be found at `Renesas R-Car S4 Spider`_ website.
34 :alt: R-Car S4 Spider block diagram
40 - `Renesas R-Car S4 chip`_
45 Here are the current supported features when running Zephyr Project on the R-Car S4 Spider CR52:
[all …]
/Zephyr-latest/boards/renesas/rcar_salvator_x/doc/
Drcar_salvator_x.rst3 Renesas R-Car H3 Salvator-X
9 of the R-CAR H3 device from Renesas Electronics and it is also used for developing
10 and evaluating application software for these R-CAR H3.
12 - The H3 Salvator-X, based on the R-CAR H3 SIP, comes with LPDDR4 @4GB in 2-channel,
19 :alt: R-Car Salvator-X kit
21 More information about the board can be found at `Renesas R-Car Development Support website`_.
31 :alt: R-Car Salvator-X features
37 - `Renesas R-Car H3 chip`_
42 Here is the current supported features when running Zephyr Project on the R-Car Salvator-X CR7:
71 :alt: R-Car Salvator-X connections
[all …]
/Zephyr-latest/drivers/can/
DKconfig.rcar1 # Renesas R-Car CAN configuration options
7 bool "Renesas R-Car CAN Driver"
12 Enable Renesas R-Car CAN Driver.
/Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/
Daarch32.rst3 Arm FVP BaseR AEMv8-R AArch32
9 This board configuration uses Armv8-R AEM FVP [1]_ to emulate a generic
10 Armv8-R [2]_ 32-bit hardware platform.
17 The Armv8-R AEM FVP is a free of charge Armv8-R Fixed Virtual Platform. It
18 supports the latest Armv8-R feature set. Please refer to FVP documentation
21 To Run the Fixed Virtual Platform simulation tool you must download "Armv8-R AEM
47 to the official Armv8-R AEM FVP memory map document [4]_.
102 .. [2] Arm Architecture Reference Manual Supplement - Armv8, for Armv8-R AArch32 architecture profi…
Daarch64.rst3 Arm FVP BaseR AEMv8-R
14 This board configuration uses Armv8-R AEM FVP [1]_ to emulate a generic
15 Armv8-R [2]_ 64-bit hardware platform.
22 The Armv8-R AEM FVP is a free of charge Armv8-R Fixed Virtual Platform. It
23 supports the latest Armv8-R feature set. Please refer to FVP documentation
26 To Run the Fixed Virtual Platform simulation tool you must download "Armv8-R AEM
30 The current minimum required version of "Armv8-R AEM FVP" is 11.16.16.
56 to the official Armv8-R AEM FVP memory map document [4]_.
112 .. [2] Arm Architecture Reference Manual Supplement - Armv8, for Armv8-R AArch64 architecture profi…
/Zephyr-latest/boards/renesas/rcar_salvator_xs/doc/
Dindex.rst3 R-CAR Salvator XS M3 ARM CA57 (ARMv8)
8 The R-Car M3-W is an SOC that features the basic functions for next-generation
13 The R-Car M3-W includes:
63 - `Renesas R-Car Development Support website`_
66 .. _Renesas R-Car Development Support website:
70 https://elinux.org/R-Car/Boards/Salvator-XS
/Zephyr-latest/tests/drivers/audio/dmic_api/
DREADME.txt11 * Verify the DMIC can sample from a stereo L/R pair
18 * Verify that invalid channel maps (R/R pair, non-adjacent channels) are
/Zephyr-latest/samples/shields/lmp90100_evb/rtd/
DREADME.rst43 R: 111.15 ohm
45 R: 111.14 ohm
47 R: 111.14 ohm
49 R: 111.13 ohm
/Zephyr-latest/arch/arm64/core/cortex_r/
DKconfig21 The ARMv8-R MPU architecture requires a power-of-two alignment
24 The ARMv8-R MPU requires the active MPU regions be non-overlapping.
25 As a result of this, the ARMv8-R MPU needs to fully partition the
29 of the ARMv8-R background memory map. The application developer may
33 SRAM area covered only by the default ARMv8-R memory map. This
41 of full partitioning the default behavior for the ARMv8-R MPU
/Zephyr-latest/doc/security/standards/
Detsi-303645.rst162 * - R
168 * - R C
251 - R
260 - R
267 - R
289 - R C
297 - R C
307 - R C
328 - R C
346 - R C
[all …]
/Zephyr-latest/subsys/net/lib/lwm2m/
Dlwm2m_obj_connmon.c113 OBJ_FIELD_DATA(CONNMON_NETWORK_BEARER_ID, R, U8),
114 OBJ_FIELD_DATA(CONNMON_AVAIL_NETWORK_BEARER_ID, R, U8),
115 OBJ_FIELD_DATA(CONNMON_RADIO_SIGNAL_STRENGTH, R, S16),
116 OBJ_FIELD_DATA(CONNMON_LINK_QUALITY, R, S16),
117 OBJ_FIELD_DATA(CONNMON_IP_ADDRESSES, R, STRING),
Dlwm2m_obj_location.c47 OBJ_FIELD_DATA(LOCATION_LATITUDE_ID, R, FLOAT),
48 OBJ_FIELD_DATA(LOCATION_LONGITUDE_ID, R, FLOAT),
52 OBJ_FIELD_DATA(LOCATION_TIMESTAMP_ID, R, TIME),
/Zephyr-latest/drivers/ethernet/
DKconfig.e10001 # Intel(R) PRO/1000 Gigabit Ethernet driver configuration options
7 bool "Intel(R) PRO/1000 Gigabit Ethernet driver"
12 Enable Intel(R) PRO/1000 Gigabit Ethernet driver.
/Zephyr-latest/soc/renesas/rcar/
DKconfig1 # Renesas R-Car SoC line
DKconfig.soc1 # Renesas R-Car SoC line
/Zephyr-latest/soc/renesas/rcar/rcar_gen3/
DKconfig.defconfig1 # Renesas R-Car Gen3 SoC line
/Zephyr-latest/soc/renesas/rcar/rcar_gen4/
DKconfig.defconfig1 # Renesas R-Car Gen4 SoC line
/Zephyr-latest/drivers/gpio/
DKconfig.rcar7 bool "Renesas R-Car GPIO"
/Zephyr-latest/samples/userspace/shared_mem/src/
Denc.h29 extern volatile BYTE R[26];

123456