From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 clock: remove extra init from csi2_96m_fck
Date: Wed, 10 Sep 2008 16:47:36 -0700 [thread overview]
Message-ID: <20080910234736.GS21163@atomide.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0809091056390.30431@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [080909 09:59]:
>
> csi2_96m_fck no longer should attempt to init its clockdomain pointer; the
> clock framework now does this by default. Applies on top of the "Update
> powerdomains and clockdomains" series sent earlier.
>
> Verified on 3430SDP ES2.
Pushing today.
Tony
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
> arch/arm/mach-omap2/clock34xx.h | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clock34xx.h b/arch/arm/mach-omap2/clock34xx.h
> index 65568c3..56ae83f 100644
> --- a/arch/arm/mach-omap2/clock34xx.h
> +++ b/arch/arm/mach-omap2/clock34xx.h
> @@ -2298,7 +2298,6 @@ static struct clk cam_ick = {
> static struct clk csi2_96m_fck = {
> .name = "csi2_96m_fck",
> .parent = &core_96m_fck,
> - .init = &omap2_init_clk_clkdm,
> .enable_reg = _OMAP34XX_CM_REGADDR(OMAP3430_CAM_MOD, CM_FCLKEN),
> .enable_bit = OMAP3430_EN_CSI2_SHIFT,
> .flags = CLOCK_IN_OMAP343X,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-10 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 16:58 [PATCH] OMAP3 clock: remove extra init from csi2_96m_fck Paul Walmsley
2008-09-10 23:47 ` Tony Lindgren [this message]
2008-09-12 16:30 ` Aguirre Rodriguez, Sergio Alberto
2008-09-12 17:33 ` Tony Lindgren
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=20080910234736.GS21163@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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