From: Tony Lindgren <tony@atomide.com> To: Tero Kristo <t-kristo@ti.com> Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org, mturquette@baylibre.com, sboyd@codeaurora.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 8/9] ARM: OMAP4: hwmod_data: use module clocks from DT Date: Fri, 18 Dec 2015 07:11:56 -0800 [thread overview] Message-ID: <20151218151156.GH23396@atomide.com> (raw) In-Reply-To: <1450447141-29936-9-git-send-email-t-kristo@ti.com> * Tero Kristo <t-kristo@ti.com> [151218 05:57]: > Replace the usage of prcm->clkstctrl with main_clk:s provided via DT. > This is done in preparation to get rid of hwmod data from kernel. ... > --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c > +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c > @@ -334,10 +329,9 @@ static struct omap_hwmod omap44xx_counter_32k_hwmod = { > .class = &omap44xx_counter_hwmod_class, > .clkdm_name = "l4_wkup_clkdm", > .flags = HWMOD_SWSUP_SIDLE, > - .main_clk = "sys_32k_ck", > + .main_clk = "counter_32k_mod_ck", > .prcm = { > .omap4 = { > - .clkctrl_offs = OMAP4_CM_WKUP_SYNCTIMER_CLKCTRL_OFFSET, > .context_offs = OMAP4_RM_WKUP_SYNCTIMER_CONTEXT_OFFSET, > }, > }, Care to describe why the main_clk now needs to be modified or added? Can that too come from dts now? Regards, Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren) To: linux-arm-kernel@lists.infradead.org Subject: [RFC 8/9] ARM: OMAP4: hwmod_data: use module clocks from DT Date: Fri, 18 Dec 2015 07:11:56 -0800 [thread overview] Message-ID: <20151218151156.GH23396@atomide.com> (raw) In-Reply-To: <1450447141-29936-9-git-send-email-t-kristo@ti.com> * Tero Kristo <t-kristo@ti.com> [151218 05:57]: > Replace the usage of prcm->clkstctrl with main_clk:s provided via DT. > This is done in preparation to get rid of hwmod data from kernel. ... > --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c > +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c > @@ -334,10 +329,9 @@ static struct omap_hwmod omap44xx_counter_32k_hwmod = { > .class = &omap44xx_counter_hwmod_class, > .clkdm_name = "l4_wkup_clkdm", > .flags = HWMOD_SWSUP_SIDLE, > - .main_clk = "sys_32k_ck", > + .main_clk = "counter_32k_mod_ck", > .prcm = { > .omap4 = { > - .clkctrl_offs = OMAP4_CM_WKUP_SYNCTIMER_CLKCTRL_OFFSET, > .context_offs = OMAP4_RM_WKUP_SYNCTIMER_CONTEXT_OFFSET, > }, > }, Care to describe why the main_clk now needs to be modified or added? Can that too come from dts now? Regards, Tony
next prev parent reply other threads:[~2015-12-18 15:11 UTC|newest] Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-18 13:58 [RFC 0/9] ARM: OMAP4: hwmod clkctrl conversion to DT + clock driver Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` [RFC 1/9] ARM: OMAP2+: omap_device: create clock alias purely from DT data Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 15:16 ` Tony Lindgren 2015-12-18 15:16 ` Tony Lindgren 2015-12-18 13:58 ` [RFC 2/9] ARM: OMAP2+: hwmod: initialize main clocks directly from DT Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` [RFC 3/9] clk: ti: remove un-used definitions from public clk_hw_omap struct Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` [RFC 4/9] clk: ti: mux: export mux clock APIs locally Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` [RFC 5/9] dt-bindings: clk: ti: Document module clock type Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` [RFC 6/9] clk: ti: add support for omap4 module clocks Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 15:36 ` Tony Lindgren 2015-12-18 15:36 ` Tony Lindgren 2016-01-01 5:48 ` Michael Turquette 2016-01-01 5:48 ` Michael Turquette 2016-01-01 5:48 ` Michael Turquette 2016-01-04 7:36 ` Tero Kristo 2016-01-04 7:36 ` Tero Kristo 2016-01-04 7:36 ` Tero Kristo 2016-01-04 10:21 ` Geert Uytterhoeven 2016-01-04 10:21 ` Geert Uytterhoeven 2016-01-04 10:21 ` Geert Uytterhoeven 2016-01-04 13:27 ` Tero Kristo 2016-01-04 13:27 ` Tero Kristo 2016-01-04 14:42 ` Russell King - ARM Linux 2016-01-04 14:42 ` Russell King - ARM Linux 2016-01-04 16:37 ` Tony Lindgren 2016-01-04 16:37 ` Tony Lindgren 2016-01-04 19:15 ` Tero Kristo 2016-01-04 19:15 ` Tero Kristo 2016-01-05 1:23 ` Michael Turquette 2016-01-05 1:23 ` Michael Turquette 2016-01-05 1:23 ` Michael Turquette 2016-01-05 1:29 ` Michael Turquette 2016-01-05 1:29 ` Michael Turquette 2016-01-05 1:29 ` Michael Turquette 2015-12-18 13:58 ` [RFC 7/9] ARM: dts: omap4: add hwmod " Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 13:58 ` Tero Kristo 2015-12-18 15:06 ` Tony Lindgren 2015-12-18 15:06 ` Tony Lindgren 2015-12-18 13:59 ` [RFC 8/9] ARM: OMAP4: hwmod_data: use module clocks from DT Tero Kristo 2015-12-18 13:59 ` Tero Kristo 2015-12-18 13:59 ` Tero Kristo 2015-12-18 15:11 ` Tony Lindgren [this message] 2015-12-18 15:11 ` Tony Lindgren 2015-12-18 13:59 ` [RFC 9/9] clk: ti: omap4: update clock aliases to reflect new module clocks Tero Kristo 2015-12-18 13:59 ` Tero Kristo 2015-12-18 13:59 ` Tero Kristo
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=20151218151156.GH23396@atomide.com \ --to=tony@atomide.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=mturquette@baylibre.com \ --cc=sboyd@codeaurora.org \ --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: 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.