[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1381839982-3026-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
Date: Tue, 15 Oct 2013 13:26:22 +0100
From: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To: mturquette@...aro.org
Cc: tomasz.figa@...il.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, patches@...nsource.wolfsonmicro.com,
Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Subject: [PATCH] clk: s3c64xx: Correct spi bus clock hookups
Correct the SPI bus clock hookups to match their state before the switch
to this driver. With out this patch my system (based on an s3c6410)
can't locate any spibus clock.
Note, I only have a passing familiarity with this driver and subsystem
so this patch could probably use a careful eye.
Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
---
drivers/clk/samsung/clk-s3c64xx.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/samsung/clk-s3c64xx.c b/drivers/clk/samsung/clk-s3c64xx.c
index 7d2c842..f6ac974 100644
--- a/drivers/clk/samsung/clk-s3c64xx.c
+++ b/drivers/clk/samsung/clk-s3c64xx.c
@@ -356,8 +356,12 @@ static struct samsung_clock_alias s3c64xx_clock_aliases[] = {
ALIAS(SCLK_MMC2, "s3c-sdhci.2", "mmc_busclk.2"),
ALIAS(SCLK_MMC1, "s3c-sdhci.1", "mmc_busclk.2"),
ALIAS(SCLK_MMC0, "s3c-sdhci.0", "mmc_busclk.2"),
- ALIAS(SCLK_SPI1, "s3c6410-spi.1", "spi-bus"),
- ALIAS(SCLK_SPI0, "s3c6410-spi.0", "spi-bus"),
+ ALIAS(PCLK_SPI1, "s3c6410-spi.1", "spi_busclk0"),
+ ALIAS(SCLK_SPI1, "s3c6410-spi.1", "spi_busclk1"),
+ ALIAS(SCLK_SPI1_48, "s3c6410-spi.1", "spi_busclk2"),
+ ALIAS(PCLK_SPI0, "s3c6410-spi.0", "spi_busclk0"),
+ ALIAS(SCLK_SPI0, "s3c6410-spi.0", "spi_busclk1"),
+ ALIAS(SCLK_SPI0_48, "s3c6410-spi.0", "spi_busclk2"),
ALIAS(SCLK_AUDIO1, "samsung-pcm.1", "audio-bus"),
ALIAS(SCLK_AUDIO1, "samsung-i2s.1", "audio-bus"),
ALIAS(SCLK_AUDIO0, "samsung-pcm.0", "audio-bus"),
--
1.7.2.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists