From: "Cousson, Benoit" <b-cousson@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Paul Walmsley <paul@pwsan.com>
Cc: Greg KH <greg@kroah.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gadiyar, Anand" <gadiyar@ti.com>, "Balbi, Felipe" <balbi@ti.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: linux-next: manual merge of the usb tree with the omap tree
Date: Thu, 23 Dec 2010 19:29:43 +0100 [thread overview]
Message-ID: <4D139517.3010608@ti.com> (raw)
In-Reply-To: <20101223171859.f6842045.sfr@canb.auug.org.au>
+ Paul "the omap clock guru".
At first glance, that seems almost good.
Except for a couple of nodes that seems to lose their 3630 support.
I'm just wondering why the original usb clock node is
kept after the introduction of the "ehci-omap.0" clock
node. But this is anyway harmless.
What commits are generating this conflict?
On 12/23/2010 7:18 AM, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the usb tree got a conflict in
> arch/arm/mach-omap2/clock3xxx_data.c and
> arch/arm/mach-omap2/clock44xx_data.c between various commits from the omap
> tree and various commits from the usb tree.
>
> I did a quick fix (which may be completely wrong - see below).
> diff --cc arch/arm/mach-omap2/clock3xxx_data.c
> index 9ab817e,0579604..0000000
> --- a/arch/arm/mach-omap2/clock3xxx_data.c
> +++ b/arch/arm/mach-omap2/clock3xxx_data.c
> @@@ -3275,17 -3267,18 +3275,18 @@@ static struct omap_clk omap3xxx_clks[]
> CLK(NULL, "gfx_l3_ick", &gfx_l3_ick, CK_3430ES1),
> CLK(NULL, "gfx_cg1_ck", &gfx_cg1_ck, CK_3430ES1),
> CLK(NULL, "gfx_cg2_ck", &gfx_cg2_ck, CK_3430ES1),
> - CLK(NULL, "sgx_fck", &sgx_fck, CK_3430ES2 | CK_3517),
> - CLK(NULL, "sgx_ick", &sgx_ick, CK_3430ES2 | CK_3517),
> + CLK(NULL, "sgx_fck", &sgx_fck, CK_3430ES2PLUS | CK_3517 | CK_36XX),
> + CLK(NULL, "sgx_ick", &sgx_ick, CK_3430ES2PLUS | CK_3517 | CK_36XX),
> CLK(NULL, "d2d_26m_fck", &d2d_26m_fck, CK_3430ES1),
> - CLK(NULL, "modem_fck", &modem_fck, CK_343X),
> - CLK(NULL, "sad2d_ick", &sad2d_ick, CK_343X),
> - CLK(NULL, "mad2d_ick", &mad2d_ick, CK_343X),
> + CLK(NULL, "modem_fck", &modem_fck, CK_34XX | CK_36XX),
> + CLK(NULL, "sad2d_ick", &sad2d_ick, CK_34XX | CK_36XX),
> + CLK(NULL, "mad2d_ick", &mad2d_ick, CK_34XX | CK_36XX),
> CLK(NULL, "gpt10_fck", &gpt10_fck, CK_3XXX),
> CLK(NULL, "gpt11_fck", &gpt11_fck, CK_3XXX),
> - CLK(NULL, "cpefuse_fck", &cpefuse_fck, CK_3430ES2 | CK_AM35XX),
> - CLK(NULL, "ts_fck", &ts_fck, CK_3430ES2 | CK_AM35XX),
> - CLK(NULL, "usbtll_fck", &usbtll_fck, CK_3430ES2 | CK_AM35XX),
> + CLK(NULL, "cpefuse_fck", &cpefuse_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK(NULL, "ts_fck", &ts_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK(NULL, "usbtll_fck", &usbtll_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
That one could be removed after the introduction of the following one if the
clk_get(dev, "usbtll_fck") API is used.
> + CLK("ehci-omap.0", "usbtll_fck", &usbtll_fck, CK_3430ES2 | CK_AM35XX),
If only that one is kept it should be:
+ CLK("ehci-omap.0", "usbtll_fck", &usbtll_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
Assuming that one of the conflicting commits was trying to add the 3630 support.
> CLK("omap-mcbsp.1", "prcm_fck", &core_96m_fck, CK_3XXX),
> CLK("omap-mcbsp.5", "prcm_fck", &core_96m_fck, CK_3XXX),
> CLK(NULL, "core_96m_fck", &core_96m_fck, CK_3XXX),
> @@@ -3309,26 -3302,27 +3310,27 @@@
> CLK(NULL, "core_12m_fck", &core_12m_fck, CK_3XXX),
> CLK("omap_hdq.0", "fck", &hdq_fck, CK_3XXX),
> CLK(NULL, "ssi_ssr_fck", &ssi_ssr_fck_3430es1, CK_3430ES1),
> - CLK(NULL, "ssi_ssr_fck", &ssi_ssr_fck_3430es2, CK_3430ES2),
> + CLK(NULL, "ssi_ssr_fck", &ssi_ssr_fck_3430es2, CK_3430ES2PLUS | CK_36XX),
> CLK(NULL, "ssi_sst_fck", &ssi_sst_fck_3430es1, CK_3430ES1),
> - CLK(NULL, "ssi_sst_fck", &ssi_sst_fck_3430es2, CK_3430ES2),
> + CLK(NULL, "ssi_sst_fck", &ssi_sst_fck_3430es2, CK_3430ES2PLUS | CK_36XX),
> CLK(NULL, "core_l3_ick", &core_l3_ick, CK_3XXX),
> - CLK("musb_hdrc", "ick", &hsotgusb_ick_3430es1, CK_3430ES1),
> - CLK("musb_hdrc", "ick", &hsotgusb_ick_3430es2, CK_3430ES2PLUS | CK_36XX),
> + CLK("musb-omap2430", "ick", &hsotgusb_ick_3430es1, CK_3430ES1),
> - CLK("musb-omap2430", "ick", &hsotgusb_ick_3430es2, CK_3430ES2),
> ++ CLK("musb-omap2430", "ick", &hsotgusb_ick_3430es2, CK_3430ES2PLUS | CK_36XX),
> CLK(NULL, "sdrc_ick", &sdrc_ick, CK_3XXX),
> CLK(NULL, "gpmc_fck", &gpmc_fck, CK_3XXX),
> - CLK(NULL, "security_l3_ick", &security_l3_ick, CK_343X),
> - CLK(NULL, "pka_ick", &pka_ick, CK_343X),
> + CLK(NULL, "security_l3_ick", &security_l3_ick, CK_34XX | CK_36XX),
> + CLK(NULL, "pka_ick", &pka_ick, CK_34XX | CK_36XX),
> CLK(NULL, "core_l4_ick", &core_l4_ick, CK_3XXX),
> - CLK(NULL, "usbtll_ick", &usbtll_ick, CK_3430ES2 | CK_AM35XX),
> + CLK(NULL, "usbtll_ick", &usbtll_ick, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK("ehci-omap.0", "usbtll_ick", &usbtll_ick, CK_3430ES2 | CK_AM35XX),
ditto, should probably be:
+ CLK("ehci-omap.0", "usbtll_ick", &usbtll_ick, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> - CLK("mmci-omap-hs.2", "ick", &mmchs3_ick, CK_3430ES2 | CK_AM35XX),
> - CLK(NULL, "icr_ick", &icr_ick, CK_343X),
> - CLK("omap-aes", "ick", &aes2_ick, CK_343X),
> - CLK("omap-sham", "ick", &sha12_ick, CK_343X),
> - CLK(NULL, "des2_ick", &des2_ick, CK_343X),
> + CLK("mmci-omap-hs.2", "ick", &mmchs3_ick, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK(NULL, "icr_ick", &icr_ick, CK_34XX | CK_36XX),
> + CLK("omap-aes", "ick", &aes2_ick, CK_34XX | CK_36XX),
> + CLK("omap-sham", "ick", &sha12_ick, CK_34XX | CK_36XX),
> + CLK(NULL, "des2_ick", &des2_ick, CK_34XX | CK_36XX),
> CLK("mmci-omap-hs.1", "ick", &mmchs2_ick, CK_3XXX),
> CLK("mmci-omap-hs.0", "ick", &mmchs1_ick, CK_3XXX),
> - CLK(NULL, "mspro_ick", &mspro_ick, CK_343X),
> + CLK(NULL, "mspro_ick", &mspro_ick, CK_34XX | CK_36XX),
> CLK("omap_hdq.0", "ick", &hdq_ick, CK_3XXX),
> CLK("omap2_mcspi.4", "ick", &mcspi4_ick, CK_3XXX),
> CLK("omap2_mcspi.3", "ick", &mcspi3_ick, CK_3XXX),
> @@@ -3361,14 -3355,17 +3363,17 @@@
> CLK("omapdss", "video_fck", &dss_96m_fck, CK_3XXX),
> CLK("omapdss", "dss2_fck", &dss2_alwon_fck, CK_3XXX),
> CLK("omapdss", "ick", &dss_ick_3430es1, CK_3430ES1),
> - CLK("omapdss", "ick", &dss_ick_3430es2, CK_3430ES2 | CK_AM35XX),
> - CLK(NULL, "cam_mclk", &cam_mclk, CK_343X),
> - CLK(NULL, "cam_ick", &cam_ick, CK_343X),
> - CLK(NULL, "csi2_96m_fck", &csi2_96m_fck, CK_343X),
> - CLK(NULL, "usbhost_120m_fck", &usbhost_120m_fck, CK_3430ES2 | CK_AM35XX),
> + CLK("omapdss", "ick", &dss_ick_3430es2, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK(NULL, "cam_mclk", &cam_mclk, CK_34XX | CK_36XX),
> + CLK(NULL, "cam_ick", &cam_ick, CK_34XX | CK_36XX),
> + CLK(NULL, "csi2_96m_fck", &csi2_96m_fck, CK_34XX | CK_36XX),
> + CLK(NULL, "usbhost_120m_fck", &usbhost_120m_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK("ehci-omap.0", "hs_fck", &usbhost_120m_fck, CK_3430ES2 | CK_AM35XX),
ditto
> - CLK(NULL, "usbhost_48m_fck", &usbhost_48m_fck, CK_3430ES2 | CK_AM35XX),
> + CLK(NULL, "usbhost_48m_fck", &usbhost_48m_fck, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK("ehci-omap.0", "fs_fck", &usbhost_48m_fck, CK_3430ES2 | CK_AM35XX),
ditto
> - CLK(NULL, "usbhost_ick", &usbhost_ick, CK_3430ES2 | CK_AM35XX),
> + CLK(NULL, "usbhost_ick", &usbhost_ick, CK_3430ES2PLUS | CK_AM35XX | CK_36XX),
> + CLK("ehci-omap.0", "usbhost_ick", &usbhost_ick, CK_3430ES2 | CK_AM35XX),
ditto
> - CLK(NULL, "usim_fck", &usim_fck, CK_3430ES2),
> + CLK(NULL, "usim_fck", &usim_fck, CK_3430ES2PLUS | CK_36XX),
> CLK(NULL, "gpt1_fck", &gpt1_fck, CK_3XXX),
> CLK(NULL, "wkup_32k_fck", &wkup_32k_fck, CK_3XXX),
> CLK(NULL, "gpio1_dbck", &gpio1_dbck, CK_3XXX),
> diff --cc arch/arm/mach-omap2/clock44xx_data.c
> index c426adc,bfcd19f..0000000
> --- a/arch/arm/mach-omap2/clock44xx_data.c
> +++ b/arch/arm/mach-omap2/clock44xx_data.c
> @@@ -3198,6 -2937,10 +3198,7 @@@ static struct omap_clk omap44xx_clks[]
> CLK(NULL, "uart3_fck", &uart3_fck, CK_443X),
> CLK(NULL, "uart4_fck", &uart4_fck, CK_443X),
> CLK(NULL, "usb_host_fs_fck", &usb_host_fs_fck, CK_443X),
> + CLK("ehci-omap.0", "fs_fck", &usb_host_fs_fck, CK_443X),
> - CLK(NULL, "usb_host_hs_utmi_p3_clk", &usb_host_hs_utmi_p3_clk, CK_443X),
> - CLK(NULL, "usb_host_hs_hsic60m_p1_clk", &usb_host_hs_hsic60m_p1_clk, CK_443X),
> - CLK(NULL, "usb_host_hs_hsic60m_p2_clk", &usb_host_hs_hsic60m_p2_clk, CK_443X),
I'm not sure these 3 nodes should be removed. AFAIR, they were just slightly moved in lo branch.
Regards,
Benoit
next prev parent reply other threads:[~2010-12-23 18:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 6:18 linux-next: manual merge of the usb tree with the omap tree Stephen Rothwell
2010-12-23 6:18 ` Stephen Rothwell
2010-12-23 8:36 ` Felipe Balbi
2010-12-23 18:29 ` Cousson, Benoit [this message]
2011-01-06 15:02 ` Ming Lei
2011-01-06 15:07 ` Anand Gadiyar
2011-01-06 15:25 ` Ming Lei
2011-01-06 15:50 ` Ming Lei
2011-01-07 14:07 ` Anand Gadiyar
2011-01-07 14:15 ` Ming Lei
2011-01-07 14:39 ` Anand Gadiyar
2011-01-07 15:20 ` Anand Gadiyar
2011-01-07 18:54 ` Gadiyar, Anand
2011-01-07 19:24 ` Felipe Balbi
2011-01-10 13:53 ` Ming Lei
2011-01-10 14:09 ` Anand Gadiyar
2011-01-06 15:43 ` Brad Parker
2011-01-06 16:59 ` Koen Kooi
2011-01-06 17:57 ` Nishanth Menon
2011-01-06 18:15 ` Kevin Hilman
2011-01-06 18:21 ` Nishanth Menon
2011-01-06 18:38 ` Kevin Hilman
2011-01-06 20:24 ` Nishanth Menon
2011-01-06 21:29 ` Kevin Hilman
2011-01-06 18:27 ` Paul Walmsley
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 5:58 Stephen Rothwell
2011-03-02 5:58 ` Stephen Rothwell
2011-03-02 5:58 Stephen Rothwell
2011-03-02 5:58 ` Stephen Rothwell
2011-03-02 5:57 Stephen Rothwell
2011-03-02 5:57 ` Stephen Rothwell
2011-03-03 8:48 ` Felipe Balbi
2011-03-03 16:02 ` Greg KH
2011-03-03 17:39 ` Felipe Balbi
2011-03-02 5:57 Stephen Rothwell
2011-03-02 5:57 ` Stephen Rothwell
2011-03-02 8:23 ` Felipe Balbi
2011-03-02 14:23 ` Greg KH
2011-03-03 8:18 ` Felipe Balbi
2009-11-11 8:30 Stephen Rothwell
2009-11-11 8:30 ` Stephen Rothwell
2009-11-11 19:12 ` Tony Lindgren
2009-11-11 19:20 ` Tony Lindgren
2009-11-11 21:52 ` Stephen Rothwell
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=4D139517.3010608@ti.com \
--to=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=gadiyar@ti.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.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 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.