From: Paul Walmsley <paul@pwsan.com> To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Nicole Chalhoub <n-chalhoub@ti.com> Subject: [PATCH 6/8] OMAP3 clock: McBSP 2, 3, 4 functional clock parent is PER_96M_FCLK, not CORE_96M_FCLK Date: Thu, 17 Dec 2009 21:20:21 -0700 [thread overview] Message-ID: <20091218042020.27280.77746.stgit@localhost.localdomain> (raw) In-Reply-To: <20091218041912.27280.92152.stgit@localhost.localdomain> The correct parent of the McBSP 2, 3, and 4 functional clocks is PER_96M_FCLK, not CORE_96M_FCLK. Fix this in the OMAP clock tree. Reported by Nicole Chalhoub <n-chalhoub@ti.com>. Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Nicole Chalhoub <n-chalhoub@ti.com> --- arch/arm/mach-omap2/clock34xx_data.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/clock34xx_data.c b/arch/arm/mach-omap2/clock34xx_data.c index c60b19a..7eea9fb 100644 --- a/arch/arm/mach-omap2/clock34xx_data.c +++ b/arch/arm/mach-omap2/clock34xx_data.c @@ -2747,7 +2747,7 @@ static struct clk mcbsp4_ick = { }; static const struct clksel mcbsp_234_clksel[] = { - { .parent = &core_96m_fck, .rates = common_mcbsp_96m_rates }, + { .parent = &per_96m_fck, .rates = common_mcbsp_96m_rates }, { .parent = &mcbsp_clks, .rates = common_mcbsp_mcbsp_rates }, { .parent = NULL } };
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 6/8] OMAP3 clock: McBSP 2, 3, 4 functional clock parent is PER_96M_FCLK, not CORE_96M_FCLK Date: Thu, 17 Dec 2009 21:20:21 -0700 [thread overview] Message-ID: <20091218042020.27280.77746.stgit@localhost.localdomain> (raw) In-Reply-To: <20091218041912.27280.92152.stgit@localhost.localdomain> The correct parent of the McBSP 2, 3, and 4 functional clocks is PER_96M_FCLK, not CORE_96M_FCLK. Fix this in the OMAP clock tree. Reported by Nicole Chalhoub <n-chalhoub@ti.com>. Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Nicole Chalhoub <n-chalhoub@ti.com> --- arch/arm/mach-omap2/clock34xx_data.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/clock34xx_data.c b/arch/arm/mach-omap2/clock34xx_data.c index c60b19a..7eea9fb 100644 --- a/arch/arm/mach-omap2/clock34xx_data.c +++ b/arch/arm/mach-omap2/clock34xx_data.c @@ -2747,7 +2747,7 @@ static struct clk mcbsp4_ick = { }; static const struct clksel mcbsp_234_clksel[] = { - { .parent = &core_96m_fck, .rates = common_mcbsp_96m_rates }, + { .parent = &per_96m_fck, .rates = common_mcbsp_96m_rates }, { .parent = &mcbsp_clks, .rates = common_mcbsp_mcbsp_rates }, { .parent = NULL } };
next prev parent reply other threads:[~2009-12-18 4:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-18 4:20 [PATCH 0/8] OMAP clock & IO mapping fixes for 2.6.33-rc2 Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 1/8] OMAP2: remove duplicated #include Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 2/8] ARM: OMAP3: PM: Fix the Invalid CM_CLKSTCTRL reg access Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 3/8] OMAP2xxx IO mapping: mark DSP mappings as being 2420-only Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 4/8] OMAP2420 IO mapping: move IVA mapping virtual address out of vmalloc space Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 5/8] OMAP3: clock: add clockdomains for UART1 & 2 Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley [this message] 2009-12-18 4:20 ` [PATCH 6/8] OMAP3 clock: McBSP 2, 3, 4 functional clock parent is PER_96M_FCLK, not CORE_96M_FCLK Paul Walmsley 2009-12-18 4:20 ` [PATCH 7/8] OMAP3 clock: Add capability to change rate of dpll4_m5_ck Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley 2009-12-18 4:20 ` [PATCH 8/8] OMAP clock: remove incorrect EXPORT_SYMBOL()s Paul Walmsley 2009-12-18 4:20 ` Paul Walmsley
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=20091218042020.27280.77746.stgit@localhost.localdomain \ --to=paul@pwsan.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=n-chalhoub@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.