From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mxs: defconfig: Enable CONFIG_COMMON_CLK_DEBUG
Date: Thu, 5 Jul 2012 08:25:40 +0200 [thread overview]
Message-ID: <20120705062540.GK30009@pengutronix.de> (raw)
In-Reply-To: <20120705005504.GG2595@S2101-09.ap.freescale.net>
On Thu, Jul 05, 2012 at 08:55:06AM +0800, Shawn Guo wrote:
> On Mon, Jul 02, 2012 at 05:35:51PM -0300, Fabio Estevam wrote:
> > From: Fabio Estevam <fabio.estevam@freescale.com>
> >
> > With the common clock framework in place, it is useful to enable
> > CONFIG_COMMON_CLK_DEBUG option, in order to easily inspect the clock tree.
> >
>
> I'm ambiguous on this. It does look useful, but on the other hand,
> I'm wondering why it hasn't been enabled by framework by default.
>
> Sascha, what's your take on this?
I also like to have debugfs support enabled in the defconfigs. I don't
know if it's desirable to enable this unconditionally when
CONFIG_DEBUGFS is enabled because I think the clk debugfs support can
have some bad influence on performance.
I think Fabios patches are fine for nor. If we decide to enable clk
debugfs support later unconditionally than all we have is two unused
lines in the defconfigs.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-07-05 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 20:35 [PATCH 1/2] ARM: imx: defconfig: Enable CONFIG_COMMON_CLK_DEBUG Fabio Estevam
2012-07-02 20:35 ` [PATCH 2/2] ARM: mxs: " Fabio Estevam
2012-07-05 0:55 ` Shawn Guo
2012-07-05 6:25 ` Sascha Hauer [this message]
2012-07-05 6:37 ` Shawn Guo
2012-07-05 7:06 ` Sascha Hauer
2012-07-05 7:33 ` Shawn Guo
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=20120705062540.GK30009@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).