socfpga: Enable SD/MMC support
Subsystems (7)
v4 cover socfpga: Enable SD/MMC support
From: Dinh Nguyen <[email protected]>
Hi,
This is v4 of the patch series to enable SD/MMC on the SOCFPGA platform.
V4 differences from V3:
* Re-use the SOCFPGA clock driver for controlling the SDR settings of the CIU clock. By using the .prepare member of the common clk_ops structure, the settings of the SD/MMC CIU can be done through the common clock API in the SD/MMC driver.
* Re-use exising binding that is on the Rockchip. The "rockchip,rk2928-dw-mshc" binding that will also work for SOCFPGA.
* Remove dw_mmm-socfpga.c that is platform specific to SOCFPGA as the only require platform specific code is already done with "rockchip,rk2928-dw-mshc".
* Add error checking for getting "samsung,dw-mshc-sdr-timing".
* Add support for SD/MMC to socfpga_defconfig.
* Add SD/MMC dts entries for socfpga_arria5.
Thanks,
Dinh Nguyen (4):
arm: dts: Add support for SD/MMC on SOCFPGA
clk: socfpga: Add a hook for SD/MMC driver to control CIU clock
settings
mmc: dw_mmc-socfpga: Remove the SOCFPGA specific platform for dw_mmc
ARM: socfpga_defconfig: enable SD/MMC support
arch/arm/boot/dts/socfpga.dtsi | 11 +++ arch/arm/boot/dts/socfpga_arria5.dtsi | 12 +++ arch/arm/boot/dts/socfpga_cyclone5.dtsi | 12 +++ arch/arm/boot/dts/socfpga_vt.dts | 12 +++ arch/arm/configs/socfpga_defconfig | 2 + drivers/clk/socfpga/clk.c | 22 +++++ drivers/mmc/host/Kconfig | 8 -- drivers/mmc/host/dw_mmc-socfpga.c | 138 ------------------------------- 8 files changed, 71 insertions(+), 146 deletions(-) delete mode 100644 drivers/mmc/host/dw_mmc-socfpga.c
Signature · 1 line
1.7.9.5
PATCH v4 1/4 arm: dts: Add support for SD/MMC on SOCFPGA
From: Dinh Nguyen <[email protected]>
Re-use the "rockchip,rk2928-dw-mshc" binding that will support SD/MMC on Altera's SOCFPGA platform.
---
v3: Re-use "rockchip,rk2928-dw-mshc" binding
v3: none
v2: none
--- arch/arm/boot/dts/socfpga.dtsi | 11 +++++++++++ arch/arm/boot/dts/socfpga_arria5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_cyclone5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_vt.dts | 12 ++++++++++++ 4 files changed, 47 insertions(+)
arch/arm/boot/dts/socfpga.dtsi +11 -0
@@ -469,6 +469,17 @@ cache-level = <2>; }; + mmc: dwmmc0 at ff704000 { + compatible = "rockchip,rk2928-dw-mshc"; + reg = <0xff704000 0x1000>; + interrupts = <0 139 4>; + fifo-depth = <0x400>; + #address-cells = <1>; + #size-cells = <0>; + clocks = <&l4_mp_clk>, <&sdmmc_clk>; + clock-names = "biu", "ciu"; + }; + /* Local timer */ timer at fffec600 { compatible = "arm,cortex-a9-twd-timer";
arch/arm/boot/dts/socfpga_arria5.dtsi +12 -0
@@ -27,6 +27,18 @@ }; }; + dwmmc0 at ff704000 { + num-slots = <1>; + supports-highspeed; + broken-cd; + samsung,dw-mshc-sdr-timing = <3 0>; + + slot at 0 { + reg = <0>; + bus-width = <4>; + }; + }; + serial0 at ffc02000 { clock-frequency = <100000000>; };
arch/arm/boot/dts/socfpga_cyclone5.dtsi +12 -0
@@ -28,6 +28,18 @@ }; }; + dwmmc0 at ff704000 { + num-slots = <1>; + supports-highspeed; + broken-cd; + samsung,dw-mshc-sdr-timing = <3 0>; + + slot at 0 { + reg = <0>; + bus-width = <4>; + }; + }; + ethernet at ff702000 { phy-mode = "rgmii"; phy-addr = <0xffffffff>; /* probe for phy addr */
arch/arm/boot/dts/socfpga_vt.dts +12 -0
@@ -41,6 +41,18 @@ }; }; + dwmmc0 at ff704000 { + num-slots = <1>; + supports-highspeed; + broken-cd; + samsung,dw-mshc-sdr-timing = <3 0>; + + slot at 0 { + reg = <0>; + bus-width = <4>; + }; + }; + ethernet at ff700000 { phy-mode = "gmii"; status = "okay";
Signature · 1 line
1.7.9.5
PATCH v4 1/4 arm: dts: Add support for SD/MMC on SOCFPGA
Quoted 25 lines · dinguyen at altera.com
From: Dinh Nguyen <[email protected]>
Re-use the "rockchip,rk2928-dw-mshc" binding that will support SD/MMC on Altera's SOCFPGA platform.
Signed-off-by Dinh Nguyen <[email protected]>---
v3: Re-use "rockchip,rk2928-dw-mshc" binding
v3: none
v2: none--- arch/arm/boot/dts/socfpga.dtsi | 11 +++++++++++ arch/arm/boot/dts/socfpga_arria5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_cyclone5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_vt.dts | 12 ++++++++++++ 4 files changed, 47 insertions(+)arch/arm/boot/dts/socfpga.dtsi +0
-0@@ -469,6 +469,17 @@ cache-level = <2>; };
arch/arm/boot/dts/socfpga.dtsi line 481
Quoted 10 lines
arch/arm/boot/dts/socfpga.dtsi +10
-0+ mmc: dwmmc0 at ff704000 { + compatible = "rockchip,rk2928-dw-mshc"; + reg = <0xff704000 0x1000>; + interrupts = <0 139 4>; + fifo-depth = <0x400>; + #address-cells = <1>; + #size-cells = <0>; + clocks = <&l4_mp_clk>, <&sdmmc_clk>; + clock-names = "biu", "ciu"; + };
I think it's great that you can reuse the existing driver, but I'd recommend using a generic compatible string here in addition to one that identifies your specific implementation. You can list "rockchip,rk2928-dw-mshc" as well, but that is probably not necessary.
What I'd expect to see here is either
compatible = "altr,socfpga-dw-mshc", "rockchip,rk2928-dw-mshc", "snps,dw-mshc";
or
compatible = "altr,socfpga-dw-mshc", "rockchip,rk2928-dw-mshc", "snps,dw-mshc";
It's probably not too late to generalize the SDMMC_CMD_USE_HOLD_REG handling, which is currently the only difference between the generic "snps,dw-mshc" and the newer "rockchip,rk2928-dw-mshc" variant.
It's quite likely that all implementations should actually set SDMMC_CMD_USE_HOLD_REG (if both rockchips and altera set it) and you don't need to have any distinction in the dw_mmc-pltfm.c driver at all.
If it's actually needed on some but not others, you could add a binary DT property to tell the driver about it rather than keying it off of the compatible string. If it's needed only on older (or only on newer) versions of the dw-mshc design, it could be encoded as a version in the string, such as "snps,dw-mshc-1.234".
Arnd
PATCH v4 1/4 arm: dts: Add support for SD/MMC on SOCFPGA
Quoted 47 lines · Arnd Bergmann
Quoted 25 lines · dinguyen at altera.com
From: Dinh Nguyen <[email protected]>
Re-use the "rockchip,rk2928-dw-mshc" binding that will support SD/MMC on Altera's SOCFPGA platform.
Signed-off-by Dinh Nguyen <[email protected]>---
v3: Re-use "rockchip,rk2928-dw-mshc" binding
v3: none
v2: none--- arch/arm/boot/dts/socfpga.dtsi | 11 +++++++++++ arch/arm/boot/dts/socfpga_arria5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_cyclone5.dtsi | 12 ++++++++++++ arch/arm/boot/dts/socfpga_vt.dts | 12 ++++++++++++ 4 files changed, 47 insertions(+)arch/arm/boot/dts/socfpga.dtsi +0
-0@@ -469,6 +469,17 @@ cache-level = <2>; };arch/arm/boot/dts/socfpga.dtsi line 481
Quoted 10 lines
arch/arm/boot/dts/socfpga.dtsi +10
-0+ mmc: dwmmc0 at ff704000 { + compatible = "rockchip,rk2928-dw-mshc"; + reg = <0xff704000 0x1000>; + interrupts = <0 139 4>; + fifo-depth = <0x400>; + #address-cells = <1>; + #size-cells = <0>; + clocks = <&l4_mp_clk>, <&sdmmc_clk>; + clock-names = "biu", "ciu"; + };I think it's great that you can reuse the existing driver, but I'd recommend using a generic compatible string here in addition to one that identifies your specific implementation. You can list "rockchip,rk2928-dw-mshc" as well, but that is probably not necessary.
What I'd expect to see here is either
compatible = "altr,socfpga-dw-mshc", "rockchip,rk2928-dw-mshc", "snps,dw-mshc";
Quoted 8 lines
or
compatible = "altr,socfpga-dw-mshc", "rockchip,rk2928-dw-mshc", "snps,dw-mshc";It's probably not too late to generalize the
SDMMC_CMD_USE_HOLD_REGhandling, which is currently the only difference between the generic "snps,dw-mshc" and the newer "rockchip,rk2928-dw-mshc" variant.
Ok, I will try to generalize the driver.
Quoted 10 lines
It's quite likely that all implementations should actually set
SDMMC_CMD_USE_HOLD_REG(if both rockchips and altera set it) and you don't need to have any distinction in thedw_mmc-pltfm.cdriver at all.If it's actually needed on some but not others, you could add a binary DT property to tell the driver about it rather than keying it off of the compatible string. If it's needed only on older (or only on newer) versions of the dw-mshc design, it could be encoded as a version in the string, such as "snps,dw-mshc-1.234".
Perhaps Seungwon and Chris might have an opinion on this:
Quoted 1 line
From the Synopsys databook for this IP, using the
SDMMC_CMD_USE_HOLD_REG
is not recommended for SDR104, SDR50 and DDR50 speed modes. For other speeds, SDR12, and SDR25, it would be necessary to use SDMMC_CMD_USE_HOLD_REG.
I am referencing v2.50a of the Synopsys DesignWare Cores Mobile Storage Host Databook.
So I think a binary DT property should suffice?
Thanks,
Dinh
Quoted 3 lines
Arnd
PATCH v4 1/4 arm: dts: Add support for SD/MMC on SOCFPGA
Quoted 11 lines · Dinh Nguyen
Perhaps Seungwon and Chris might have an opinion on this:
From the Synopsys databook for this IP, using the
SDMMC_CMD_USE_HOLD_REGis not recommended for SDR104, SDR50 and DDR50 speed modes. For other speeds, SDR12, and SDR25, it would be necessary to useSDMMC_CMD_USE_HOLD_REG.I am referencing v2.50a of the Synopsys DesignWare Cores Mobile Storage Host Databook.
So I think a binary DT property should suffice?
Well, if it depends on the interface speed, it is something the driver should actually be able to figure out itself, since it knows the speed that is used.
That way, you don't even need a property or per-platform compatible string.
Arnd
PATCH v4 2/4 clk: socfpga: Add a hook for SD/MMC driver to control CIU clock settings
In reply to dinguyen at altera.comFrom: Dinh Nguyen <[email protected]>
Populate the .prepare function in the clk-ops for the "sdmmc_clk" that represents the "ciu" clock for the SD/MMC driver. The prepare function will handle setting the correct clock-phase for the CIU clock of the SD/MMC IP.
Re-use the "rockchip,rk2928-dw-mshc" binding as it is already defined and appropriate for the SOCFPGA platform as well.
--- drivers/clk/socfpga/clk.c | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+)
drivers/clk/socfpga/clk.c +25 -0
@@ -55,7 +55,13 @@#define div_mask (width) ((1 << (width)) - 1)#define streq (a, b) (strcmp((a), (b)) == 0) +#define SYSMGR_SDMMCGRP_CTRL_OFFSET 0x108 +/* SDMMC Group for System Manager defines */ +#define SYSMGR_SDMMC_CTRL_SET (smplsel, drvsel) \ + ((((smplsel) & 0x7) << 3) | (((drvsel) & 0x7) << 0)) +extern void __iomem *clk_mgr_base_addr; +extern void __iomem *sys_manager_base_addr;struct socfpga_clk {struct clk_gate hw;
@@ -68,6 +74,22 @@ struct socfpga_clk { };#define to_socfpga_clk (p) container_of(p, struct socfpga_clk, hw.hw) +static int sdmmc_ciuclk_prepare (struct clk_hw *hwclk) +{ +struct device_node *np; +u32 timing[2 ]; +u32 hs_timing; + + np =of_find_compatible_node (NULL ,NULL ,"rockchip,rk2928-dw-mshc" ); +if (of_property_read_u32_array (np,"samsung,dw-mshc-sdr-timing" , timing,2 )) { +pr_err ("SDMMC: cannot find samsung,dw-mshc-sdr-timing!\n" ); +return -ENODATA ; + } + hs_timing =SYSMGR_SDMMC_CTRL_SET (timing[1 ], timing[0 ]); +writel (hs_timing, sys_manager_base_addr +SYSMGR_SDMMCGRP_CTRL_OFFSET ); +return 0 ; +} +static unsigned long clk_pll_recalc_rate (struct clk_hw *hwclk,unsigned long parent_rate) {
@@ -274,6 +296,9 @@ static void __init socfpga_gate_clk_init(struct device_node *node, socfpga_clk->hw.reg = clk_mgr_base_addr + clk_gate[0 ]; socfpga_clk->hw.bit_idx = clk_gate[1 ]; +if (streq (clk_name,"sdmmc_clk" )) + gateclk_ops.prepare = sdmmc_ciuclk_prepare; + gateclk_ops.enable = clk_gate_ops.enable; gateclk_ops.disable = clk_gate_ops.disable; }
Signature · 1 line
1.7.9.5
PATCH v4 2/4 clk: socfpga: Add a hook for SD/MMC driver to control CIU clock settings
Quoted 10 lines · dinguyen at altera.com
From: Dinh Nguyen <[email protected]>
Populate the .prepare function in the clk-ops for the "
sdmmc_clk" that represents the "ciu" clock for the SD/MMC driver. The prepare function will handle setting the correct clock-phase for the CIU clock of the SD/MMC IP.Re-use the "rockchip,rk2928-dw-mshc" binding as it is already defined and appropriate for the SOCFPGA platform as well.
Signed-off-by Dinh Nguyen <[email protected]>
I think with this series we're getting closer to where things should be, but there are still a number of the same problems. Maybe I have misunderstood a few things here in how the clocks fit together, but here is what still looks wrong about this patch:
Quoted 5 lines
drivers/clk/socfpga/clk.c +0
-0
drivers/clk/socfpga/clk.c line 64
Quoted 10 lines
drivers/clk/socfpga/clk.c +6
-0@@ -55,7 +55,13 @@#define div_mask (width) ((1 << (width)) - 1)#define streq (a, b) (strcmp((a), (b)) == 0) +#define SYSMGR_SDMMCGRP_CTRL_OFFSET 0x108 +/* SDMMC Group for System Manager defines */ +#define SYSMGR_SDMMC_CTRL_SET (smplsel, drvsel) \ + ((((smplsel) & 0x7) << 3) | (((drvsel) & 0x7) << 0)) +extern void __iomem *clk_mgr_base_addr; +extern void __iomem *sys_manager_base_addr;
As mentioned in yesterday's comments, you should not have the 'extern' declaration for sys_manager_base_addr here. In fact, the existing clk_mgr_base_addr declaration is just as wrong.
Quoted 6 lines
drivers/clk/socfpga/clk.c +6
-0+static int sdmmc_ciuclk_prepare (struct clk_hw *hwclk) +{ +struct device_node *np; +u32 timing[2 ]; +u32 hs_timing; +
drivers/clk/socfpga/clk.c struct socfpga_clk { · line 92
Quoted 10 lines
drivers/clk/socfpga/clk.c +10
-0+ np =of_find_compatible_node (NULL ,NULL ,"rockchip,rk2928-dw-mshc" ); +if (of_property_read_u32_array (np,"samsung,dw-mshc-sdr-timing" , timing,2 )) { +pr_err ("SDMMC: cannot find samsung,dw-mshc-sdr-timing!\n" ); +return -ENODATA ; + } + hs_timing =SYSMGR_SDMMC_CTRL_SET (timing[1 ], timing[0 ]); +writel (hs_timing, sys_manager_base_addr +SYSMGR_SDMMCGRP_CTRL_OFFSET ); +return 0 ; +} +
And in now way should the clock provider code look into the DT properties of the clock consumer. From what I can tell, the dw-mshc code already interprets the "samsung,dw-mshc-sdr-timing" property and uses the data to pass the correct clock rate using 'clk_set_rate()'. The clock code should only use the data passed in the argument to that function to set up the registers and not need to know at all who is setting it.
I am a little confused though what the SYSMGR_SDMMCGRP_CTRL_OFFSET register actually does. It looks like this is just a clock divider, which should be represented as a separate clock node (as you had in v3) and compute the correct factor from the requested clock rate and the parent clock rate.
Arnd
PATCH v4 2/4 clk: socfpga: Add a hook for SD/MMC driver to control CIU clock settings
Quoted 24 lines · Arnd Bergmann
Quoted 10 lines · dinguyen at altera.com
From: Dinh Nguyen <[email protected]>
Populate the .prepare function in the clk-ops for the "
sdmmc_clk" that represents the "ciu" clock for the SD/MMC driver. The prepare function will handle setting the correct clock-phase for the CIU clock of the SD/MMC IP.Re-use the "rockchip,rk2928-dw-mshc" binding as it is already defined and appropriate for the SOCFPGA platform as well.
Signed-off-by Dinh Nguyen <[email protected]>I think with this series we're getting closer to where things should be, but there are still a number of the same problems. Maybe I have misunderstood a few things here in how the clocks fit together, but here is what still looks wrong about this patch:
Quoted 8 lines
drivers/clk/socfpga/clk.c +0
-0@@ -55,7 +55,13 @@#define div_mask (width) ((1 << (width)) - 1)#define streq (a, b) (strcmp((a), (b)) == 0)
Quoted 10 lines
drivers/clk/socfpga/clk.c line 64
Quoted 7 lines
drivers/clk/socfpga/clk.c +6
-0+#define SYSMGR_SDMMCGRP_CTRL_OFFSET 0x108 +/* SDMMC Group for System Manager defines */ +#define SYSMGR_SDMMC_CTRL_SET (smplsel, drvsel) \ + ((((smplsel) & 0x7) << 3) | (((drvsel) & 0x7) << 0)) +extern void __iomem *clk_mgr_base_addr; +extern void __iomem *sys_manager_base_addr;As mentioned in yesterday's comments, you should not have the 'extern' declaration for
sys_manager_base_addrhere. In fact, the existingclk_mgr_base_addrdeclaration is just as wrong.
Yes, will fix..
Quoted 15 lines
Quoted 15 lines
drivers/clk/socfpga/clk.c +14
-0+static int sdmmc_ciuclk_prepare (struct clk_hw *hwclk) +{ +struct device_node *np; +u32 timing[2 ]; +u32 hs_timing; + + np =of_find_compatible_node (NULL ,NULL ,"rockchip,rk2928-dw-mshc" ); +if (of_property_read_u32_array (np,"samsung,dw-mshc-sdr-timing" , timing,2 )) { +pr_err ("SDMMC: cannot find samsung,dw-mshc-sdr-timing!\n" ); +return -ENODATA ; + } + hs_timing =SYSMGR_SDMMC_CTRL_SET (timing[1 ], timing[0 ]); +writel (hs_timing, sys_manager_base_addr +SYSMGR_SDMMCGRP_CTRL_OFFSET ); +return 0 ;
Quoted 8 lines
drivers/clk/socfpga/clk.c
Quoted 2 lines
drivers/clk/socfpga/clk.c +2
-0+} +And in now way should the clock provider code look into the DT properties of the clock consumer. From what I can tell, the dw-mshc code already interprets the "samsung,dw-mshc-sdr-timing" property and uses the data to pass the correct clock rate using '
clk_set_rate()'. The clock code should only use the data passed in the argument to that function to set up the registers and not need to know at all who is setting it.
You're right, the dw-mshc code interprets "samsung,dw-mshc-sdr-timing", but it is
currently doing it in the platform specific code(dw_mmc-exynos and dw_mmc-socfpga).
I was thinking I can remove the platform specific for SOCFPGA. But perhaps now that
patch "mmc: dw_mmc: Make the use of the hold reg generic" is progressing, and
that patch reads "samsung,dw-mshc-sdr-timing" in the generic dw_mmc code, I can now
pass it through the clk_set_rate call.
My initial thought to read "samsung,dw-mshc-sdr-timing" in the socfpga clock driver's was that the SOCFPGA's sdmmc_clk only role in life is to feed the sdmmc block. So
reading the phase shift bits that adjust this clock does seem weird, but a straightforward way
of doing it. I stuck it in the function in .prepare function because the setting of the clock's phase
shift also requires that CIU clock be turned off while the bits are toggled, so the prepare function
seems to work perfectly. So I think you're only concern is that I should figure out a way to pass
the values of "samsung,dw-mshc-sdr-timing" from the dw_mmc driver to the clock driver, correct?
Yes, I can read the "samsung,dw-mshc-sdr-timing" in the dw_mmc code and pass it to the clock
driver using clk_set_rate(), but this method seems more cumbersome, as this clk_set_rate does not
have anything to do with setting the rate, but only the phase shift settings of the clock.
Quoted 5 lines
I am a little confused though what the
SYSMGR_SDMMCGRP_CTRL_OFFSETregister actually does. It looks like this is just a clock divider, which should be represented as a separate clock node (as you had in v3) and compute the correct factor from the requested clock rate and the parent clock rate.
The SYSMGR_SDMMCGRP_CTRL_OFFSET is just putting the 2 values of "samsung,dw-mshc-sdr-timing"
into a a single u32 value to be written to the register. "samsung,dw-mshc-sdr-timing" has 2 values that
controls the phase shift of 2 clocks, the drive clock and the sample clock.
Thanks,
Dinh
Quoted 2 lines
Arnd
PATCH v4 2/4 clk: socfpga: Add a hook for SD/MMC driver to control CIU clock settings
Quoted 8 lines · Dinh Nguyen
Quoted 6 lines · Arnd Bergmann
And in now way should the clock provider code look into the DT properties of the clock consumer. From what I can tell, the dw-mshc code already interprets the "samsung,dw-mshc-sdr-timing" property and uses the data to pass the correct clock rate using '
clk_set_rate()'. The clock code should only use the data passed in the argument to that function to set up the registers and not need to know at all who is setting it.
Quoted 11 lines
You're right, the dw-mshc code interprets "samsung,dw-mshc-sdr-timing", but it is
currently doing it in the platform specificcode(dw_mmc-exynos and dw_mmc-socfpga).
I was thinking I can remove the platform specific for SOCFPGA. But perhaps now that
patch "mmc:dw_mmc: Make the use of the hold reg generic" is progressing, and
that patch reads "samsung,dw-mshc-sdr-timing" in the genericdw_mmccode, I can now
pass it through theclk_set_ratecall.
Ok, good.
Quoted 14 lines
My initial thought to read "samsung,dw-mshc-sdr-timing" in the socfpga clock driver's was that the SOCFPGA's
sdmmc_clkonly role in life is to feed the sdmmc block. So
reading the phase shift bits that adjust this clock does seem weird, but a straightforward way
of doing it. I stuck it in the function in .prepare function because the setting of the clock's phase
shift also requires that CIU clock be turned off while the bits are toggled, so the prepare function
seems to work perfectly. So I think you're only concern is that I should figure out a way to pass
the values of "samsung,dw-mshc-sdr-timing" from thedw_mmcdriver to the clock driver, correct?
Quoted 6 lines
Yes, I can read the "samsung,dw-mshc-sdr-timing" in the
dw_mmccode and pass it to the clock
driver usingclk_set_rate(), but this method seems more cumbersome, as thisclk_set_ratedoes not
have anything to do with setting the rate, but only the phase shift settings of the clock.
I see, that does indeed sound a bit strange and is probably not the best API. I'm not that familiar with what is actually going on at the hardware level. Can you explain in a little more detail what the phase setting is about? What are the possible values here and what units are being used?
Quoted 9 lines
Quoted 4 lines
I am a little confused though what the
SYSMGR_SDMMCGRP_CTRL_OFFSETregister actually does. It looks like this is just a clock divider, which should be represented as a separate clock node (as you had in v3) and compute the correct factor from the requested clock rate and the parent clock rate.The
SYSMGR_SDMMCGRP_CTRL_OFFSETis just putting the 2 values of "samsung,dw-mshc-sdr-timing"
into a a single u32 value to be written to the register. "samsung,dw-mshc-sdr-timing" has 2 values that
controls the phase shift of 2 clocks, the drive clock and the sample clock.
Do other clocks ever have the same requirement? Would it make sense to have a generic clk_set_phase interface for this?
If not, could the values alternatively (i.e. departing from the samsung method) be encoded in the clock specifier? That would come down to setting #clock-cells = <2> for this clock and using a complex clock in the mshc node to point at it using
<&phandle $phase1 $phase2> Arnd Arnd
PATCH v4 2/4 clk: socfpga: Add a hook for SD/MMC driver to control CIU clock settings
Quoted 41 lines · Arnd Bergmann
Quoted 7 lines · Dinh Nguyen
Quoted 6 lines · Arnd Bergmann
And in now way should the clock provider code look into the DT properties of the clock consumer. From what I can tell, the dw-mshc code already interprets the "samsung,dw-mshc-sdr-timing" property and uses the data to pass the correct clock rate using '
clk_set_rate()'. The clock code should only use the data passed in the argument to that function to set up the registers and not need to know at all who is setting it.Quoted 11 lines
You're right, the dw-mshc code interprets "samsung,dw-mshc-sdr-timing", but it is
currently doing it in the platform specificcode(dw_mmc-exynos and dw_mmc-socfpga).
I was thinking I can remove the platform specific for SOCFPGA. But perhaps now that
patch "mmc:dw_mmc: Make the use of the hold reg generic" is progressing, and
that patch reads "samsung,dw-mshc-sdr-timing" in the genericdw_mmccode, I can now
pass it through theclk_set_ratecall.Ok, good.
Quoted 14 lines
My initial thought to read "samsung,dw-mshc-sdr-timing" in the socfpga clock driver's was that the SOCFPGA's
sdmmc_clkonly role in life is to feed the sdmmc block. So
reading the phase shift bits that adjust this clock does seem weird, but a straightforward way
of doing it. I stuck it in the function in .prepare function because the setting of the clock's phase
shift also requires that CIU clock be turned off while the bits are toggled, so the prepare function
seems to work perfectly. So I think you're only concern is that I should figure out a way to pass
the values of "samsung,dw-mshc-sdr-timing" from thedw_mmcdriver to the clock driver, correct?Quoted 6 lines
Yes, I can read the "samsung,dw-mshc-sdr-timing" in the
dw_mmccode and pass it to the clock
driver usingclk_set_rate(), but this method seems more cumbersome, as thisclk_set_ratedoes not
have anything to do with setting the rate, but only the phase shift settings of the clock.
Quoted 5 lines
I see, that does indeed sound a bit strange and is probably not the best API. I'm not that familiar with what is actually going on at the hardware level. Can you explain in a little more detail what the phase setting is about? What are the possible values here and what units are being used?
The phase shift settings for this clock is a way for the IP block to meet the delay and hold
timing requirements for the different data modes of the SD. For example by shifting the input
clock that is feeding the CIU by 90 degrees in SDR25 mode, the minimum hold/delay time of 2ns
is achieved.
The values can be:
0 -> 0 degrees0x1 -> 45 degrees0x2 -> 90 degrees0x3 -> 135 degrees0x4 -> 180 degrees0x5 -> 225 degrees0x6 -> 270 degrees0x7 -> 315 degrees
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
I am a little confused though what the
SYSMGR_SDMMCGRP_CTRL_OFFSETregister actually does. It looks like this is just a clock divider, which should be represented as a separate clock node (as you had in v3) and compute the correct factor from the requested clock rate and the parent clock rate.
Quoted 7 lines
Quoted 5 lines
The
SYSMGR_SDMMCGRP_CTRL_OFFSETis just putting the 2 values of "samsung,dw-mshc-sdr-timing"
into a a single u32 value to be written to the register. "samsung,dw-mshc-sdr-timing" has 2 values that
controls the phase shift of 2 clocks, the drive clock and the sample clock.Do other clocks ever have the same requirement? Would it make sense to have a generic
clk_set_phaseinterface for this?
I am not aware of any other clocks that need these phase adjustments.
Quoted 6 lines
If not, could the values alternatively (i.e. departing from the samsung method) be encoded in the clock specifier? That would come down to setting #clock-cells = <2> for this clock and using a complex clock in the mshc node to point at it using
<&phandle $phase1 $phase2>
Hmm..this could also be done. I just sent out a V6 that uses the clk_set_rate API. I believe
that there can be other platforms that can use this approach.
Thanks,
Dinh
Quoted 3 lines
Arnd
Arnd
PATCH v4 3/4 mmc: dw_mmc-socfpga: Remove the SOCFPGA specific platform for dw_mmc
In reply to dinguyen at altera.comFrom: Dinh Nguyen <[email protected]>
It turns now that the only really platform specific code that is needed for SOCFPGA is using the SDMMC_CMD_USE_HOLD_REG in the prepare_command function. Since the Rockchip already has this functionality, re-use the code that is already in dw_mmc-pltfm.c.
--- drivers/mmc/host/Kconfig | 8 --- drivers/mmc/host/dw_mmc-socfpga.c | 138 ------------------------------------- 2 files changed, 146 deletions(-) delete mode 100644 drivers/mmc/host/dw_mmc-socfpga.c
drivers/mmc/host/Kconfig +0 -8
@@ -567,14 +567,6 @@ config MMC_DW_EXYNOS Synopsys DesignWare Memory Card Interface driver. Select this option for platforms based on Exynos4 and Exynos5 SoC's. -config MMC_DW_SOCFPGA - tristate "SOCFPGA specific extensions for Synopsys DW Memory Card Interface" - depends on MMC_DW && MFD_SYSCON - select MMC_DW_PLTFM - help - This selects support for Altera SoCFPGA specific extensions to the - Synopsys DesignWare Memory Card Interface driver. - config MMC_DW_PCI tristate "Synopsys Designware MCI support on PCI bus" depends on MMC_DW && PCI
drivers/mmc/host/dw_mmc-socfpga.c deleted +0 -138
138 lines not on this page · raw message
Signature · 1 line
1.7.9.5
PATCH v4 4/4 ARM: socfpga_defconfig: enable SD/MMC support
In reply to dinguyen at altera.comFrom: Dinh Nguyen <[email protected]>
Enables the dw_mmc driver for SOCFPGA.
--- arch/arm/configs/socfpga_defconfig | 2 ++ 1 file changed, 2 insertions(+)
arch/arm/configs/socfpga_defconfig +2 -0
@@ -82,3 +82,5 @@ CONFIG_DEBUG_INFO=y CONFIG_ENABLE_DEFAULT_TRACERS=y CONFIG_DEBUG_USER=y CONFIG_XZ_DEC=y +CONFIG_MMC=y +CONFIG_MMC_DW=y
Signature · 1 line
1.7.9.5