Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-27 Thread Stephen Warren
On 06/27/2014 06:19 AM, Peter De Schrijver wrote: > On Thu, Jun 26, 2014 at 05:52:16PM +0200, Stephen Warren wrote: >> On 06/26/2014 09:48 AM, Peter De Schrijver wrote: >>> When writing a module for testing or debugging purposes, there is no way to >>> get hold of clk handles. This patch solves

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-27 Thread Peter De Schrijver
On Thu, Jun 26, 2014 at 05:52:16PM +0200, Stephen Warren wrote: > On 06/26/2014 09:48 AM, Peter De Schrijver wrote: > > When writing a module for testing or debugging purposes, there is no way to > > get hold of clk handles. This patch solves this by exposing all valid clocks > > as clkdev's for

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-27 Thread Peter De Schrijver
On Thu, Jun 26, 2014 at 05:52:16PM +0200, Stephen Warren wrote: On 06/26/2014 09:48 AM, Peter De Schrijver wrote: When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-27 Thread Stephen Warren
On 06/27/2014 06:19 AM, Peter De Schrijver wrote: On Thu, Jun 26, 2014 at 05:52:16PM +0200, Stephen Warren wrote: On 06/26/2014 09:48 AM, Peter De Schrijver wrote: When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Sergei Shtylyov
Hello. On 06/26/2014 07:48 PM, Peter De Schrijver wrote: When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the virtual device tegra-clk-debug. Signed-off-by: Peter De

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Stephen Warren
On 06/26/2014 09:48 AM, Peter De Schrijver wrote: > When writing a module for testing or debugging purposes, there is no way to > get hold of clk handles. This patch solves this by exposing all valid clocks > as clkdev's for the virtual device tegra-clk-debug. This is to support clk_get_sys()? I

[PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Peter De Schrijver
When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the virtual device tegra-clk-debug. Signed-off-by: Peter De Schrijver --- drivers/clk/tegra/clk.c |6 ++ 1 files

[PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Peter De Schrijver
When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the virtual device tegra-clk-debug. Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com --- drivers/clk/tegra/clk.c |

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Stephen Warren
On 06/26/2014 09:48 AM, Peter De Schrijver wrote: When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the virtual device tegra-clk-debug. This is to support clk_get_sys()? I

Re: [PATCH] clk: tegra: export clock names for debugging

2014-06-26 Thread Sergei Shtylyov
Hello. On 06/26/2014 07:48 PM, Peter De Schrijver wrote: When writing a module for testing or debugging purposes, there is no way to get hold of clk handles. This patch solves this by exposing all valid clocks as clkdev's for the virtual device tegra-clk-debug. Signed-off-by: Peter De