Thread (17 messages) 17 messages, 3 authors, 2012-07-06

[PATCH 1/5] ARM: tegra: set up wlan clocks for tegra dt

From: Wei Ni <hidden>
Date: 2012-07-05 03:18:40
Also in: linux-tegra, lkml

On Wed, 2012-07-04 at 19:51 +0800, Marc Dietrich wrote:
Am Mittwoch, 4. Juli 2012, 19:23:33 schrieb Wei Ni:
quoted
On Wed, 2012-07-04 at 18:43 +0800, Marc Dietrich wrote:
quoted
Am Mittwoch, 4. Juli 2012, 17:34:44 schrieb Wei Ni:
quoted
Set up the wlan clock tree for Tegra20 and Tegra30.

Signed-off-by: Wei Ni <redacted>
---

 arch/arm/mach-tegra/board-dt-tegra20.c |    1 +
 arch/arm/mach-tegra/board-dt-tegra30.c |    1 +
 2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-tegra/board-dt-tegra20.c
b/arch/arm/mach-tegra/board-dt-tegra20.c index 70a19a9..fbcc7d9 100644
--- a/arch/arm/mach-tegra/board-dt-tegra20.c
+++ b/arch/arm/mach-tegra/board-dt-tegra20.c
@@ -78,6 +78,7 @@ static __initdata struct tegra_clk_init_table
tegra_dt_clk_init_table[] = { { "pll_a",      "pll_p_out1",   56448000,

  true },
  
 	{ "pll_a_out0", "pll_a",        11289600,       true },
 	{ "cdev1",      NULL,           0,              true },

+	{ "blink",      "clk_32k",      32768,          true },
what's the reason to enable this on all boards? Would it make sense to set
this to "false" instead?
This clock is used for the wlan device, it need to be enabled, so that
the wlan device can be powered on, and then the mmc driver can enumerate
it.
My question was more why you enable it for *all* boards, even those without 
wlan cards connected to the sdhci. Defining it, but set it to "false", would 
give the driver the chance to enable it only on request. On the other hand, 
the impact on additional power consumption may be too low to measure.
Yes we have thought about this issue.
In here we need to enable this clock before loading wifi driver, so that
the mmc driver can enumerate it.
This likes another thing that the SD controller should be taught how to
provide to clients, such as trigger the power/reset gpios. We had talked
about it in the:
http://www.spinics.net/lists/linux-wireless/msg92093.html

And we are trying to provide the tegra clk framework support, so at that
time we could set this clock for different boards.

So I suppose we can just dump it into the clk init tables for now.
Marc
quoted
quoted
quoted
 	{ "i2s1",       "pll_a_out0",   11289600,       false},
 	{ "i2s2",       "pll_a_out0",   11289600,       false},
 	{ NULL,		NULL,		0,		0},
diff --git a/arch/arm/mach-tegra/board-dt-tegra30.c
b/arch/arm/mach-tegra/board-dt-tegra30.c index 53bf60f..2d73c61 100644
--- a/arch/arm/mach-tegra/board-dt-tegra30.c
+++ b/arch/arm/mach-tegra/board-dt-tegra30.c
@@ -61,6 +61,7 @@ static __initdata struct tegra_clk_init_table
tegra_dt_clk_init_table[] = { { "pll_a_out0",	"pll_a",	11289600,	true },

 	{ "extern1",	"pll_a_out0",	0,		true },
 	{ "clk_out_1",	"extern1",	0,		true },

+	{ "blink",	"clk_32k",	32768,		true },

 	{ "i2s0",	"pll_a_out0",	11289600,	false},
 	{ "i2s1",	"pll_a_out0",	11289600,	false},
 	{ "i2s2",	"pll_a_out0",	11289600,	false},
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help