From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: balbi@ti.com
Cc: Paul Walmsley <paul@pwsan.com>,
hemahk@ti.com, tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: OMAP2-only kernel compile broken
Date: Sun, 10 Jul 2011 03:35:13 -0700 [thread overview]
Message-ID: <4E198061.5060202@ti.com> (raw)
In-Reply-To: <20110710095216.GN31978@legolas.emea.dhcp.ti.com>
Felipe,
On 7/10/2011 2:52 AM, Felipe Balbi wrote:
> From: Felipe Balbi<balbi@ti.com>
> Date: Sun, 10 Jul 2011 12:22:20 +0300
> Subject: [PATCH] usb: musb: fix build breakage
> Organization: Texas Instruments\n
>
> This patch fixes the compilation brekage which
> commits 208466dc ("usb: otg:OMAP4430: Powerdown
> the internal PHY when USB is disabled") and
> fb91cde4 ("usb: musb: OMAP4430: Power down
> the PHY during board init") introduced when
> building a OMAP2-only kernel.
>
> LD .tmp_vmlinux1
> arch/arm/mach-omap2/built-in.o:(.data+0x7ce0): undefined reference to
> +`omap4430_phy_init'
> arch/arm/mach-omap2/built-in.o:(.data+0x7ce4): undefined reference to
> +`omap4430_phy_exit'
> arch/arm/mach-omap2/built-in.o:(.data+0x7ce8): undefined reference to
> +`omap4430_phy_power'
> arch/arm/mach-omap2/built-in.o:(.data+0x7cec): undefined reference to
> +`omap4430_phy_set_clk'
> arch/arm/mach-omap2/built-in.o:(.data+0x7cf0): undefined reference to
> +`omap4430_phy_suspend'
> make: *** [.tmp_vmlinux1] Error 1
>
> Cc:stable@kernel.org
> Reported-by: Paul Walmsley<paul@pwsan.com>
> Signed-off-by: Felipe Balbi<balbi@ti.com>
> ---
> arch/arm/plat-omap/include/plat/usb.h | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-omap/include/plat/usb.h b/arch/arm/plat-omap/include/plat/usb.h
> index 17d3c93..99dd64e 100644
> --- a/arch/arm/plat-omap/include/plat/usb.h
> +++ b/arch/arm/plat-omap/include/plat/usb.h
> @@ -103,11 +103,25 @@ extern void usbhs_init(const struct usbhs_omap_board_data *pdata);
> extern int omap_usbhs_enable(struct device *dev);
> extern void omap_usbhs_disable(struct device *dev);
>
> +#if defined(CONFIG_ARCH_OMAP4) || defined(CONFIG_ARCH_OMAP3)
> extern int omap4430_phy_power(struct device *dev, int ID, int on);
> extern int omap4430_phy_set_clk(struct device *dev, int on);
> extern int omap4430_phy_init(struct device *dev);
> extern int omap4430_phy_exit(struct device *dev);
> extern int omap4430_phy_suspend(struct device *dev, int suspend);
The comment is not related to this patch, but are above functions
limited to _omap4430_ only or omap446x may also need them. If the
phy is same on all OMAP4 devices, then another patch with renaming
all these functions to omap4_* should be done. Or even better is
make use of phy IP name itslef.
Regrads,
Santosh
next prev parent reply other threads:[~2011-07-10 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 1:57 OMAP2-only kernel compile broken Paul Walmsley
2011-07-10 9:52 ` Felipe Balbi
2011-07-10 10:35 ` Santosh Shilimkar [this message]
2011-07-10 11:43 ` Paul Walmsley
2011-07-11 6:21 ` Felipe Balbi
2011-07-11 6:31 ` Paul Walmsley
2011-07-11 6:42 ` Paul Walmsley
2011-07-11 6:43 ` Felipe Balbi
2011-07-11 8:26 ` Tony Lindgren
2011-07-11 9:24 ` Felipe Balbi
2011-08-15 15:44 ` Paul Walmsley
2011-08-15 16:02 ` Felipe Balbi
2011-07-11 6:57 ` Felipe Balbi
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=4E198061.5060202@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=balbi@ti.com \
--cc=hemahk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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.