Hello.
On 11/11/2014 9:42 AM, Yoshihiro Kaneko wrote:
From: Shinobu Uehara <[email protected]>
Signed-off-by: Shinobu Uehara <[email protected]>
Signed-off-by: Yoshihiro Kaneko <[email protected]>
---
This patch is based on mmc-next branch of Chris Ball's mmc tree.
drivers/mmc/host/sh_mmcif.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
index 656fbba..fe9a8b7 100644
--- a/drivers/mmc/host/sh_mmcif.c
+++ b/drivers/mmc/host/sh_mmcif.c
[...]
@@ -1371,6 +1373,8 @@ static int sh_mmcif_probe(struct platform_device *pdev)
struct resource *res;
void __iomem *reg;
const char *name;
+ struct device_node *np = pdev->dev.of_node;
+ int clk_rate;
'u32'.
irq[0] = platform_get_irq(pdev, 0);
irq[1] = platform_get_irq(pdev, 1);
@@ -1433,6 +1437,16 @@ static int sh_mmcif_probe(struct platform_device *pdev)
dev_err(&pdev->dev, "cannot get clock: %d\n", ret);
goto eclkget;
}
+
+ if (np && !of_property_read_u32(np, "renesas,clk-rate", &clk_rate)) {
Doesn't the standard "clock-frequency" prop fit here?
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
