From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] clk-imx35: Add clko clock support
Date: Wed, 25 Jun 2014 21:12:35 +0800 [thread overview]
Message-ID: <20140625131234.GF2224@dragon> (raw)
In-Reply-To: <1857714.L0sRRUOXiN@ws-stein>
On Wed, Jun 25, 2014 at 10:58:12AM +0200, Alexander Stein wrote:
> > > > > @@ -260,6 +273,7 @@ int __init mx35_clocks_init(void)
> > > > > clk_register_clkdev(clk[nfc_div], NULL, "imx25-nand.0");
> > > > > clk_register_clkdev(clk[csi_gate], NULL, "mx3-camera.0");
> > > > > clk_register_clkdev(clk[admux_gate], "audmux", NULL);
> > > > > + clk_register_clkdev(clk[clko_gate], NULL, "clko.0");
> > > >
> > > > Will this lookup be used somewhere?
> > >
> > > Well, as this is a pretty customizable output clock signal, I think this will only be used in custom board implementation. Or is there any generic driver to configure an arbitrary programmable clock?
> > >
> >
> > I prefer to add this lookup only when there is an in-tree user for it.
>
> Well, the cko (cko1 and cko2) clocks on i.MX6 are also added. Though I can't find any user of that. So why addind it despite that?
>
To be clear, I'm not talking about the cko clock itself but the lookup
to cko, i.e. clk_register_clkdev() of "clko.0".
Shawn
prev parent reply other threads:[~2014-06-25 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:27 [PATCH 1/1] clk-imx35: Add clko clock support Alexander Stein
2014-06-20 8:15 ` Shawn Guo
2014-06-23 6:21 ` Alexander Stein
2014-06-25 6:53 ` Shawn Guo
2014-06-25 8:58 ` Alexander Stein
2014-06-25 9:54 ` Russell King - ARM Linux
2014-06-25 13:12 ` Shawn Guo [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=20140625131234.GF2224@dragon \
--to=shawn.guo@freescale.com \
--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).