Skip to contentSkip to conversation

ARM: DaVinci: ASoC: Adds McASP clock support for TI DM646X processor

PATCH In review Naresh Medisetty 2 participants 2 messages Mar 16, 2009

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 6/9 ARM: DaVinci: ASoC: Adds McASP clock support for TI DM646X processor

Adds McASP clock support for TI DM646X processor

---
This patch applies to the DaVinci git tree available at http://git.kernel.org/?p=linux/kernel/git/khilman/linux-davinci.git;a=commit;h=486afa37130356662213cc1a2199a285b4fd72af.

 arch/arm/mach-davinci/dm646x.c |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
arch/arm/mach-davinci/dm646x.c +14 -0
index af040cf..0aee774 100644
@@ -185,6 +185,18 @@ static struct clk gpio_clk = {
 	.lpsc = DM646X_LPSC_GPIO,
 };
 
+static struct clk mcasp0_clk = {
+	.name = "mcasp0",
+	.parent = &pll1_sysclk3,
+	.lpsc = DM646X_LPSC_McASP0,
+};
+
+static struct clk mcasp1_clk = {
+	.name = "mcasp0",
+	.parent = &pll1_sysclk3,
+	.lpsc = DM646X_LPSC_McASP1,
+};
+
 static struct clk aemif_clk = {
 	.name = "aemif",
 	.parent = &pll1_sysclk3,
@@ -253,6 +265,8 @@ struct davinci_clk dm646x_clks[] = {
 	CLK(NULL, "uart2", &uart2_clk),
 	CLK("i2c_davinci.1", NULL, &i2c_clk),
 	CLK(NULL, "gpio", &gpio_clk),
+	CLK("soc-audio.0", NULL, &mcasp0_clk),
+	CLK("soc-audio.1", NULL, &mcasp1_clk),
 	CLK(NULL, "aemif", &aemif_clk),
 	CLK("davinci_emac.1", NULL, &emac_clk),
 	CLK(NULL, "pwm0", &pwm0_clk),
Signature · 1 line
1.5.6
#1 lore raw

arch/arm/mach-davinci/dm646x.c struct davinci_clk dm646x_clks[] = { · line 269

Quoted 2 lines · Naresh Medisetty
arch/arm/mach-davinci/dm646x.c +2 -0
+	CLK("soc-audio.0", NULL, &mcasp0_clk),
+	CLK("soc-audio.1", NULL, &mcasp1_clk),

Assuming this is a shorthand for defining two platform devices for two ASoC cards I'd suggest that you instead move towards registering clocks for the DAIs and probing them as platform devices - take a look at how the PXA AC97 driver now does this for an example. The soc-audio device will hopefully get removed at some point and you can't guarantee that the user won't want to put the two DAIs into a single sound card.