From: Tony Lindgren <tony@atomide.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Tero Kristo <t-kristo@ti.com>, Rajendra <rnayak@ti.com>,
Nishanth Menon <nm@ti.com>, Benoit Cousson <b-cousson@ti.com>,
Joel A Fernandes <joelagnel@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH RFC 1/3] clk: omap: introduce clock driver
Date: Tue, 4 Jun 2013 07:52:52 -0700 [thread overview]
Message-ID: <20130604145252.GJ3331@atomide.com> (raw)
In-Reply-To: <1370327958-19776-2-git-send-email-mturquette@linaro.org>
* Mike Turquette <mturquette@linaro.org> [130603 23:45]:
> Parses OMAP clock data from DT and registers those clocks with the clock
> framework. dt_omap_clk_init must be called early during boot for timer
> initialization so it is exported and called from the existing clock code
> instead of probing like a real driver.
Thanks for doing this, makes sense to me. I have queued up patches to
make omap4 DT only, so this is the way to go.
> --- /dev/null
> +++ b/include/linux/clk/omap.h
> @@ -0,0 +1,24 @@
> +/*
> + * Copyright (C) 2010 Broadcom
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
> + */
> +
> +#ifndef __LINUX_CLK_OMAP_H_
> +#define __LINUX_CLK_OMAP_H_
> +
> +int __init dt_omap_clk_init(void);
> +
> +#endif
Maybe leave out the Broadcom copyright from this header? :)
Regards,
Tony
next prev parent reply other threads:[~2013-06-04 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:39 [PATCH RFC 0/3] first pass converting omap4 clock data to DT Mike Turquette
2013-06-04 6:39 ` [PATCH RFC 1/3] clk: omap: introduce clock driver Mike Turquette
2013-06-04 14:52 ` Tony Lindgren [this message]
2013-06-14 22:12 ` Grant Likely
2013-06-04 6:39 ` [PATCH RFC 2/3] ARM: dts: omap4 clock data Mike Turquette
2013-06-04 14:55 ` Tony Lindgren
[not found] ` <20130604145543.GK3331-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-06-04 18:34 ` Mike Turquette
2013-06-04 19:37 ` Tony Lindgren
2013-06-04 6:39 ` [PATCH RFC 3/3] ARM: omap4: register DT clocks & remove old data Mike Turquette
2013-06-04 13:28 ` [PATCH RFC 0/3] first pass converting omap4 clock data to DT Tero Kristo
2013-06-05 6:45 ` Mike Turquette
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=20130604145252.GJ3331@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=joelagnel@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).