On Thu, May 29, 2014 at 07:52:00PM +0200, Stephen Warren wrote:
> On 05/28/2014 10:51 AM, Peter De Schrijver wrote:
> > This patch set introduces the 'regs' debugfs entry which shows the
> > contents of all registers related to a clock.
>
> Would it be better to create a regmap object for the
On Thu, May 29, 2014 at 07:52:00PM +0200, Stephen Warren wrote:
On 05/28/2014 10:51 AM, Peter De Schrijver wrote:
This patch set introduces the 'regs' debugfs entry which shows the
contents of all registers related to a clock.
Would it be better to create a regmap object for the entire
On 05/28/2014 10:51 AM, Peter De Schrijver wrote:
> This patch set introduces the 'regs' debugfs entry which shows the
> contents of all registers related to a clock.
Would it be better to create a regmap object for the entire clock module
register space, and then get all the debugfs stuff for
On 05/28/2014 10:51 AM, Peter De Schrijver wrote:
This patch set introduces the 'regs' debugfs entry which shows the
contents of all registers related to a clock.
Would it be better to create a regmap object for the entire clock module
register space, and then get all the debugfs stuff for
This patch set introduces the 'regs' debugfs entry which shows the
contents of all registers related to a clock.
Peter De Schrijver (2):
clk: tegra: Add debugfs infrastructure
clk: tegra: periph, PLL and super clk debugfs entries
drivers/clk/tegra/clk-periph.c | 24 +++
This patch set introduces the 'regs' debugfs entry which shows the
contents of all registers related to a clock.
Peter De Schrijver (2):
clk: tegra: Add debugfs infrastructure
clk: tegra: periph, PLL and super clk debugfs entries
drivers/clk/tegra/clk-periph.c | 24 +++
6 matches
Mail list logo
