- 21 Dec, 2023 6 commits
-
-
Arnd Bergmann authored
Merge tag 'mtk-dts64-for-v6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux into soc/dt MediaTek ARM64 DeviceTree updates for v6.8 This adds devicetree bindings and nodes for: - Media Data Path 3 (MDP3) bindings and enablement on MT8195 - Smart Voltage Scaling (SVS) on MT8195 - LVTS SoC thermal on MT8192 - MT8188 SoC along with its resets, display bindings, and more - MT8183 hardware video decoder (mtk-vcodec-dec) Adds the following new machines: - MT8188 Evaluation Board (EVB) - MT8183 Chromebooks: Kukui-Katsu, Jacuzzi-Makomo, Pico, Pico6 Performs cleanups for various MediaTek SoCs and PMICs, and also includes some spare fixes. * tag 'mtk-dts64-for-v6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux: (60 commits) arm64: dts: mediatek: mt8192: Add Smart Voltage Scaling node arm64: dts: mediatek: mt8195: Add SVS node and reduce LVTS_AP iospace arm64: dts: mediatek: mt8183: Change iospaces for thermal and svs arm64: dts: mediatek: mt8186: fix address warning for ADSP mailboxes arm64: dts: mediatek: mt8186: Fix alias prefix for ovl_2l0 arm64: dts: mt6358: Drop bogus "regulator-fixed" compatible properties arm64: dts: mt8183: kukui-jacuzzi: Drop bogus anx7625 panel_flag property arm64: dts: Add MediaTek MT8188 dts and evaluation board and Makefile dt-bindings: soc: mediatek: pwrap: Modify compatible for MT8188 dt-bindings: arm: mediatek: Add mt8188 pericfg compatible dt-bindings: arm: Add compatible for MediaTek MT8188 arm64: dts: mediatek: mt8195: add DSI and MIPI DPHY nodes dt-bindings: display: mediatek: dsi: add compatible for MediaTek MT8195 arm64: dts: mediatek: mt6358: Merge ldo_vcn33_* regulators dt-bindings: arm: mediatek: convert audsys and mt2701-afe-pcm to yaml arm64: dts: mediatek: mt8195: add MDP3 nodes arm64: dts: mediatek: mt8195: revise VDOSYS RDMA node name arm64: dts: mediatek: mt8183: correct MDP3 DMA-related nodes dt-bindings: display: mediatek: padding: add compatible for MT8195 dt-bindings: display: mediatek: split: add compatible for MT8195 ... Link: https://lore.kernel.org/r/20231212114515.121695-1-angelogioacchino.delregno@collabora.comSigned-off-by:
Arnd Bergmann <arnd@arndb.de>
-
Arnd Bergmann authored
Merge tag 'samsung-dt-6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into soc/dt Samsung DTS ARM changes for v6.8 1. Exynos4212 and Exynos4412: Final fixes for dtbs_check warnings. Replace duplicate PMU node in FIMC IS node with syscon phandle. The old solution of duplicated PMU node was not a correct representation of the hardware and could have concurrent access issues. The DTS change depends on media FIMC IS drivers changes already merged in previous cycle, thus it is not fully backwards-compatible. It is a necessary trade-off in fixing wrong description in DTS. With this fix, `make dtbs_check` status looks like: S3C6410: no warnings Exynos: no warnings, one undocumented compatible S5PV210: one warning, one undocumented compatible 2. Exynos4210, Exynos4212, Exynos4412, S5PV210: Correct FIMC IS camera ranges and IO addresses to silence dtc W=1 warnings. No functional impact expected. After this fix, there are no dtc W=1 warnings on all ARMv7 platforms. 3. Galaxy I9100: Fix 12-second hang during boot by enabling regulator (real cause not really known), add touch keys and accelerometer. * tag 'samsung-dt-6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux: ARM: dts: samsung: exynos4210-i9100: Add accelerometer node ARM: dts: samsung: exynos4210-i9100: Add node for touch keys ARM: dts: samsung: exynos4210-i9100: Unconditionally enable LDO12 ARM: dts: samsung: s5pv210: fix camera unit addresses/ranges ARM: dts: samsung: exynos4: fix camera unit addresses/ranges ARM: dts: samsung: exynos4x12: replace duplicate pmu node with phandle Link: https://lore.kernel.org/r/20231212093105.13938-2-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'samsung-dt64-6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into soc/dt Samsung DTS ARM64 changes for v6.8 Two (and a half) major items are coming with this pull request: 1. Add specific compatibles to all Samsung Exynos and Tesla FSD blocks, because that's what guidelines expect [1] and is generally recommended practice. Existing compatibles are left untouched, thus no driver changes are needed. The work only cleans things up, so any future contributions will use recommended style: specific and fallback compatibles. Since no driver changes are needed in this work and the DTS is directly affected by bindings change (running tests with `make dtbs_check`), this pull includes all bindings changes, even though usual practice is that bindings come via driver subsystem. Keeping everything here makes review and testing easier. Also will allow us to avoid conflicts related to new platforms (see below). 2. Add ExynosAutov920 SoC and SADK board (Samsung Automotive Development Kit) with minimal support so far: serial console, GPIO-based keys and PWM fan. 3. Add few bindings for upcoming Google GS101 SoC. This pull request does not include its DTS yet, just few reviewed dependencies. DTS will be coming soon. [1] Documentation/devicetree/bindings/writing-bindings.rst * tag 'samsung-dt64-6.8' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux: (38 commits) arm64: dts: exynos: add minimal support for exynosautov920 sadk board arm64: dts: exynos: add initial support for exynosautov920 SoC dt-bindings: samsung: exynos-sysreg: combine exynosautov920 with other enum dt-bindings: soc: google: exynos-sysreg: add dedicated SYSREG compatibles to GS101 dt-bindings: clock: Add Google gs101 clock management unit bindings dt-bindings: soc: samsung: exynos-pmu: Add gs101 compatible arm64: dts: fsd: add specific compatibles for Tesla FSD dt-bindings: watchdog: samsung: add specific compatible for Tesla FSD dt-bindings: samsung: exynos-pmu: add specific compatible for Tesla FSD dt-bindings: serial: samsung: add specific compatible for Tesla FSD dt-bindings: pwm: samsung: add specific compatible for Tesla FSD dt-bindings: i2c: exynos5: add specific compatible for Tesla FSD arm64: dts: exynosautov9: use Exynos7 fallbacks for pin wake-up controller arm64: dts: exynos850: use Exynos7 fallbacks for pin wake-up controllers dt-bindings: hwinfo: samsung,exynos-chipid: add exynosautov920 compatible dt-bindings: arm: samsung: Document exynosautov920 SADK board binding dt-bindings: pwm: samsung: add exynosautov920 compatible dt-bindings: serial: samsung: add exynosautov920-uart compatible dt-bindings: samsung: usi: add exynosautov920-usi compatible dt-bindings: samsung: exynos-pmu: add exynosautov920 compatible ... Link: https://lore.kernel.org/r/20231212093105.13938-1-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Krzysztof Kozlowski authored
The DTS code coding style expects exactly one space before and after '=' sign. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Link: https://lore.kernel.org/r/20231212-ux500-dts-v1-1-5a31b6742d85@linaro.orgSigned-off-by:
-
Arnd Bergmann authored
Merge tag 'omap-for-v6.8/dt-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into soc/dt Devicetree changes for omaps - A series of patches to reorganize Motorola Mapphone related files to add support for tablets as the peripherals are different compared to the phones - Apply am57xx-idk overlays to base dtbs - Extcon update to use id-gpios and vbus-gpios - Update omap4-epson-embt2ws to enable wlan clock and bluetooth-gnss - Update for logicpd-torpedo to use bluetooth-gnss node name * tag 'omap-for-v6.8/dt-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap: ARM: dts: omap4-embt2ws: Add Bluetooth ARM: dts: omap: logicpd-torpedo: do not disguise GNSS device ARM: dts: omap4-embt2ws: enable 32K clock on WLAN ARM: dts: ti/omap: Replace deprecated extcon-usb-gpio id-gpio/vbus-gpio properties arm: dts: omap: Apply am57xx-idk overlays to base dtbs ARM: dts: motorola-mapphone: Add basic support for mz609 and mz617 ARM: dts: motorola-mapphone: Move handset devices to a common file ARM: dts: motorola-mapphone: Move LCD to common file for xt875 and xt894 dt-bindings: omap: Add Motorola mapphone mz609 and mz617 tablets Link: https://lore.kernel.org/r/pull-1702037869-295608@atomide.comSigned-off-by:
-
https://github.com/hisilicon/linux-hisiArnd Bergmann authored
ARM64: DT: HiSilicon ARM64 DT updates for v6.8 - Merge the hi3620-clock binding into hisilicon,sysctrl - Clean up the hikey970 PMIC dtsi * tag 'hisi-arm64-dt-for-6.8' of https://github.com/hisilicon/linux-hisi: arm64: dts: hisilicon: hikey970-pmic: clean up SPMI node arm64: dts: hisilicon: hikey970-pmic: fix regulator cells properties dt-bindings: hisilicon: Merge hi3620-clock into hisilicon,sysctrl binding Link: https://lore.kernel.org/r/6572C4C8.6050401@hisilicon.comSigned-off-by:
-
- 11 Dec, 2023 34 commits
-
-
AngeloGioacchino Del Regno authored
Add the MediaTek SVS node: this will lower the voltage of various components of the SoC based on chip quality (read from fuses) in order to save power and generate less heat. Link: https://lore.kernel.org/r/20231121125044.78642-20-angelogioacchino.delregno@collabora.comSigned-off-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
-
AngeloGioacchino Del Regno authored
Add the MediaTek SVS node: this will lower the voltage of various components of the SoC based on chip quality (read from fuses) in order to save power and generate less heat. Also, reduce the LVTS_AP iospace to 0xc00, because that's exactly where SVS starts. - LVTS_AP start: 0x1100b000 length: 0xc00 - SVS start: 0x1100bc00 length: 0x400 Link: https://lore.kernel.org/r/20231121125044.78642-21-angelogioacchino.delregno@collabora.comSigned-off-by:
-
AngeloGioacchino Del Regno authored
The SVS iospace starts at 0x1100bc00 and not at 0x1100b000 as the latter is the thermal sensor iospace instead. Change the iospaces for both as following: - Thermal: 0x1100b000, length 0xc00 - SVS: 0x1100bc00, length 0x400 Please note that while this would be a breaking change for SVS (but not for thermal sensors), it doesn't matter because the svs driver never worked anyway because of the missing trips in tzts2, causing that thermal zone to never actually register, hence the SVS driver to fail probing anyway. Link: https://lore.kernel.org/r/20231121125044.78642-2-angelogioacchino.delregno@collabora.comSigned-off-by:
-
Eugen Hristev authored
Fix warnings reported by dtbs_check : arch/arm64/boot/dts/mediatek/mt8186.dtsi:1163.35-1168.5: Warning (simple_bus_reg): /soc/mailbox@10686000: simple-bus unit address format error, expected "10686100" arch/arm64/boot/dts/mediatek/mt8186.dtsi:1170.35-1175.5: Warning (simple_bus_reg): /soc/mailbox@10687000: simple-bus unit address format error, expected "10687100" by having the right bus address as node name. Fixes: 379cf0e6 ("arm64: dts: mediatek: mt8186: Add ADSP mailbox nodes") Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Link: https://lore.kernel.org/r/20231204135533.21327-1-eugen.hristev@collabora.comSigned-off-by:
-
Chen-Yu Tsai authored
The alias prefix for ovl_2l (2 layer overlay) is "ovl-2l", not "ovl_2l". Fix this. Fixes: 7e07d332 ("arm64: dts: mediatek: mt8186: Add display nodes") Signed-off-by:
Chen-Yu Tsai <wenst@chromium.org> Link: https://lore.kernel.org/r/20231130074032.913511-4-wenst@chromium.orgSigned-off-by:
-
Chen-Yu Tsai authored
Whether a regulator under the MT6358 PMIC is a fixed regulator or not is derived from the node name. Compatible string properties are not used. This causes validation errors after the regulator binding is converted to DT schema. Drop the bogus "regulator-fixed" compatible properties from the PMIC's regulator sub-nodes. Fixes: 9f887222 ("arm64: dts: mt6358: add PMIC MT6358 related nodes") Signed-off-by:
-
Chen-Yu Tsai authored
The panel_flag property was used in ChromeOS's downstream kernel. It was used to signal whether the downstream device was a fixed panel or a connector for an external display. This property was dropped in favor of standard OF graph descrptions of downstream display panels and bridges. Drop the property from the device tree file. Fixes: cabc71b0 ("arm64: dts: mt8183: Add kukui-jacuzzi-damu board") Signed-off-by:
-
jason-ch chen authored
MT8188 is a SoC based on 64bit ARMv8 architecture. It contains 6 CA55 and 2 CA78 cores. MT8188 share many HW IP with MT65xx series. We add basic chip support for MediaTek MT8188 on evaluation board. Signed-off-by:
jason-ch chen <Jason-ch.Chen@mediatek.com> Reviewed-by:
Alexandre Mergnat <amergnat@baylibre.com> Link: https://lore.kernel.org/r/20231023083839.24453-5-jason-ch.chen@mediatek.comSigned-off-by:
-
jason-ch chen authored
The reason for changing the patch was that while MT8188 uses the same pwrap as MT8195, the original code was only applicable to 'compatible = "mediatek,mt8188-pwrap"'. To resolve the DTBS check warning that '['mediatek,mt8188-pwrap', 'mediatek,mt8195-pwrap', 'syscon'] is too long', it is necessary to modify the code. Signed-off-by:
Conor Dooley <conor.dooley@microchip.com> Reviewed-by:
-
jason-ch chen authored
Add mt8188 pericfg compatible to binding document. Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20231023083839.24453-3-jason-ch.chen@mediatek.comSigned-off-by:
-
jason-ch chen authored
This commit adds dt-binding documentation for the MediaTek MT8188 reference board. Signed-off-by:
-
Michael Walle authored
Add the two DSI controller node and the associated DPHY nodes. Individual boards have to enable them in the board device tree. Signed-off-by:
Michael Walle <mwalle@kernel.org> Reviewed-by:
-
Michael Walle authored
Add the compatible string for MediaTek MT8195 SoC, using the same DSI block as the MT8183. Signed-off-by:
-
Chen-Yu Tsai authored
The ldo_vcn33_bt and ldo_vcn33_wifi regulators are actually the same regulator, having the same voltage setting and output pin. There are simply two enable bits that are ORed together to enable the regulator. Having two regulators representing the same output pin is misleading from a design matching standpoint, and also error-prone in driver implementations. Now that the bindings have these two merged, merge them in the device tree as well. Neither vcn33 regulators are referenced in upstream device trees. As far as hardware designs go, none of the Chromebooks using MT8183 w/ MT6358 use this output. Signed-off-by:
-
Eugen Hristev authored
Convert the mediatek,audsys binding to YAML, together with the associated binding bindings/sound/mt2701-afe-pcm.yaml . Signed-off-by:
-
Moudy Ho authored
Add device nodes for Media Data Path 3 (MDP3) modules. Signed-off-by:
Moudy Ho <moudy.ho@mediatek.com> Signed-off-by:
-
Moudy Ho authored
DMA-related nodes have their own standardized naming. Therefore, the MT8195 VDOSYS RDMA has been unified and corrected. Additionally, these modifications will facilitate the further integration of bindings. Fixes: 92d2c23d ("arm64: dts: mt8195: add display node for vdosys1") Signed-off-by:
-
Moudy Ho authored
In order to generalize the node names, the DMA-related nodes corresponding to MT8183 MDP3 need to be corrected. Fixes: 60a2fb8d ("arm64: dts: mt8183: add MediaTek MDP3 nodes") Signed-off-by:
-
Moudy Ho authored
Add a compatible string for the PADDING block in MediaTek MT8195 that is controlled by MDP3. Signed-off-by:
-
Moudy Ho authored
Add compatible string and GCE property for MT8195 SPLIT, of which is operated by MDP3. Signed-off-by:
-
Moudy Ho authored
Add a compatible string for the OVL block in MediaTek MT8195 that is controlled by MDP3. Signed-off-by:
-
Moudy Ho authored
Add a compatible string for the MERGE block in MediaTek MT8195 that is controlled by MDP3. Signed-off-by:
-
Moudy Ho authored
Add a compatible string for the COLOR block in MediaTek MT8195 that is controlled by MDP3. Signed-off-by:
-
Moudy Ho authored
Add a compatible string for the AAL block in MediaTek MT8195 that is controlled by MDP3. Signed-off-by:
-
Moudy Ho authored
Add the fundamental hardware configuration of component TDSHP, which is controlled by MDP3 on MT8195. Signed-off-by:
-
Moudy Ho authored
Add the fundamental hardware configuration of component TCC, which is controlled by MDP3 on MT8195. Signed-off-by:
-
Moudy Ho authored
Add the fundamental hardware configuration of component STITCH, which is controlled by MDP3 on MT8195. Signed-off-by:
-
Moudy Ho authored
Add the fundamental hardware configuration of component HDR, which is controlled by MDP3 on MT8195. Signed-off-by:
-
Moudy Ho authored
Add the fundamental hardware configuration of component FG, which is controlled by MDP3 on MT8195. Signed-off-by:
AngeloGioacchino Del Regno <zangelogioacchino.delregno@collabora.com> Reviewed-by:
-
Moudy Ho authored
MT8195 WROT inherited from MT8183, add the corresponding compatible name to it. Signed-off-by:
-
Moudy Ho authored
MT8195 RSZ inherited from MT8183, add the corresponding compatible name to it. Signed-off-by:
-
Moudy Ho authored
Added the configuration for MT8195 RDMA. In comparison to MT8183, it no longer shares SRAM with RSZ, and there are now preconfigured 5 mbox. Signed-off-by:
-
Moudy Ho authored
To simplify maintenance and avoid branches, the identical component should be merged and placed in the path belonging to the MDP (from display/* to media/*). In addition, currently only MDP utilizes RDMA through CMDQ, and the necessary properties for "mediatek,gce-events", and "mboxes" have been set up for this purpose. Within DISP, it directly receives component interrupt signals. Signed-off-by:
-
Moudy Ho authored
The DMA-related nodes RDMA/WROT in MDP3 should be changed to generic names. In addition, fix improper space indent in example. Fixes: 4ad7b396 ("media: dt-binding: mediatek: add bindings for MediaTek MDP3 components") Signed-off-by:
-
