Skip to contentSkip to conversation

Add support for MediaTek MT8195 demo board

PATCH Superseded Fabien Parent 5 participants 11 messages Mar 27, 2022 – Apr 1, 2022

Subsystems (2)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

v2 cover Add support for MediaTek MT8195 demo board

This patch serie adds basic support for the MediaTek MT8195 demo board. For now the support is pretty basic and allow just to boot, use USB, and the SD card.

When more IO support will be added for MT8195, new changes will be pushed to the device-tree of the MT8195 demo board to support these IOs as well.

This serie depends on the following patches:
[0] https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
[1] https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

Fabien Parent (4):
dt-bindings: arm64: dts: mediatek: Add mt8195-demo board
arm64: dts: mediatek: Add device-tree for MT8195 Demo board
arm64: defconfig: enable MT6359 regulator driver
arm64: defconfig: enable some mt6360 PMIC drivers

 .../devicetree/bindings/arm/mediatek.yaml     |   1 +
 arch/arm64/boot/dts/mediatek/Makefile         |   1 +
 arch/arm64/boot/dts/mediatek/mt8195-demo.dts  | 447 ++++++++++++++++++
 arch/arm64/configs/defconfig                  |   4 +
 4 files changed, 453 insertions(+)
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts
Signature · 7 lines
2.35.1


_______________________________________________
Linux-mediatek mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-mediatek
#1 lore raw

PATCH v2 1/4 dt-bindings: arm64: dts: mediatek: Add mt8195-demo board

Add bindings for the MediaTek mt8195-demo board.

---
v2:
* move compatible next to the MT8195-EVB compatible

 Documentation/devicetree/bindings/arm/mediatek.yaml | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/arm/mediatek.yaml +1 -0
index ab0593c77321..024a45300da5 100644
@@ -133,6 +133,7 @@ properties:
           - const: mediatek,mt8183
       - items:
           - enum:
+              - mediatek,mt8195-demo
               - mediatek,mt8195-evb
           - const: mediatek,mt8195
       - description: Google Burnet (HP Chromebook x360 11MK G3 EE)
Signature · 1 line
2.35.1
#3 lore raw

PATCH v2 2/4 arm64: dts: mediatek: Add device-tree for MT8195 Demo board

In reply to Fabien Parent

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

 arch/arm64/boot/dts/mediatek/Makefile        |   1 +
 arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
 2 files changed, 448 insertions(+)
 create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts
arch/arm64/boot/dts/mediatek/Makefile +1 -0
index 5da29e7223e4..c7d4636a2cb7 100644
@@ -38,5 +38,6 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-kukui-krane-sku0.dtb
 dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-kukui-krane-sku176.dtb
 dtb-$(CONFIG_ARCH_MEDIATEK) += mt8183-pumpkin.dtb
 dtb-$(CONFIG_ARCH_MEDIATEK) += mt8192-evb.dtb
+dtb-$(CONFIG_ARCH_MEDIATEK) += mt8195-demo.dtb
 dtb-$(CONFIG_ARCH_MEDIATEK) += mt8195-evb.dtb
 dtb-$(CONFIG_ARCH_MEDIATEK) += mt8516-pumpkin.dtb
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +447 -0

447 lines not on this page · raw message

Signature · 1 line
2.35.1
#4 lore raw

Re: [PATCH v2 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board

Il 27/03/22 22:03, Fabien Parent ha scritto:

Quoted 39 lines

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

  arch/arm64/boot/dts/mediatek/Makefile        |   1 +
  arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
  2 files changed, 448 insertions(+)

create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts

..snip..

Quoted 6 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +0 -0
new file mode 100644
index 000000000000..d94b4e01159a
@@ -0,0 +1,447 @@

..snip..

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 72

Quoted 8 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +8 -0
+
+	gpio-keys {
+		compatible = "gpio-keys";
+		input-name = "gpio-keys";
+		pinctrl-names = "default";
+		pinctrl-0 = <&gpio_keys_pins>;
+
+		key-0 {

key-volup is more descriptive, can you please change that?

Quoted 9 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +9 -0
+			gpios = <&pio 106 GPIO_ACTIVE_LOW>;
+			label = "volume_up";
+			linux,code = <KEY_VOLUMEUP>;
+			wakeup-source;
+			debounce-interval = <15>;
+		};
+	};
+};
+

..snip..

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 124

Quoted 4 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +4 -0
+
+&pmic {
+	interrupt-parent = <&pio>;
+	interrupts = <222 IRQ_TYPE_LEVEL_HIGH>;

I would instead use interrupts-extended here:

	interrupts-extended = <&pio 222 IRQ_TYPE_LEVEL_HIGH>;
Quoted 4 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +4 -0
+};
+
+&i2c6 {
+	clock-frequency = <400000>;

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 138

Quoted 10 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +10 -0
+	pinctrl-0 = <&i2c6_pins>;
+	pinctrl-names = "default";
+	status = "okay";
+
+	mt6360: pmic@34 {
+		compatible = "mediatek,mt6360";
+		reg = <0x34>;
+		interrupt-controller;
+		interrupt-parent = <&pio>;
+		interrupts = <101 IRQ_TYPE_EDGE_FALLING>;

Same here

Quoted 2 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +2 -0
+		interrupt-names = "IRQB";
+

...snip...

Quoted 9 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +9 -0
+
+&pio {
+	mmc0_default_pins: mmc0-default-pins {
+		pins-cmd-dat {
+			pinmux = <PINMUX_GPIO126__FUNC_MSDC0_DAT0>,
+				 <PINMUX_GPIO125__FUNC_MSDC0_DAT1>,
+				 <PINMUX_GPIO124__FUNC_MSDC0_DAT2>,
+				 <PINMUX_GPIO123__FUNC_MSDC0_DAT3>,
+				 <PINMUX_GPIO119__FUNC_MSDC0_DAT4>,

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 327

Quoted 10 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +10 -0
+				 <PINMUX_GPIO118__FUNC_MSDC0_DAT5>,
+				 <PINMUX_GPIO117__FUNC_MSDC0_DAT6>,
+				 <PINMUX_GPIO116__FUNC_MSDC0_DAT7>,
+				 <PINMUX_GPIO121__FUNC_MSDC0_CMD>;
+			input-enable;
+			drive-strength = <MTK_DRIVE_6mA>;
+			bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
+		};
+
+		pin-clk {

This is supposed to be "pins-clk", not "pin-clk"... same for all the other instances of the "pin-".

Before pushing patches upstream, please run dtbs_check, as these are all mistakes that will be pointed out by that.

Regards,
Angelo

#5 lore raw

Re: [PATCH v2 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board

Quoted 52 lines · AngeloGioacchino Del Regno

Il 27/03/22 22:03, Fabien Parent ha scritto:

Quoted 39 lines

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

  arch/arm64/boot/dts/mediatek/Makefile        |   1 +
  arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
  2 files changed, 448 insertions(+)

create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts

..snip..

Quoted 6 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +0 -0
new file mode 100644
index 000000000000..d94b4e01159a
@@ -0,0 +1,447 @@

..snip..

Quoted 10 lines

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 72

Quoted 8 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +8 -0
+
+	gpio-keys {
+		compatible = "gpio-keys";
+		input-name = "gpio-keys";
+		pinctrl-names = "default";
+		pinctrl-0 = <&gpio_keys_pins>;
+
+		key-0 {

key-volup is more descriptive, can you please change that?

Which review should I follow, yours or the one from Krzysztof? Because both reviews are contradictory

Quoted 13 lines
Quoted 10 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +9 -0
+			gpios = <&pio 106 GPIO_ACTIVE_LOW>;
+			label = "volume_up";
+			linux,code = <KEY_VOLUMEUP>;
+			wakeup-source;
+			debounce-interval = <15>;
+		};
+	};
+};
+

..snip..

Quoted 8 lines

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 124

Quoted 4 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +4 -0
+
+&pmic {
+	interrupt-parent = <&pio>;
+	interrupts = <222 IRQ_TYPE_LEVEL_HIGH>;

I would instead use interrupts-extended here:

	interrupts-extended = <&pio 222 IRQ_TYPE_LEVEL_HIGH>;

Thanks, it will be fixed in v3.

Quoted 17 lines
Quoted 5 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +4 -0
+};
+
+&i2c6 {
+	clock-frequency = <400000>;

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 138

Quoted 10 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +10 -0
+	pinctrl-0 = <&i2c6_pins>;
+	pinctrl-names = "default";
+	status = "okay";
+
+	mt6360: pmic@34 {
+		compatible = "mediatek,mt6360";
+		reg = <0x34>;
+		interrupt-controller;
+		interrupt-parent = <&pio>;
+		interrupts = <101 IRQ_TYPE_EDGE_FALLING>;

Same here

Thanks, it will be fixed in v3.

Quoted 20 lines
Quoted 3 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +2 -0
+		interrupt-names = "IRQB";
+

...snip...

Quoted 14 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +14 -0
+
+&pio {
+	mmc0_default_pins: mmc0-default-pins {
+		pins-cmd-dat {
+			pinmux = <PINMUX_GPIO126__FUNC_MSDC0_DAT0>,
+				 <PINMUX_GPIO125__FUNC_MSDC0_DAT1>,
+				 <PINMUX_GPIO124__FUNC_MSDC0_DAT2>,
+				 <PINMUX_GPIO123__FUNC_MSDC0_DAT3>,
+				 <PINMUX_GPIO119__FUNC_MSDC0_DAT4>,
+				 <PINMUX_GPIO118__FUNC_MSDC0_DAT5>,
+				 <PINMUX_GPIO117__FUNC_MSDC0_DAT6>,
+				 <PINMUX_GPIO116__FUNC_MSDC0_DAT7>,
+				 <PINMUX_GPIO121__FUNC_MSDC0_CMD>;
+			input-enable;
Quoted 8 lines

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 327

Quoted 5 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +5 -0
+			drive-strength = <MTK_DRIVE_6mA>;
+			bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
+		};
+
+		pin-clk {

This is supposed to be "pins-clk", not "pin-clk"... same for all the other instances of the "pin-".

There is only one pin in that node, so it should be singular, no?

Quoted 7 lines

Before pushing patches upstream, please run dtbs_check, as these are all mistakes that will be pointed out by that.

Regards,
Angelo

#6 lore raw

Re: [PATCH v2 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board

Il 28/03/22 16:41, Fabien Parent ha scritto:

Quoted 64 lines · AngeloGioacchino Del Regno
Quoted 52 lines

Il 27/03/22 22:03, Fabien Parent ha scritto:

Quoted 39 lines

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

   arch/arm64/boot/dts/mediatek/Makefile        |   1 +
   arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
   2 files changed, 448 insertions(+)

create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts

..snip..

Quoted 6 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +0 -0
new file mode 100644
index 000000000000..d94b4e01159a
@@ -0,0 +1,447 @@

..snip..

Quoted 10 lines

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 72

Quoted 8 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +8 -0
+
+	gpio-keys {
+		compatible = "gpio-keys";
+		input-name = "gpio-keys";
+		pinctrl-names = "default";
+		pinctrl-0 = <&gpio_keys_pins>;
+
+		key-0 {

key-volup is more descriptive, can you please change that?

Quoted 2 lines

Which review should I follow, yours or the one from Krzysztof? Because both reviews are contradictory

There are a lot of "vol-down", "vol-up" (etc) instances, lots of which are on Qualcomm device-trees... so I guess this is just about personal preference...

Honestly, before sending my review I forgot to check Krzysztof's one (sorry!!), but I think that this kind of node names is highly subjective... at least, I am not aware of any rule about having to use "generic" names.

Check Documentation/devicetree/bindings/input/gpio-keys.yaml - in the example, you can find "specific" node names, like:

        up {

            label = "GPIO Key UP";

In any case, as I said, it's my personal preference to have it named as something like "key-volup" or "vol-up" or .. a name that is describing the key, but, as a personal preference, it is nothing mandatory, not even from my side.

If anyone else has reasons to disagree, shrug, it's fine :))

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +8 -0
+			gpios = <&pio 106 GPIO_ACTIVE_LOW>;
+			label = "volume_up";
+			linux,code = <KEY_VOLUMEUP>;
+			wakeup-source;
+			debounce-interval = <15>;
+		};
+	};
+};
#7 lore raw

Re: [PATCH v2 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board

Quoted 68 lines · AngeloGioacchino Del Regno

Il 28/03/22 16:41, Fabien Parent ha scritto:

Quoted 64 lines · AngeloGioacchino Del Regno
Quoted 52 lines

Il 27/03/22 22:03, Fabien Parent ha scritto:

Quoted 39 lines

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

   arch/arm64/boot/dts/mediatek/Makefile        |   1 +
   arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
   2 files changed, 448 insertions(+)

create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts

..snip..

Quoted 6 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +0 -0
new file mode 100644
index 000000000000..d94b4e01159a
@@ -0,0 +1,447 @@

..snip..

Quoted 10 lines

arch/arm64/boot/dts/mediatek/mt8195-demo.dts line 72

Quoted 8 lines
arch/arm64/boot/dts/mediatek/mt8195-demo.dts new file +8 -0
+
+	gpio-keys {
+		compatible = "gpio-keys";
+		input-name = "gpio-keys";
+		pinctrl-names = "default";
+		pinctrl-0 = <&gpio_keys_pins>;
+
+		key-0 {

key-volup is more descriptive, can you please change that?

Quoted 2 lines

Which review should I follow, yours or the one from Krzysztof? Because both reviews are contradictory

Quoted 6 lines

There are a lot of "vol-down", "vol-up" (etc) instances, lots of which are on Qualcomm device-trees... so I guess this is just about personal preference...

Honestly, before sending my review I forgot to check Krzysztof's one (sorry!!), but I think that this kind of node names is highly subjective... at least, I am not aware of any rule about having to use "generic" names.

Node names should be generic, not descriptive. See Devicetree specification:
"The name of a node should be somewhat generic, reflecting the function of the device and not its precise programming
model. If appropriate, the name should be one of the following choices:
...
- keyboard

- key

- keys
"

I prefer key-0 but "volup-key" or "key-volup" could work too (but these are still specific, not generic).

Using other DTS as examples is wrong, because most of submissions are wrong and almost half of my bindings and DTS reviews include that comment - generic node names. To be fair, most of my DTS contributions also contained specific node names till I learnt that rule...

Anyway, it's not that important. :)

Thanks for other changes in the DTS.

Quoted 8 lines

Check Documentation/devicetree/bindings/input/gpio-keys.yaml - in the example, you can find "specific" node names, like:

         up {

             label = "GPIO Key UP";
Quoted 5 lines

In any case, as I said, it's my personal preference to have it named as something like "key-volup" or "vol-up" or .. a name that is describing the key, but, as a personal preference, it is nothing mandatory, not even from my side.

If anyone else has reasons to disagree, shrug, it's fine :))

Best regards,
Krzysztof

#8 lore raw

Re: [PATCH v2 2/4] arm64: dts: mediatek: Add device-tree for MT8195 Demo board

In reply to AngeloGioacchino Del Regno
Quoted 42 lines · AngeloGioacchino Del Regno

Il 28/03/22 16:41, Fabien Parent ha scritto:

Quoted 41 lines · AngeloGioacchino Del Regno
Quoted 40 lines

Il 27/03/22 22:03, Fabien Parent ha scritto:

Quoted 39 lines

Add basic device-tree for the MT8195 Demo board. The Demo board is made by MediaTek and has a MT8195 SoC, associated with the MT6359 and MT6360 PMICs, and the MT7921 connectivity chip.

The IOs available on that board are:
* 1 USB Type-C connector with DP aux mode support
* 1 USB Type-A connector
* 1 full size HDMI RX and 1 full size HDMI TX connector
* 1 uSD slot
* 40 pins header
* SPI interface header
* 1 M.2 slot
* 1 audio jack
* 1 micro-USB port for serial debug
* 2 connectors for DSI displays
* 3 connectors for CSI cameras
* 1 connector for a eDP panel
* 1 MMC storage

This commit adds basic support in order to be able to boot.

---
v2:
* remove empty i2c nodes
* remove empty spi node
* remove unused pcie pinctrls
* fixup node nodes to not contains underscore
* rename mt6360 pmic node
* move mmc1 node right after mmc0 node
* use generic node name for gpio-keys
* uniformize pinctrl node names

   arch/arm64/boot/dts/mediatek/Makefile        |   1 +
   arch/arm64/boot/dts/mediatek/mt8195-demo.dts | 447 +++++++++++++++++++
   2 files changed, 448 insertions(+)

create mode 100644 arch/arm64/boot/dts/mediatek/mt8195-demo.dts

Boot-tested to console on i1200-demo board.

#9 lore raw

PATCH v2 3/4 arm64: defconfig: enable MT6359 regulator driver

In reply to Fabien Parent

The PMIC regulators are essentials to be able to boot MediaTek MT8195 based boards to userspace. Like the other MediaTek PMIC regulator driver, let's enable as well the one for the MT6359 PMIC.

---
v2: no changes

 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
index 50aa3d75ab4f..1e521f17cb39 100644
@@ -644,6 +644,7 @@ CONFIG_REGULATOR_MAX77620=y
 CONFIG_REGULATOR_MAX8973=y
 CONFIG_REGULATOR_MP8859=y
 CONFIG_REGULATOR_MT6358=y
+CONFIG_REGULATOR_MT6359=y
 CONFIG_REGULATOR_MT6397=y
 CONFIG_REGULATOR_PCA9450=y
 CONFIG_REGULATOR_PF8X00=y
Signature · 1 line
2.35.1
#10 lore raw

PATCH v2 4/4 arm64: defconfig: enable some mt6360 PMIC drivers

In reply to Fabien Parent

Enable the charger and regulator driver for the MT6360 PMIC. These drivers are essential for some MediaTek MT8195 based boards to boot properly.

---
v2: no changes

 arch/arm64/configs/defconfig | 3 +++
 1 file changed, 3 insertions(+)
arch/arm64/configs/defconfig +3 -0
index 1e521f17cb39..3848246f6727 100644
@@ -565,6 +565,7 @@ CONFIG_SYSCON_REBOOT_MODE=y
 CONFIG_BATTERY_SBS=m
 CONFIG_BATTERY_BQ27XXX=y
 CONFIG_BATTERY_MAX17042=m
+CONFIG_CHARGER_MT6360=m
 CONFIG_CHARGER_BQ25890=m
 CONFIG_CHARGER_BQ25980=m
 CONFIG_SENSORS_ARM_SCMI=y
@@ -625,6 +626,7 @@ CONFIG_MFD_EXYNOS_LPASS=m
 CONFIG_MFD_HI6421_PMIC=y
 CONFIG_MFD_HI655X_PMIC=y
 CONFIG_MFD_MAX77620=y
+CONFIG_MFD_MT6360=y
 CONFIG_MFD_MT6397=y
 CONFIG_MFD_SPMI_PMIC=y
 CONFIG_MFD_RK808=y
@@ -645,6 +647,7 @@ CONFIG_REGULATOR_MAX8973=y
 CONFIG_REGULATOR_MP8859=y
 CONFIG_REGULATOR_MT6358=y
 CONFIG_REGULATOR_MT6359=y
+CONFIG_REGULATOR_MT6360=y
 CONFIG_REGULATOR_MT6397=y
 CONFIG_REGULATOR_PCA9450=y
 CONFIG_REGULATOR_PF8X00=y
Signature · 1 line
2.35.1