From: Ben Gamari <bgamari@gmail.com>
To: linux-usb@vger.kernel.org
Cc: linux-omap@vger.kernel.org, balbi@ti.com,
Ajay Kumar Gupta <ajay.gupta@ti.com>
Subject: Re: [PATCH] musb: am35x: fix compile error due to control apis
Date: Thu, 30 Dec 2010 11:20:33 -0500 [thread overview]
Message-ID: <87zkrnmdv2.fsf@gmail.com> (raw)
In-Reply-To: <1291399965-19623-1-git-send-email-ajay.gupta@ti.com>
On Fri, 3 Dec 2010 23:42:45 +0530, Ajay Kumar Gupta <ajay.gupta@ti.com> wrote:
> As the control.h have been moved to new location and it's
> uses are not allowed to drivers directly so moving the phy
> control, interrupt clear and reset functionality to board
> files.
>
I could have sworn I tried applying this before but I guess I must be
wrong. Perhaps I am missing something?
CC arch/arm/mach-omap2/usb-musb.o
arch/arm/mach-omap2/usb-musb.c: In function ‘am35x_musb_phy_power’:
arch/arm/mach-omap2/usb-musb.c:45: error: implicit declaration of function ‘omap_ctrl_readl’
arch/arm/mach-omap2/usb-musb.c:45: error: ‘AM35XX_CONTROL_DEVCONF2’ undeclared (first use in this function)
arch/arm/mach-omap2/usb-musb.c:45: error: (Each undeclared identifier is reported only once
arch/arm/mach-omap2/usb-musb.c:45: error: for each function it appears in.)
arch/arm/mach-omap2/usb-musb.c:50: error: implicit declaration of function ‘omap_ctrl_writel’
arch/arm/mach-omap2/usb-musb.c: In function ‘am35x_musb_clear_irq’:
arch/arm/mach-omap2/usb-musb.c:78: error: ‘AM35XX_CONTROL_LVL_INTR_CLEAR’ undeclared (first use in this function)
arch/arm/mach-omap2/usb-musb.c:79: error: ‘AM35XX_USBOTGSS_INT_CLR’ undeclared (first use in this function)
arch/arm/mach-omap2/usb-musb.c: In function ‘am35x_musb_set_mode’:
arch/arm/mach-omap2/usb-musb.c:86: error: ‘AM35XX_CONTROL_DEVCONF2’ undeclared (first use in this function)
arch/arm/mach-omap2/usb-musb.c: In function ‘usb_musb_init’:
arch/arm/mach-omap2/usb-musb.c:175: error: expected expression before ‘}’ token
- Ben
--
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
prev parent reply other threads:[~2010-12-30 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 18:12 [PATCH] musb: am35x: fix compile error due to control apis Ajay Kumar Gupta
[not found] ` <1291399965-19623-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-12-03 18:50 ` Anand Gadiyar
2010-12-04 13:53 ` Gupta, Ajay Kumar
2010-12-03 19:23 ` Sergei Shtylyov
2010-12-04 13:57 ` Gupta, Ajay Kumar
2010-12-23 17:16 ` Ben Gamari
[not found] ` <87hbe41kbd.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-27 9:20 ` Felipe Balbi
[not found] ` <20101227092038.GB2301-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2010-12-30 7:44 ` Ben Gamari
[not found] ` <877heriu1j.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-30 12:27 ` Felipe Balbi
2010-12-30 13:06 ` Sergei Shtylyov
2010-12-30 15:00 ` Ben Gamari
2010-12-30 15:24 ` Anca Emanuel
[not found] ` <AANLkTinE9Dgz9nCFv-1d=DdF22OEXSYn16s7krxo3CGp-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-30 16:04 ` Felipe Balbi
2010-12-30 16:05 ` Felipe Balbi
2010-12-30 16:14 ` Sergei Shtylyov
2010-12-30 16:20 ` Ben Gamari [this message]
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=87zkrnmdv2.fsf@gmail.com \
--to=bgamari@gmail.com \
--cc=ajay.gupta@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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