From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
Mike Turquette <mturquette@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/2] debugfs entries for Tegra clocks
Date: Thu, 29 May 2014 11:52:00 -0600 [thread overview]
Message-ID: <538773C0.30906@wwwdotorg.org> (raw)
In-Reply-To: <1401295868-18697-1-git-send-email-pdeschrijver@nvidia.com>
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 free?
next prev parent reply other threads:[~2014-05-29 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 16:51 [PATCH 0/2] debugfs entries for Tegra clocks Peter De Schrijver
2014-05-28 16:51 ` [PATCH 1/2] clk: tegra: Add debugfs infrastructure Peter De Schrijver
2014-05-28 16:51 ` [PATCH 2/2] clk: tegra: periph, PLL and super clk debugfs entries Peter De Schrijver
2014-05-29 17:52 ` Stephen Warren [this message]
2014-05-30 13:12 ` [PATCH 0/2] debugfs entries for Tegra clocks Peter De Schrijver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538773C0.30906@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox