...
 
Commits (1686)

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

variables:
GIT_STRATEGY: clone
GIT_DEPTH: 10
DOCKER_DRIVER: overlay2
DOCKER_IMAGE_TAG: v2
###############################
# Standard CIP configurations #
###############################
build:arm_hitachi_omap_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: hitachi_omap_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_moxa_mxc_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: moxa_mxc_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_renesas_shmobile_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: renesas_shmobile_defconfig
CONFIG_LOC: cip-kernel-config
DEVICES: r8a7743-iwg20d-q7 r8a7745-iwg22d-sodimm r8a77470-iwg23s-sbc
DTBS: r8a7743-iwg20d-q7-dbcm-ca.dtb r8a7745-iwg22d-sodimm-dbhd-ca.dtb r8a77470-iwg23s-sbc.dtb
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
test:arm_renesas_shmobile_defconfig:
stage: test
needs: ["build:arm_renesas_shmobile_defconfig"]
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:test-$DOCKER_IMAGE_TAG
when: always
variables:
GIT_STRATEGY: none
script:
- /opt/submit_tests.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_am335x-axm2_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_am335x-axm2_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_am335x-draco_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_am335x-draco_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_am335x-dxr2_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_am335x-dxr2_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_am335x-etamin_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_am335x-etamin_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_am57xx-pxm3.config:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_am57xx-pxm3.config
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_dcu2.config:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_dcu2.config
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_siemens_imx6_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: siemens_imx6_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_toshiba_tegra_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: toshiba_tegra_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:arm_toshiba_zynq_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: arm
CONFIG: toshiba_zynq_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:x86_plathome_obsvx1.config:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: x86
CONFIG: plathome_obsvx1.config
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:x86_siemens_iot2000.config:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: x86
CONFIG: siemens_iot2000.config
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:x86_siemens_server_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: x86
CONFIG: siemens_server_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
build:x86_toshiba_defconfig:
stage: build
image: registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCKER_IMAGE_TAG
variables:
BUILD_ARCH: x86
CONFIG: toshiba_defconfig
CONFIG_LOC: cip-kernel-config
BUILD_ONLY: "true"
script:
- /opt/build_kernel.sh
artifacts:
name: "$CI_JOB_NAME"
when: always
paths:
- output
......@@ -200,6 +200,7 @@ nodes to be present and contain the properties described below.
"qcom,gcc-msm8660"
"qcom,kpss-acc-v1"
"qcom,kpss-acc-v2"
"renesas,apmu"
"rockchip,rk3066-smp"
"ste,dbx500-smp"
......
......@@ -13,6 +13,12 @@ SoCs:
compatible = "renesas,r8a73a4"
- R-Mobile A1 (R8A77400)
compatible = "renesas,r8a7740"
- RZ/G1M (R8A77430)
compatible = "renesas,r8a7743"
- RZ/G1E (R8A77450)
compatible = "renesas,r8a7745"
- RZ/G1C (R8A77470)
compatible = "renesas,r8a77470"
- R-Car M1A (R8A77781)
compatible = "renesas,r8a7778"
- R-Car H1 (R8A77790)
......@@ -45,6 +51,16 @@ Boards:
compatible = "renesas,gose", "renesas,r8a7793"
- Henninger
compatible = "renesas,henninger", "renesas,r8a7791"
- iWave Systems RZ/G1C Single Board Computer (iW-RainboW-G23S)
compatible = "iwave,g23s", "renesas,r8a77470"
- iWave Systems RZ/G1E SODIMM SOM Development Platform (iW-RainboW-G22D)
compatible = "iwave,g22d", "iwave,g22m", "renesas,r8a7745"
- iWave Systems RZ/G1E SODIMM System On Module (iW-RainboW-G22M-SM)
compatible = "iwave,g22m", "renesas,r8a7745"
- iWave Systems RZ/G1M Qseven Development Platform (iW-RainboW-G20D-Qseven)
compatible = "iwave,g20d", "iwave,g20m", "renesas,r8a7743"
- iWave Systems RZ/G1M Qseven System On Module (iW-RainboW-G20M-Qseven)
compatible = "iwave,g20m", "renesas,r8a7743"
- Koelsch (RTP0RC7791SEB00010S)
compatible = "renesas,koelsch", "renesas,r8a7791"
- Kyoto Microcomputer Co. KZM-A9-Dual
......
......@@ -9,6 +9,9 @@ Required Properties:
- compatible: Must be one of the following
- "renesas,r8a73a4-div6-clock" for R8A73A4 (R-Mobile APE6) DIV6 clocks
- "renesas,r8a7740-div6-clock" for R8A7740 (R-Mobile A1) DIV6 clocks
- "renesas,r8a7743-div6-clock" for R8A7743 (RZ/G1M) DIV6 clocks
- "renesas,r8a7745-div6-clock" for R8A7745 (RZ/G1E) DIV6 clocks
- "renesas,r8a77470-div6-clock" for R8A77470 (RZ/G1C) DIV6 clocks
- "renesas,r8a7790-div6-clock" for R8A7790 (R-Car H2) DIV6 clocks
- "renesas,r8a7791-div6-clock" for R8A7791 (R-Car M2-W) DIV6 clocks
- "renesas,r8a7793-div6-clock" for R8A7793 (R-Car M2-N) DIV6 clocks
......
......@@ -13,6 +13,9 @@ Required Properties:
- "renesas,r7s72100-mstp-clocks" for R7S72100 (RZ) MSTP gate clocks
- "renesas,r8a73a4-mstp-clocks" for R8A73A4 (R-Mobile APE6) MSTP gate clocks
- "renesas,r8a7740-mstp-clocks" for R8A7740 (R-Mobile A1) MSTP gate clocks
- "renesas,r8a7743-mstp-clocks" for R8A7743 (RZ/G1M) MSTP gate clocks
- "renesas,r8a7745-mstp-clocks" for R8A7745 (RZ/G1E) MSTP gate clocks
- "renesas,r8a77470-mstp-clocks" for R8A77470 (RZ/G1C) MSTP gate clocks
- "renesas,r8a7778-mstp-clocks" for R8A7778 (R-Car M1) MSTP gate clocks
- "renesas,r8a7779-mstp-clocks" for R8A7779 (R-Car H1) MSTP gate clocks
- "renesas,r8a7790-mstp-clocks" for R8A7790 (R-Car H2) MSTP gate clocks
......
......@@ -8,6 +8,9 @@ CPG Module Stop (MSTP) Clocks.
Required Properties:
- compatible: Must be one of
- "renesas,r8a7743-cpg-clocks" for the r8a7743 CPG
- "renesas,r8a7745-cpg-clocks" for the r8a7745 CPG
- "renesas,r8a77470-cpg-clocks" for the r8a77470 CPG
- "renesas,r8a7790-cpg-clocks" for the r8a7790 CPG
- "renesas,r8a7791-cpg-clocks" for the r8a7791 CPG
- "renesas,r8a7793-cpg-clocks" for the r8a7793 CPG
......
......@@ -3,6 +3,8 @@
Required Properties:
- compatible: must be one of the following.
- "renesas,du-r8a7743" for R8A7743 (RZ/G1M) compatible DU
- "renesas,du-r8a7745" for R8A7745 (RZ/G1E) compatible DU
- "renesas,du-r8a7779" for R8A7779 (R-Car H1) compatible DU
- "renesas,du-r8a7790" for R8A7790 (R-Car H2) compatible DU
- "renesas,du-r8a7791" for R8A7791 (R-Car M2-W) compatible DU
......@@ -24,10 +26,10 @@ Required Properties:
- clock-names: Name of the clocks. This property is model-dependent.
- R8A7779 uses a single functional clock. The clock doesn't need to be
named.
- R8A779[0134] use one functional clock per channel and one clock per LVDS
encoder (if available). The functional clocks must be named "du.x" with
"x" being the channel numerical index. The LVDS clocks must be named
"lvds.x" with "x" being the LVDS encoder numerical index.
- All other DU instances use one functional clock per channel and one
clock per LVDS encoder (if available). The functional clocks must be
named "du.x" with "x" being the channel numerical index. The LVDS clocks
must be named "lvds.x" with "x" being the LVDS encoder numerical index.
- In addition to the functional and encoder clocks, all DU versions also
support externally supplied pixel clocks. Those clocks are optional.
When supplied they must be named "dclkin.x" with "x" being the input
......@@ -41,13 +43,15 @@ bindings specified in Documentation/devicetree/bindings/graph.txt.
The following table lists for each supported model the port number
corresponding to each DU output.
Port 0 Port1 Port2
Port 0 Port1 Port2
-----------------------------------------------------------------------------
R8A7779 (H1) DPAD 0 DPAD 1 -
R8A7790 (H2) DPAD LVDS 0 LVDS 1
R8A7791 (M2-W) DPAD LVDS 0 -
R8A7793 (M2-N) DPAD LVDS 0 -
R8A7794 (E2) DPAD 0 DPAD 1 -
R8A7743 (RZ/G1M) DPAD 0 LVDS 0 -
R8A7745 (RZ/G1E) DPAD 0 DPAD 1 -
R8A7779 (R-Car H1) DPAD 0 DPAD 1 -
R8A7790 (R-Car H2) DPAD 0 LVDS 0 LVDS 1
R8A7791 (R-Car M2-W) DPAD 0 LVDS 0 -
R8A7793 (R-Car M2-N) DPAD 0 LVDS 0 -
R8A7794 (R-Car E2) DPAD 0 DPAD 1 -
Example: R8A7790 (R-Car H2) DU
......
* Renesas R-Car DMA Controller Device Tree bindings
* Renesas R-Car (RZ/G) DMA Controller Device Tree bindings
Renesas R-Car Generation 2 SoCs have multiple multi-channel DMA
controller instances named DMAC capable of serving multiple clients. Channels
......@@ -14,14 +14,25 @@ not described in these device tree bindings.
Required Properties:
- compatible: must contain "renesas,rcar-dmac"
- compatible: "renesas,dmac-<soctype>", "renesas,rcar-dmac" as fallback.
Examples with soctypes are:
- "renesas,dmac-r8a7743" (RZ/G1M)
- "renesas,dmac-r8a7745" (RZ/G1E)
- "renesas,dmac-r8a77470" (RZ/G1C)
- "renesas,dmac-r8a7790" (R-Car H2)
- "renesas,dmac-r8a7791" (R-Car M2-W)
- "renesas,dmac-r8a7792" (R-Car V2H)
- "renesas,dmac-r8a7793" (R-Car M2-N)
- "renesas,dmac-r8a7794" (R-Car E2)
- "renesas,dmac-r8a7795" (R-Car H3)
- reg: base address and length of the registers block for the DMAC
- interrupts: interrupt specifiers for the DMAC, one for each entry in
interrupt-names.
- interrupt-names: one entry per channel, named "ch%u", where %u is the
channel number ranging from zero to the number of channels minus one.
- interrupt-names: one entry for the error interrupt, named "error", plus one
entry per channel, named "ch%u", where %u is the channel number ranging from
zero to the number of channels minus one.
- clock-names: "fck" for the functional clock
- clocks: a list of phandle + clock-specifier pairs, one for each entry
......@@ -35,7 +46,7 @@ Required Properties:
Example: R8A7790 (R-Car H2) SYS-DMACs
dmac0: dma-controller@e6700000 {
compatible = "renesas,rcar-dmac";
compatible = "renesas,dmac-r8a7790", "renesas,rcar-dmac";
reg = <0 0xe6700000 0 0x20000>;
interrupts = <0 197 IRQ_TYPE_LEVEL_HIGH
0 200 IRQ_TYPE_LEVEL_HIGH
......@@ -65,7 +76,7 @@ Example: R8A7790 (R-Car H2) SYS-DMACs
};
dmac1: dma-controller@e6720000 {
compatible = "renesas,rcar-dmac";
compatible = "renesas,dmac-r8a7790", "renesas,rcar-dmac";
reg = <0 0xe6720000 0 0x20000>;
interrupts = <0 220 IRQ_TYPE_LEVEL_HIGH
0 216 IRQ_TYPE_LEVEL_HIGH
......
......@@ -141,9 +141,9 @@ in a lot of designs, some using all 32 bits, some using 18 and some using
first 18 GPIOs, at local offset 0 .. 17, are in use.
If these GPIOs do not happen to be the first N GPIOs at offset 0...N-1, an
additional bitmask is needed to specify which GPIOs are actually in use,
and which are dummies. The bindings for this case has not yet been
specified, but should be specified if/when such hardware appears.
additional set of tuples is needed to specify which GPIOs are unusable, with
the gpio-reserved-ranges binding. This property indicates the start and size
of the GPIOs that can't be used.
Example:
......@@ -153,6 +153,7 @@ gpio-controller@00000000 {
gpio-controller;
#gpio-cells = <2>;
ngpios = <18>;
gpio-reserved-ranges = <0 4>, <12 2>;
}
The GPIO chip may contain GPIO hog definitions. GPIO hogging is a mechanism
......
......@@ -2,7 +2,10 @@
Required Properties:
- compatible: should contain one of the following.
- compatible: should contain one or more of the following:
- "renesas,gpio-r8a7743": for R8A7743 (RZ/G1M) compatible GPIO controller.
- "renesas,gpio-r8a7745": for R8A7745 (RZ/G1E) compatible GPIO controller.
- "renesas,gpio-r8a77470": for R8A77470 (RZ/G1C) compatible GPIO controller.
- "renesas,gpio-r8a7778": for R8A7778 (R-Mobile M1) compatible GPIO controller.
- "renesas,gpio-r8a7779": for R8A7779 (R-Car H1) compatible GPIO controller.
- "renesas,gpio-r8a7790": for R8A7790 (R-Car H2) compatible GPIO controller.
......@@ -10,7 +13,13 @@ Required Properties:
- "renesas,gpio-r8a7793": for R8A7793 (R-Car M2-N) compatible GPIO controller.
- "renesas,gpio-r8a7794": for R8A7794 (R-Car E2) compatible GPIO controller.
- "renesas,gpio-r8a7795": for R8A7795 (R-Car H3) compatible GPIO controller.
- "renesas,gpio-rcar": for generic R-Car GPIO controller.
- "renesas,rcar-gen1-gpio": for a generic R-Car Gen1 GPIO controller.
- "renesas,rcar-gen2-gpio": for a generic R-Car Gen2 or RZ/G1 GPIO controller.
- "renesas,gpio-rcar": deprecated.
When compatible with the generic version nodes must list the
SoC-specific version corresponding to the platform first followed by
the generic version.
- reg: Base address and length of each memory resource used by the GPIO
controller hardware module.
......@@ -22,7 +31,7 @@ Required Properties:
- #gpio-cells: Should be 2. The first cell is the GPIO number and the second
cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>. Only the
GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW flags are supported.
- gpio-ranges: Range of pins managed by the GPIO controller.
- gpio-ranges: See gpio.txt.
Optional properties:
......@@ -30,35 +39,42 @@ Optional properties:
mandatory if the hardware implements a controllable functional clock for
the GPIO instance.
Please refer to gpio.txt in this directory for details of gpio-ranges property
and the common GPIO bindings used by client devices.
- gpio-reserved-ranges: See gpio.txt.
Please refer to gpio.txt in this directory for the common GPIO bindings used by
client devices.