From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: Mike Turquette <mturquette@linaro.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] clk: flatten clk tree in debugfs
Date: Fri, 30 May 2014 11:10:43 +0300 [thread overview]
Message-ID: <20140530081043.GO5961@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <538656C1.3090402@codeaurora.org>
> >>
> >> Mike, others,
> >>
> >> Any objections to this idea? If there's not much opposition, then maybe
> >> Peter can actually spend time fixing and testing this patch?
> >
> > Idea seems fine. I had actually considered removing the hiearchal
> > directory structure completely with the advent of clk_dump and
> > clk_summary, but if there is value in the flattened directory structure
> > then I'm all for it.
> I think the additional value of the flattened directory probably comes
> from internal tree patches that would add set rate capability to clocks,
> etc that would be helpful with testing.
>
Yes. Eg. I posted a patch to dump a clocks registers for Tegra.
> Agree with all the comments so far.
>
> Peter,
>
> Looks like there's some support and no opposition so far. So do you want
> to send out a real patch that's been tested and with the comments above
> taken care of?
Yes. I will do that.
Cheers,
Peter.
prev parent reply other threads:[~2014-05-30 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 10:59 Peter De Schrijver
2014-05-23 22:24 ` Saravana Kannan
2014-05-26 11:14 ` Peter De Schrijver
2014-05-28 17:47 ` Saravana Kannan
2014-05-28 18:52 ` Mike Turquette
2014-05-28 21:36 ` Saravana Kannan
2014-05-30 8:10 ` Peter De Schrijver [this message]
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=20140530081043.GO5961@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=skannan@codeaurora.org \
/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
all inboxes | Powered by JetHome®