* [PATCH 0/7] Another set of exynos7870 devicetree fixes
@ 2025-09-28 16:43 Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty
` (6 more replies)
0 siblings, 7 replies; 15+ messages in thread
From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar
Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel,
Kaustabh Chakraborty
Applying this patchset will introduce the following:
* All ${x}-names properties will now follow the corresponding ${x}
properties.
* bus-width of mmc0 node of all exynos7870 devices will be explicitly
defined.
Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
Kaustabh Chakraborty (7):
arm64: dts: exynos7870: relocate ${x}-names property after ${x}
arm64: dts: exynos7870-a2corelte: relocate ${x}-names property after ${x}
arm64: dts: exynos7870-j6lte: relocate ${x}-names property after ${x}
arm64: dts: exynos7870-on7xelte: relocate ${x}-names property after ${x}
arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node
arm64: dts: exynos7870-j6lte: add bus-width to mmc0 node
arm64: dts: exynos7870-on7xelte: add bus-width to mmc0 node
.../arm64/boot/dts/exynos/exynos7870-a2corelte.dts | 21 ++--
arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts | 21 ++--
arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts | 21 ++--
arch/arm64/boot/dts/exynos/exynos7870.dtsi | 108 ++++++++++-----------
4 files changed, 87 insertions(+), 84 deletions(-)
---
base-commit: 262858079afde6d367ce3db183c74d8a43a0e83f
change-id: 20250820-exynos7870-dt-fixes-b4ad027cef67
Best regards,
--
Kaustabh Chakraborty <kauschluss@disroot.org>
^ permalink raw reply [flat|nested] 15+ messages in thread* [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-09-28 21:56 ` Krzysztof Kozlowski 2025-09-28 16:43 ` [PATCH 2/7] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty ` (5 subsequent siblings) 6 siblings, 1 reply; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty All ${x}-names properties are conventionally placed after their corresponding ${x} properties. For instance, 'clock-names' must follow 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary changes to follow said convention. No functional changes made. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870.dtsi | 108 ++++++++++++++--------------- 1 file changed, 54 insertions(+), 54 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos7870.dtsi b/arch/arm64/boot/dts/exynos/exynos7870.dtsi index d5d347623b9038b71da55dccdc9084aeaf71618c..48ace70fb958edd28d758f4afea52bc4c7192001 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870.dtsi +++ b/arch/arm64/boot/dts/exynos/exynos7870.dtsi @@ -150,8 +150,6 @@ cmu_peri: clock-controller@101f0000 { reg = <0x101f0000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "bus", "spi0", "spi1", "spi2", - "spi3", "spi4", "uart0", "uart1", "uart2"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_PERI_BUS>, <&cmu_mif CLK_GOUT_MIF_CMU_PERI_SPI0>, @@ -162,6 +160,8 @@ cmu_peri: clock-controller@101f0000 { <&cmu_mif CLK_GOUT_MIF_CMU_PERI_UART0>, <&cmu_mif CLK_GOUT_MIF_CMU_PERI_UART1>, <&cmu_mif CLK_GOUT_MIF_CMU_PERI_UART2>; + clock-names = "oscclk", "bus", "spi0", "spi1", "spi2", + "spi3", "spi4", "uart0", "uart1", "uart2"; }; cmu_mif: clock-controller@10460000 { @@ -169,8 +169,8 @@ cmu_mif: clock-controller@10460000 { reg = <0x10460000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk"; clocks = <&oscclk>; + clock-names = "oscclk"; }; pmu_system_controller: system-controller@10480000 { @@ -206,11 +206,11 @@ hsi2c0: i2c@10510000 { reg = <0x10510000 0x2000>; interrupts = <GIC_SPI 371 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c0_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_mif CLK_GOUT_MIF_HSI2C_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -224,14 +224,14 @@ pinctrl_mif: pinctrl@10530000 { gpu: gpu@11400000 { compatible = "samsung,exynos7870-mali", "arm,mali-t830"; reg = <0x11400000 0x5000>; - interrupt-names = "job", "mmu", "gpu"; interrupts = <GIC_SPI 282 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 283 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 281 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "job", "mmu", "gpu"; - clock-names = "core", "bus"; clocks = <&cmu_g3d CLK_GOUT_G3D_CLK>, <&cmu_g3d CLK_GOUT_G3D_ASYNCS_D0_CLK>; + clock-names = "core", "bus"; status = "disabled"; }; @@ -241,9 +241,9 @@ cmu_g3d: clock-controller@11460000 { reg = <0x11460000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "switch"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_G3D_SWITCH>; + clock-names = "oscclk", "switch"; }; cmu_mfcmscl: clock-controller@12cb0000 { @@ -251,10 +251,10 @@ cmu_mfcmscl: clock-controller@12cb0000 { reg = <0x12cb0000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "mfc", "mscl"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_MFCMSCL_MFC>, <&cmu_mif CLK_GOUT_MIF_CMU_MFCMSCL_MSCL>; + clock-names = "oscclk", "mfc", "mscl"; }; mmc0: mmc@13540000 { @@ -262,9 +262,9 @@ mmc0: mmc@13540000 { reg = <0x13540000 0x2000>; interrupts = <GIC_SPI 245 IRQ_TYPE_LEVEL_HIGH>; - clock-names = "biu", "ciu"; clocks = <&cmu_fsys CLK_GOUT_FSYS_MMC0_ACLK>, <&cmu_mif CLK_GOUT_MIF_CMU_FSYS_MMC0>; + clock-names = "biu", "ciu"; status = "disabled"; }; @@ -274,9 +274,9 @@ mmc1: mmc@13550000 { reg = <0x13550000 0x2000>; interrupts = <GIC_SPI 246 IRQ_TYPE_LEVEL_HIGH>; - clock-names = "biu", "ciu"; clocks = <&cmu_fsys CLK_GOUT_FSYS_MMC1_ACLK>, <&cmu_mif CLK_GOUT_MIF_CMU_FSYS_MMC1>; + clock-names = "biu", "ciu"; status = "disabled"; }; @@ -286,9 +286,9 @@ mmc2: mmc@13560000 { reg = <0x13560000 0x2000>; interrupts = <GIC_SPI 247 IRQ_TYPE_LEVEL_HIGH>; - clock-names = "biu", "ciu"; clocks = <&cmu_fsys CLK_GOUT_FSYS_MMC2_ACLK>, <&cmu_mif CLK_GOUT_MIF_CMU_FSYS_MMC2>; + clock-names = "biu", "ciu"; status = "disabled"; }; @@ -298,9 +298,9 @@ usbdrd_phy: phy@135c0000 { reg = <0x135c0000 0x100>; #phy-cells = <1>; - clock-names = "phy", "ref"; clocks = <&cmu_fsys CLK_GOUT_FSYS_MUX_USB20DRD_PHYCLOCK_USER>, <&cmu_fsys CLK_GOUT_FSYS_MUX_USB_PLL>; + clock-names = "phy", "ref"; samsung,pmu-syscon = <&pmu_system_controller>; }; @@ -311,10 +311,10 @@ usbdrd: usb@13600000 { #address-cells = <1>; #size-cells = <1>; - clock-names = "bus_early", "ref", "ctrl"; clocks = <&cmu_fsys CLK_GOUT_FSYS_USB20DRD_ACLK_HSDRD>, <&cmu_fsys CLK_GOUT_FSYS_USB20DRD_HSDRD_REF_CLK>, <&cmu_fsys CLK_GOUT_FSYS_USB20DRD_HCLK_USB20_CTRL>; + clock-names = "bus_early", "ref", "ctrl"; status = "disabled"; @@ -323,8 +323,8 @@ usb@0 { reg = <0x0 0x10000>; interrupts = <GIC_SPI 230 IRQ_TYPE_LEVEL_HIGH>; - phy-names = "usb2-phy"; phys = <&usbdrd_phy 0>; + phy-names = "usb2-phy"; usb-role-switch; snps,usb2-gadget-lpm-disable; @@ -336,10 +336,10 @@ cmu_fsys: clock-controller@13730000 { reg = <0x13730000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "bus", "usb20drd"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_FSYS_BUS>, <&cmu_mif CLK_GOUT_MIF_CMU_FSYS_USB20DRD_REFCLK>; + clock-names = "oscclk", "bus", "usb20drd"; }; pinctrl_fsys: pinctrl@13750000 { @@ -354,12 +354,12 @@ serial0: serial@13800000 { reg = <0x13800000 0x100>; interrupts = <GIC_SPI 421 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&uart0_bus>; + pinctrl-names = "default"; - clock-names = "uart", "clk_uart_baud0"; clocks = <&cmu_peri CLK_GOUT_PERI_UART0_PCLK>, <&cmu_peri CLK_GOUT_PERI_UART0_EXT_UCLK>; + clock-names = "uart", "clk_uart_baud0"; samsung,uart-fifosize = <16>; @@ -372,12 +372,12 @@ serial1: serial@13810000 { reg = <0x13810000 0x100>; interrupts = <GIC_SPI 422 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&uart1_bus>; + pinctrl-names = "default"; - clock-names = "uart", "clk_uart_baud0"; clocks = <&cmu_peri CLK_GOUT_PERI_UART1_PCLK>, <&cmu_peri CLK_GOUT_PERI_UART1_EXT_UCLK>; + clock-names = "uart", "clk_uart_baud0"; samsung,uart-fifosize = <256>; @@ -390,12 +390,12 @@ serial2: serial@13820000 { reg = <0x13820000 0x100>; interrupts = <GIC_SPI 423 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&uart2_bus>; + pinctrl-names = "default"; - clock-names = "uart", "clk_uart_baud0"; clocks = <&cmu_peri CLK_GOUT_PERI_UART2_PCLK>, <&cmu_peri CLK_GOUT_PERI_UART2_EXT_UCLK>; + clock-names = "uart", "clk_uart_baud0"; samsung,uart-fifosize = <256>; @@ -408,11 +408,11 @@ i2c0: i2c@13830000 { reg = <0x13830000 0x100>; interrupts = <GIC_SPI 424 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c0_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C0_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -423,11 +423,11 @@ i2c1: i2c@13840000 { reg = <0x13840000 0x100>; interrupts = <GIC_SPI 425 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c1_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C1_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -438,11 +438,11 @@ i2c2: i2c@13850000 { reg = <0x13850000 0x100>; interrupts = <GIC_SPI 426 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c2_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C2_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -453,11 +453,11 @@ i2c3: i2c@13860000 { reg = <0x13860000 0x100>; interrupts = <GIC_SPI 427 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c3_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C3_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -468,11 +468,11 @@ i2c4: i2c@13870000 { reg = <0x13870000 0x100>; interrupts = <GIC_SPI 428 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c4_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C4_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -483,11 +483,11 @@ i2c5: i2c@13880000 { reg = <0x13880000 0x100>; interrupts = <GIC_SPI 429 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c5_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C5_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -498,11 +498,11 @@ i2c6: i2c@13890000 { reg = <0x13890000 0x100>; interrupts = <GIC_SPI 430 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c6_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C6_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -513,11 +513,11 @@ hsi2c1: i2c@138a0000 { reg = <0x138a0000 0x1000>; interrupts = <GIC_SPI 449 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c1_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C1_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -528,11 +528,11 @@ hsi2c2: i2c@138b0000 { reg = <0x138b0000 0x1000>; interrupts = <GIC_SPI 450 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c2_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C2_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -543,11 +543,11 @@ hsi2c3: i2c@138c0000 { reg = <0x138c0000 0x1000>; interrupts = <GIC_SPI 451 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c3_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C3_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -558,11 +558,11 @@ i2c7: i2c@138d0000 { reg = <0x138d0000 0x100>; interrupts = <GIC_SPI 453 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c7_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C7_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -573,11 +573,11 @@ i2c8: i2c@138e0000 { reg = <0x138e0000 0x100>; interrupts = <GIC_SPI 454 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&i2c8_bus>; + pinctrl-names = "default"; - clock-names = "i2c"; clocks = <&cmu_peri CLK_GOUT_PERI_I2C8_PCLK>; + clock-names = "i2c"; status = "disabled"; }; @@ -588,11 +588,11 @@ hsi2c4: i2c@138f0000 { reg = <0x138f0000 0x1000>; interrupts = <GIC_SPI 456 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c4_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C4_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -603,11 +603,11 @@ hsi2c5: i2c@13950000 { reg = <0x13950000 0x1000>; interrupts = <GIC_SPI 457 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c5_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C5_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -618,11 +618,11 @@ hsi2c6: i2c@13960000 { reg = <0x13960000 0x1000>; interrupts = <GIC_SPI 458 IRQ_TYPE_LEVEL_HIGH>; - pinctrl-names = "default"; pinctrl-0 = <&hsi2c6_bus>; + pinctrl-names = "default"; - clock-names = "hsi2c"; clocks = <&cmu_peri CLK_GOUT_PERI_HSI2C6_IPCLK>; + clock-names = "hsi2c"; status = "disabled"; }; @@ -668,11 +668,11 @@ cmu_isp: clock-controller@144d0000 { reg = <0x144d0000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "cam", "isp", "vra"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_ISP_CAM>, <&cmu_mif CLK_GOUT_MIF_CMU_ISP_ISP>, <&cmu_mif CLK_GOUT_MIF_CMU_ISP_VRA>; + clock-names = "oscclk", "cam", "isp", "vra"; }; pinctrl_dispaud: pinctrl@148c0000 { @@ -686,11 +686,11 @@ cmu_dispaud: clock-controller@148d0000 { reg = <0x148d0000 0x1000>; #clock-cells = <1>; - clock-names = "oscclk", "bus", "decon_eclk", "decon_vclk"; clocks = <&oscclk>, <&cmu_mif CLK_GOUT_MIF_CMU_DISPAUD_BUS>, <&cmu_mif CLK_GOUT_MIF_CMU_DISPAUD_DECON_ECLK>, <&cmu_mif CLK_GOUT_MIF_CMU_DISPAUD_DECON_VCLK>; + clock-names = "oscclk", "bus", "decon_eclk", "decon_vclk"; }; }; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} 2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty @ 2025-09-28 21:56 ` Krzysztof Kozlowski 2025-09-29 10:01 ` Kaustabh Chakraborty 0 siblings, 1 reply; 15+ messages in thread From: Krzysztof Kozlowski @ 2025-09-28 21:56 UTC (permalink / raw) To: Kaustabh Chakraborty Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On Mon, 29 Sept 2025 at 01:44, Kaustabh Chakraborty <kauschluss@disroot.org> wrote: > > All ${x}-names properties are conventionally placed after their > corresponding ${x} properties. For instance, 'clock-names' must follow > 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary > changes to follow said convention. No functional changes made. > I don't intend to take such cosmetic changes, because they interfere with stable back porting, unless we have a tool for such cleanup. Did you use my prototype tool for that or some other tool? Best regards, Krzysztof ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} 2025-09-28 21:56 ` Krzysztof Kozlowski @ 2025-09-29 10:01 ` Kaustabh Chakraborty 2025-10-07 1:22 ` Krzysztof Kozlowski 0 siblings, 1 reply; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-29 10:01 UTC (permalink / raw) To: Krzysztof Kozlowski Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On 2025-09-28 21:56, Krzysztof Kozlowski wrote: > On Mon, 29 Sept 2025 at 01:44, Kaustabh Chakraborty > <kauschluss@disroot.org> wrote: >> >> All ${x}-names properties are conventionally placed after their >> corresponding ${x} properties. For instance, 'clock-names' must follow >> 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary >> changes to follow said convention. No functional changes made. >> > > I don't intend to take such cosmetic changes, because they interfere > with stable back porting, unless we have a tool for such cleanup. Did > you use my prototype tool for that or some other tool? No, I did it manually. This is due to your first remark in [1] and my corresponding reply in [2]. What do I do here then? [1] https://lore.kernel.org/all/6f0451ee-ddb8-4ded-8f0a-b491de9cc308@kernel.org/ [2] https://lore.kernel.org/all/00240935c664edaec3092354a303a91f@disroot.org/ > > Best regards, > Krzysztof ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} 2025-09-29 10:01 ` Kaustabh Chakraborty @ 2025-10-07 1:22 ` Krzysztof Kozlowski 2025-10-13 8:24 ` Kaustabh Chakraborty 0 siblings, 1 reply; 15+ messages in thread From: Krzysztof Kozlowski @ 2025-10-07 1:22 UTC (permalink / raw) To: Kaustabh Chakraborty Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On 29/09/2025 19:01, Kaustabh Chakraborty wrote: > On 2025-09-28 21:56, Krzysztof Kozlowski wrote: >> On Mon, 29 Sept 2025 at 01:44, Kaustabh Chakraborty >> <kauschluss@disroot.org> wrote: >>> >>> All ${x}-names properties are conventionally placed after their >>> corresponding ${x} properties. For instance, 'clock-names' must follow >>> 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary >>> changes to follow said convention. No functional changes made. >>> >> >> I don't intend to take such cosmetic changes, because they interfere >> with stable back porting, unless we have a tool for such cleanup. Did >> you use my prototype tool for that or some other tool? > > No, I did it manually. This is due to your first remark in [1] and > my corresponding reply in [2]. What do I do here then? I asked for the new code to follow this style, but I don't want to fix yet existing code - before we come with a tool doing it. Best regards, Krzysztof ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} 2025-10-07 1:22 ` Krzysztof Kozlowski @ 2025-10-13 8:24 ` Kaustabh Chakraborty 0 siblings, 0 replies; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-10-13 8:24 UTC (permalink / raw) To: Krzysztof Kozlowski Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On 2025-10-07 01:22, Krzysztof Kozlowski wrote: > On 29/09/2025 19:01, Kaustabh Chakraborty wrote: >> On 2025-09-28 21:56, Krzysztof Kozlowski wrote: >>> On Mon, 29 Sept 2025 at 01:44, Kaustabh Chakraborty >>> <kauschluss@disroot.org> wrote: >>>> >>>> All ${x}-names properties are conventionally placed after their >>>> corresponding ${x} properties. For instance, 'clock-names' must >>>> follow >>>> 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary >>>> changes to follow said convention. No functional changes made. >>>> >>> >>> I don't intend to take such cosmetic changes, because they interfere >>> with stable back porting, unless we have a tool for such cleanup. Did >>> you use my prototype tool for that or some other tool? >> >> No, I did it manually. This is due to your first remark in [1] and >> my corresponding reply in [2]. What do I do here then? > > > I asked for the new code to follow this style, but I don't want to fix > yet existing code - before we come with a tool doing it. Well it would stay inconsistent until then – fine, I'll drop these. > > > Best regards, > Krzysztof ^ permalink raw reply [flat|nested] 15+ messages in thread
* [PATCH 2/7] arm64: dts: exynos7870-a2corelte: relocate ${x}-names property after ${x} 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 3/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty ` (4 subsequent siblings) 6 siblings, 0 replies; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty All ${x}-names properties are conventionally placed after their corresponding ${x} properties. For instance, 'clock-names' must follow 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary changes to follow said convention. No functional changes made. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts index eb7b48593187409ce6653b7d857b63f6946aa4f7..f8a7610abeb77cab9f38aaf48d441d99ec61ab5f 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts @@ -47,8 +47,8 @@ gpio-keys { compatible = "gpio-keys"; label = "GPIO Keys"; - pinctrl-names = "default"; pinctrl-0 = <&key_power &key_voldown &key_volup>; + pinctrl-names = "default"; key-power { label = "Power Key"; @@ -140,8 +140,8 @@ pmic@66 { interrupt-parent = <&gpa0>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; - pinctrl-names = "default"; pinctrl-0 = <&pmic_irq>; + pinctrl-names = "default"; regulators { vdd_buck1: buck1 { @@ -379,8 +379,8 @@ accelerometer@1d { interrupt-parent = <&gpa2>; interrupts = <3 IRQ_TYPE_EDGE_RISING>; - pinctrl-names = "default"; pinctrl-0 = <&accel_irq>; + pinctrl-names = "default"; st,drdy-int-pin = <1>; }; @@ -391,8 +391,8 @@ proximity@48 { interrupt-parent = <&gpa0>; interrupts = <5 IRQ_TYPE_EDGE_BOTH>; - pinctrl-names = "default"; pinctrl-0 = <&proxm_irq>; + pinctrl-names = "default"; proximity-near-level = <25>; }; @@ -415,8 +415,8 @@ touchscreen@4b { #address-cells = <1>; #size-cells = <0>; - pinctrl-names = "default"; pinctrl-0 = <&touch_irq>; + pinctrl-names = "default"; vdd-supply = <&vdd_ldo35>; @@ -441,8 +441,8 @@ rmi4-f12@12 { }; &mmc0 { - pinctrl-names = "default"; pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_rdqs &sd0_bus1 &sd0_bus4 &sd0_bus8>; + pinctrl-names = "default"; vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; @@ -460,8 +460,8 @@ &mmc1 { #address-cells = <1>; #size-cells = <0>; - pinctrl-names = "default"; pinctrl-0 = <&sd1_clk &sd1_cmd &sd1_bus1 &sd1_bus4>; + pinctrl-names = "default"; mmc-pwrseq = <&pwrseq_mmc1>; @@ -479,17 +479,17 @@ &mmc1 { wifi@1 { compatible = "brcm,bcm43430a1-fmac", "brcm,bcm4329-fmac"; reg = <0x1>; - interrupt-names = "host-wake"; interrupt-parent = <&gpa2>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; + interrupt-names = "host-wake"; reset-gpios = <&gpd3 6 GPIO_ACTIVE_LOW>; }; }; &mmc2 { - pinctrl-names = "default"; pinctrl-0 = <&sd2_clk &sd2_cmd &sd2_bus1 &sd2_bus4 &dwmmc2_irq>; + pinctrl-names = "default"; vmmc-supply = <&vdd_fixed_mmc2>; vqmmc-supply = <&vdd_ldo2>; @@ -608,8 +608,8 @@ &serial1 { bluetooth { compatible = "brcm,bcm43430a1-bt"; - pinctrl-names = "default"; pinctrl-0 = <&bt_btwake &bt_hostwake &bt_enable>; + pinctrl-names = "default"; device-wakeup-gpios = <&gpa1 2 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpa1 6 GPIO_ACTIVE_HIGH>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* [PATCH 3/7] arm64: dts: exynos7870-j6lte: relocate ${x}-names property after ${x} 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 2/7] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 4/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty ` (3 subsequent siblings) 6 siblings, 0 replies; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty All ${x}-names properties are conventionally placed after their corresponding ${x} properties. For instance, 'clock-names' must follow 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary changes to follow said convention. No functional changes made. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts index b8ce433b93b1b488da31bbe4846f8092243611ad..b2990b5466c949c18a61d1b1c4427986b19804ba 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts @@ -47,8 +47,8 @@ gpio-hall-effect-sensor { compatible = "gpio-keys"; label = "GPIO Hall Effect Sensor"; - pinctrl-names = "default"; pinctrl-0 = <&hall_irq>; + pinctrl-names = "default"; event-hall-effect-sensor { label = "Hall Effect Sensor"; @@ -64,8 +64,8 @@ gpio-keys { compatible = "gpio-keys"; label = "GPIO Keys"; - pinctrl-names = "default"; pinctrl-0 = <&key_power &key_voldown &key_volup>; + pinctrl-names = "default"; key-power { label = "Power Key"; @@ -149,8 +149,8 @@ pmic@66 { interrupt-parent = <&gpa0>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; - pinctrl-names = "default"; pinctrl-0 = <&pmic_irq>; + pinctrl-names = "default"; regulators { vdd_buck1: buck1 { @@ -387,8 +387,8 @@ accelerometer@1d { interrupt-parent = <&gpa2>; interrupts = <3 IRQ_TYPE_EDGE_RISING>; - pinctrl-names = "default"; pinctrl-0 = <&accel_irq>; + pinctrl-names = "default"; mount-matrix = "-1", "0", "0", "0", "1", "0", @@ -413,8 +413,8 @@ touchscreen@20 { interrupt-parent = <&gpa0>; interrupts = <6 IRQ_TYPE_LEVEL_LOW>; - pinctrl-names = "default"; pinctrl-0 = <&touch_irq>; + pinctrl-names = "default"; touchscreen-size-x = <720>; touchscreen-size-y = <1480>; @@ -424,8 +424,8 @@ touchscreen@20 { }; &mmc0 { - pinctrl-names = "default"; pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_rdqs &sd0_bus1 &sd0_bus4 &sd0_bus8>; + pinctrl-names = "default"; vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; @@ -443,8 +443,8 @@ &mmc1 { #address-cells = <1>; #size-cells = <0>; - pinctrl-names = "default"; pinctrl-0 = <&sd1_clk &sd1_cmd &sd1_bus1 &sd1_bus4>; + pinctrl-names = "default"; mmc-pwrseq = <&pwrseq_mmc1>; @@ -462,17 +462,17 @@ &mmc1 { wifi@1 { compatible = "brcm,bcm43430a1-fmac", "brcm,bcm4329-fmac"; reg = <0x1>; - interrupt-names = "host-wake"; interrupt-parent = <&gpa2>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; + interrupt-names = "host-wake"; reset-gpios = <&gpd3 6 GPIO_ACTIVE_LOW>; }; }; &mmc2 { - pinctrl-names = "default"; pinctrl-0 = <&sd2_clk &sd2_cmd &sd2_bus1 &sd2_bus4 &dwmmc2_irq>; + pinctrl-names = "default"; vmmc-supply = <&vdd_fixed_mmc2>; vqmmc-supply = <&vdd_ldo2>; @@ -591,8 +591,8 @@ &serial1 { bluetooth { compatible = "brcm,bcm43430a1-bt"; - pinctrl-names = "default"; pinctrl-0 = <&bt_btwake &bt_hostwake &bt_enable>; + pinctrl-names = "default"; device-wakeup-gpios = <&gpa1 2 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpa1 6 GPIO_ACTIVE_HIGH>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* [PATCH 4/7] arm64: dts: exynos7870-on7xelte: relocate ${x}-names property after ${x} 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty ` (2 preceding siblings ...) 2025-09-28 16:43 ` [PATCH 3/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty ` (2 subsequent siblings) 6 siblings, 0 replies; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty All ${x}-names properties are conventionally placed after their corresponding ${x} properties. For instance, 'clock-names' must follow 'clocks', 'interrupt-names' must follow 'interrupts'. Make necessary changes to follow said convention. No functional changes made. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts b/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts index b1d9eff5a82702cd7c9797b2124486207e03ad89..66413a9506276cca8925e644c0e857fb5c48112d 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts @@ -47,8 +47,8 @@ gpio-keys { compatible = "gpio-keys"; label = "GPIO Keys"; - pinctrl-names = "default"; pinctrl-0 = <&key_home &key_power &key_voldown &key_volup>; + pinctrl-names = "default"; key-home { label = "Home Key"; @@ -139,8 +139,8 @@ pmic@66 { interrupt-parent = <&gpa0>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; - pinctrl-names = "default"; pinctrl-0 = <&pmic_irq>; + pinctrl-names = "default"; regulators { vdd_buck1: buck1 { @@ -385,8 +385,8 @@ touchscreen@70 { #address-cells = <1>; #size-cells = <0>; - pinctrl-names = "default"; pinctrl-0 = <&touch_irq>; + pinctrl-names = "default"; syna,reset-delay-ms = <200>; syna,startup-delay-ms = <200>; @@ -423,8 +423,8 @@ accelerometer@1d { interrupt-parent = <&gpa2>; interrupts = <3 IRQ_TYPE_EDGE_RISING>; - pinctrl-names = "default"; pinctrl-0 = <&accel_irq>; + pinctrl-names = "default"; mount-matrix = "1", "0", "0", "0", "-1", "0", @@ -449,16 +449,16 @@ proximity@48 { interrupt-parent = <&gpa0>; interrupts = <5 IRQ_TYPE_EDGE_BOTH>; - pinctrl-names = "default"; pinctrl-0 = <&proxm_irq>; + pinctrl-names = "default"; proximity-near-level = <25>; }; }; &mmc0 { - pinctrl-names = "default"; pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_rdqs &sd0_bus1 &sd0_bus4 &sd0_bus8>; + pinctrl-names = "default"; vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; @@ -476,8 +476,8 @@ &mmc1 { #address-cells = <1>; #size-cells = <0>; - pinctrl-names = "default"; pinctrl-0 = <&sd1_clk &sd1_cmd &sd1_bus1 &sd1_bus4>; + pinctrl-names = "default"; mmc-pwrseq = <&pwrseq_mmc1>; @@ -495,17 +495,17 @@ &mmc1 { wifi@1 { compatible = "brcm,bcm43430a1-fmac", "brcm,bcm4329-fmac"; reg = <0x1>; - interrupt-names = "host-wake"; interrupt-parent = <&gpa2>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; + interrupt-names = "host-wake"; reset-gpios = <&gpd3 6 GPIO_ACTIVE_LOW>; }; }; &mmc2 { - pinctrl-names = "default"; pinctrl-0 = <&sd2_clk &sd2_cmd &sd2_bus1 &sd2_bus4 &dwmmc2_irq>; + pinctrl-names = "default"; vmmc-supply = <&vdd_fixed_mmc2>; vqmmc-supply = <&vdd_ldo2>; @@ -640,8 +640,8 @@ &serial1 { bluetooth { compatible = "brcm,bcm43430a1-bt"; - pinctrl-names = "default"; pinctrl-0 = <&bt_btwake &bt_hostwake &bt_enable>; + pinctrl-names = "default"; device-wakeup-gpios = <&gpa1 2 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpa1 6 GPIO_ACTIVE_HIGH>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty ` (3 preceding siblings ...) 2025-09-28 16:43 ` [PATCH 4/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski 2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty 2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty 6 siblings, 1 reply; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty Add the bus-width property in &mmc0 node. The Exynos DWMMC driver assumes bus width to be 8 if not present in devicetree, so at least with respect to the Linux kernel, this doesn't introduce any functional changes. But other drivers referring to it may not. Either way, without the bus-width property the hardware description remains incomplete. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts index f8a7610abeb77cab9f38aaf48d441d99ec61ab5f..1193f0f7dcc171762fefccee23c2c294a41c46c9 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts @@ -447,6 +447,7 @@ &mmc0 { vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; + bus-width = <8>; fifo-depth = <64>; samsung,dw-mshc-ciu-div = <3>; samsung,dw-mshc-sdr-timing = <0 4>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: (subset) [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node 2025-09-28 16:43 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty @ 2025-10-13 0:25 ` Krzysztof Kozlowski 0 siblings, 0 replies; 15+ messages in thread From: Krzysztof Kozlowski @ 2025-10-13 0:25 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, Kaustabh Chakraborty Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On Sun, 28 Sep 2025 22:13:56 +0530, Kaustabh Chakraborty wrote: > Add the bus-width property in &mmc0 node. The Exynos DWMMC driver > assumes bus width to be 8 if not present in devicetree, so at least with > respect to the Linux kernel, this doesn't introduce any functional > changes. But other drivers referring to it may not. Either way, without > the bus-width property the hardware description remains incomplete. > > > [...] Applied, thanks! [5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node https://git.kernel.org/krzk/linux/c/5b33bce0bd31ca3ebc5e3a75b3053141540ec644 Best regards, -- Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> ^ permalink raw reply [flat|nested] 15+ messages in thread
* [PATCH 6/7] arm64: dts: exynos7870-j6lte: add bus-width to mmc0 node 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty ` (4 preceding siblings ...) 2025-09-28 16:43 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski 2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty 6 siblings, 1 reply; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty Add the bus-width property in &mmc0 node. The Exynos DWMMC driver assumes bus width to be 8 if not present in devicetree, so at least with respect to the Linux kernel, this doesn't introduce any functional changes. But other drivers referring to it may not. Either way, without the bus-width property the hardware description remains incomplete. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts index b2990b5466c949c18a61d1b1c4427986b19804ba..4aa80ea3a1cc94e69d88a5e5a135eb7ac5510fdf 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts @@ -430,6 +430,7 @@ &mmc0 { vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; + bus-width = <8>; fifo-depth = <64>; samsung,dw-mshc-ciu-div = <3>; samsung,dw-mshc-sdr-timing = <0 4>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: (subset) [PATCH 6/7] arm64: dts: exynos7870-j6lte: add bus-width to mmc0 node 2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty @ 2025-10-13 0:25 ` Krzysztof Kozlowski 0 siblings, 0 replies; 15+ messages in thread From: Krzysztof Kozlowski @ 2025-10-13 0:25 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, Kaustabh Chakraborty Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On Sun, 28 Sep 2025 22:13:57 +0530, Kaustabh Chakraborty wrote: > Add the bus-width property in &mmc0 node. The Exynos DWMMC driver > assumes bus width to be 8 if not present in devicetree, so at least with > respect to the Linux kernel, this doesn't introduce any functional > changes. But other drivers referring to it may not. Either way, without > the bus-width property the hardware description remains incomplete. > > > [...] Applied, thanks! [6/7] arm64: dts: exynos7870-j6lte: add bus-width to mmc0 node https://git.kernel.org/krzk/linux/c/9e3e37939362ba110c341cae09acaf000c0edb34 Best regards, -- Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> ^ permalink raw reply [flat|nested] 15+ messages in thread
* [PATCH 7/7] arm64: dts: exynos7870-on7xelte: add bus-width to mmc0 node 2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty ` (5 preceding siblings ...) 2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty @ 2025-09-28 16:43 ` Kaustabh Chakraborty 2025-10-13 0:26 ` (subset) " Krzysztof Kozlowski 6 siblings, 1 reply; 15+ messages in thread From: Kaustabh Chakraborty @ 2025-09-28 16:43 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel, Kaustabh Chakraborty Add the bus-width property in &mmc0 node. The Exynos DWMMC driver assumes bus width to be 8 if not present in devicetree, so at least with respect to the Linux kernel, this doesn't introduce any functional changes. But other drivers referring to it may not. Either way, without the bus-width property the hardware description remains incomplete. Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org> --- arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts b/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts index 66413a9506276cca8925e644c0e857fb5c48112d..87549e9560643cd0692ce4a9b2c5cdff80b21173 100644 --- a/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts +++ b/arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts @@ -463,6 +463,7 @@ &mmc0 { vmmc-supply = <&vdd_ldo26>; vqmmc-supply = <&vdd_ldo27>; + bus-width = <8>; fifo-depth = <64>; samsung,dw-mshc-ciu-div = <3>; samsung,dw-mshc-sdr-timing = <0 4>; -- 2.51.0 ^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: (subset) [PATCH 7/7] arm64: dts: exynos7870-on7xelte: add bus-width to mmc0 node 2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty @ 2025-10-13 0:26 ` Krzysztof Kozlowski 0 siblings, 0 replies; 15+ messages in thread From: Krzysztof Kozlowski @ 2025-10-13 0:26 UTC (permalink / raw) To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Alim Akhtar, Kaustabh Chakraborty Cc: devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel On Sun, 28 Sep 2025 22:13:58 +0530, Kaustabh Chakraborty wrote: > Add the bus-width property in &mmc0 node. The Exynos DWMMC driver > assumes bus width to be 8 if not present in devicetree, so at least with > respect to the Linux kernel, this doesn't introduce any functional > changes. But other drivers referring to it may not. Either way, without > the bus-width property the hardware description remains incomplete. > > > [...] Applied, thanks! [7/7] arm64: dts: exynos7870-on7xelte: add bus-width to mmc0 node https://git.kernel.org/krzk/linux/c/2bb07378bae9504f5122bfbe4a6082bcdcc8bdf6 Best regards, -- Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2025-10-13 8:24 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty
2025-09-28 21:56 ` Krzysztof Kozlowski
2025-09-29 10:01 ` Kaustabh Chakraborty
2025-10-07 1:22 ` Krzysztof Kozlowski
2025-10-13 8:24 ` Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 2/7] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 3/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 4/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty
2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-10-13 0:25 ` (subset) " Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-10-13 0:26 ` (subset) " Krzysztof Kozlowski
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).