> ---
> Hi Paul,
>
> I could not find the patches from Sebastien's series:
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg82971.html
>
> But AFAIK you have taken them for 3.9.
>
> This patch is on top of it to fix compilation error.
>
> Regards,
>
-omap@vger.kernel.org/msg82971.html
But AFAIK you have taken them for 3.9.
This patch is on top of it to fix compilation error.
Regards,
Peter
arch/arm/mach-omap2/omap_hwmod_reset.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_reset.c
b/arch/arm/mach-
On 11/20/2012 10:25 AM, Constantine Shulyupin wrote:
> From: Constantine Shulyupin
>
> Added required linux/errno.h
>
> Signed-off-by: Constantine Shulyupin
This supposed to be already fixed:
https://patchwork.kernel.org/patch/1728521/
> ---
> arch/arm/mach-omap2/cm_common.c |1 +
> 1 fi
Hi Mauro,
On Sunday 07 October 2012 10:17:18 Mauro Carvalho Chehab wrote:
> Em Tue, 2 Oct 2012 09:31:58 -0700 Tony Lindgren escreveu:
> > * Ido Yariv [121001 15:48]:
> > > Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
> > > mach-omap2") moved omap34xx.h to mach-omap2. Thi
* Mauro Carvalho Chehab [121007 06:18]:
> Em Tue, 2 Oct 2012 09:31:58 -0700
> Tony Lindgren escreveu:
>
> > * Ido Yariv [121001 15:48]:
> > > Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
> > > mach-omap2") moved omap34xx.h to mach-omap2. This broke omap3isp, as it
> >
Em Tue, 2 Oct 2012 09:31:58 -0700
Tony Lindgren escreveu:
> * Ido Yariv [121001 15:48]:
> > Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
> > mach-omap2") moved omap34xx.h to mach-omap2. This broke omap3isp, as it
> > includes omap34xx.h.
> >
> > Instead of moving omap3
* Ido Yariv [121001 15:48]:
> Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
> mach-omap2") moved omap34xx.h to mach-omap2. This broke omap3isp, as it
> includes omap34xx.h.
>
> Instead of moving omap34xx to platform_data, simply add the two
> definitions the driver needs
Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
mach-omap2") moved omap34xx.h to mach-omap2. This broke omap3isp, as it
includes omap34xx.h.
Instead of moving omap34xx to platform_data, simply add the two
definitions the driver needs and remove the include altogether.
Signe
Commit c49f34bc ("ARM: OMAP2+ Move SoC specific headers to be local to
mach-omap2") moved omap34xx.h to mach-omap2. This broke omap3isp, as it
includes omap34xx.h.
Instead of moving omap34xx to platform_data, simply add the two
definitions the driver needs and remove the include altogether.
Signe
Hello,
Which branch should i use from TI[1] tree? I need to boot linux
with linaro-nano.
I tried: p-linux-omap-3.4 branch but i am getting compilation error for
omap4plus_pm_min_defconfig and omap2plus_defconfig:
/home/arm/work/kernel/mywork/linux.git/arch/arm/mm/proc-v7.S:
Assembler messages
* Govindraj.R [09 03:12]:
> Fix below compilation failure on mainline kernel 3.2-rc1
> when omap_l3_noc.c is built as module.
>
> arch/arm/mach-omap2/omap_l3_noc.c:240: error: expected ',' or ';' before
> 'MODULE_DEVICE_TABLE'
>
> Signed-off-by: Govindraj.R
> Acked-by: Santosh Shilimkar
1fe7bde8846ad389e Mon Sep 17 00:00:00 2001
>> From: Govindraj.R
>> Date: Tue, 8 Nov 2011 16:57:22 +0530
>> Subject: [PATCH] OMAP2+: Fix Compilation error on current mainline
>>
>> Fix below compilation failure on mainline kernel commit id
>> 1ea6b8f48918282bdca0b32a3
Fix below compilation failure on mainline kernel 3.2-rc1
when omap_l3_noc.c is built as module.
arch/arm/mach-omap2/omap_l3_noc.c:240: error: expected ',' or ';' before
'MODULE_DEVICE_TABLE'
Signed-off-by: Govindraj.R
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/omap_l3_noc.c |2 +-
s the right one.[1]
--
Thanks,
Govindraj.R
[1]:
From 9d244c0dea4de10ab9052fc1fe7bde8846ad389e Mon Sep 17 00:00:00 2001
From: Govindraj.R
Date: Tue, 8 Nov 2011 16:57:22 +0530
Subject: [PATCH] OMAP2+: Fix Compilation error on current mainline
Fix below compilation failure on mainline kernel comm
On Tue, Nov 8, 2011 at 4:24 PM, Santosh Shilimkar
wrote:
> On Tuesday 08 November 2011 04:16 PM, Cousson, Benoit wrote:
>> Hi Govind,
>>
>> On 11/8/2011 7:28 AM, Govindraj.R wrote:
>>> Patch to fix below compilation error on latest mainline commit
>>> b32fc0
On Tuesday 08 November 2011 04:16 PM, Cousson, Benoit wrote:
> Hi Govind,
>
> On 11/8/2011 7:28 AM, Govindraj.R wrote:
>> Patch to fix below compilation error on latest mainline commit
>> b32fc0a0629bf5894b35f33554c118aacfd0d1e2 with omap2plus_defconfig.
>>
>>
Hi Govind,
On 11/8/2011 7:28 AM, Govindraj.R wrote:
Patch to fix below compilation error on latest mainline commit
b32fc0a0629bf5894b35f33554c118aacfd0d1e2 with omap2plus_defconfig.
arch/arm/mach-omap2/omap_l3_noc.c:250: error: 'THIS_MODULE' undeclared here
(not in a functi
On Tue, Nov 8, 2011 at 11:58 AM, Govindraj.R wrote:
> Patch to fix below compilation error on latest mainline commit
> b32fc0a0629bf5894b35f33554c118aacfd0d1e2 with omap2plus_defconfig.
>
> arch/arm/mach-omap2/omap_l3_noc.c:250: error: 'THIS_MODULE' undeclared here
> (no
Patch to fix below compilation error on latest mainline commit
b32fc0a0629bf5894b35f33554c118aacfd0d1e2 with omap2plus_defconfig.
arch/arm/mach-omap2/omap_l3_noc.c:250: error: 'THIS_MODULE' undeclared here
(not in a function)
make[1]: *** [arch/arm/mach-omap2/omap_l3_noc.o] Error 1
* Janusz Krzysztofik [110530 15:43]:
>
> Detected and corrected while building for Amstrad Delta, confirmed with
> omap1_defconfig.
Thanks, will queue this fix.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
M
Forward-declare platform_device structure in
arch/arm/plat-omap/include/plat/flash.h, otherwise compilation may break
with:
In file included from arch/arm/mach-omap1/flash.c:15:
arch/arm/plat-omap/include/plat/flash.h:14: warning: 'struct platform_device'
declared inside parameter list
arch/arm/
Include from
arch/arm/plat-omap/include/plat/flash.h, otherwise compilation may break
with:
In file included from arch/arm/mach-omap1/flash.c:15:
arch/arm/plat-omap/include/plat/flash.h:14: warning: 'struct platform_device'
declared inside parameter list
arch/arm/plat-omap/include/plat/flash.h
On Mon, May 30, 2011 at 11:44:01PM +0200, Janusz Krzysztofik wrote:
> Include from
> arch/arm/plat-omap/include/plat/flash.h, otherwise compilation may break
> with:
>
> In file included from arch/arm/mach-omap1/flash.c:15:
> arch/arm/plat-omap/include/plat/flash.h:14: warning: 'struct platform
On Tue, Dec 07, 2010 at 07:25:12PM +0530, Gupta, Ajay Kumar wrote:
Hi,
>> Is AM35x that different ? Can't you just write to MUSB_INTRRX
>> MUSB_INTRTX and MUSB_INTRUSB ??
>Writing to MUSB_INTRRX/TX/USB wouldn't help. We have to clear interrupt
>Bit in control register INTR_LVL_CLR.
I see, thank
Hi,
> >> Is AM35x that different ? Can't you just write to MUSB_INTRRX
> >> MUSB_INTRTX and MUSB_INTRUSB ??
> >Writing to MUSB_INTRRX/TX/USB wouldn't help. We have to clear interrupt
> >Bit in control register INTR_LVL_CLR.
>
> I see, thanks for the info :-)
Felipe,
I have recreated this patch (
On Mon, Dec 06, 2010 at 05:24:53PM +0530, Gupta, Ajay Kumar wrote:
On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
>> >We already have generic APIs so I think we can pass function pointers
to
>> >musb driver via "struct omap_musb_board_data",
>> >
>> > struct omap_musb_board_da
> On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
> >> >We already have generic APIs so I think we can pass function pointers
> to
> >> >musb driver via "struct omap_musb_board_data",
> >> >
> >> > struct omap_musb_board_data {
> >> >+ void(*phy_on) (void)
> >> >+ void(*p
On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
>We already have generic APIs so I think we can pass function pointers to
>musb driver via "struct omap_musb_board_data",
>
> struct omap_musb_board_data {
>+ void(*phy_on) (void)
>+ void(*phy_off) (void)
>+ void (*
> >We already have generic APIs so I think we can pass function pointers to
> >musb driver via "struct omap_musb_board_data",
> >
> > struct omap_musb_board_data {
> >+void(*phy_on) (void)
> >+void(*phy_off) (void)
> >+void (*intr_clr) (void)
> > }
> >
> >Reset part can be done
On Thu, Dec 02, 2010 at 04:13:50PM +0530, Gupta, Ajay Kumar wrote:
>> why don't you add a proper otg_transceiver driver for am35x ?
>> Is it like omap4's internal phy ? A separate block ?
>
>AM35x PHY is built inside the ip and we need to configure it through
>PHY control register.
>
>Additionall
> >> why don't you add a proper otg_transceiver driver for am35x ?
> >> Is it like omap4's internal phy ? A separate block ?
> >
> >AM35x PHY is built inside the ip and we need to configure it through
> >PHY control register.
> >
> >Additionally we also need to access IPSS reset and Intr clear regi
On Thu, Dec 02, 2010 at 10:22:11AM +0530, Gupta, Ajay Kumar wrote:
> We would need control register apis for accessing USB PHY control
> , IPSS reset and interrupt clear register. This would require to
> add three different function pointer and that would mostly be
> custom to AM35x. Will that be
> > We would need control register apis for accessing USB PHY control
> > , IPSS reset and interrupt clear register. This would require to
> > add three different function pointer and that would mostly be
> > custom to AM35x. Will that be acceptable from musb perspective ?
>
> why don't you add a
On Wed, 2010-12-01 at 17:38 +0530, Gupta, Ajay Kumar wrote:
> > >> Tony ? Do you ack the usage of that header ?
> > >
> > >NAK. Drivers should not mess with the control registers directly.
> > >
> > >Instead, the following should be done in the platform init code:
> > >
> > >$ grep -r omap_ctrl_rea
> >> Tony ? Do you ack the usage of that header ?
> >
> >NAK. Drivers should not mess with the control registers directly.
> >
> >Instead, the following should be done in the platform init code:
> >
> >$ grep -r omap_ctrl_read drivers/usb
> >drivers/usb/musb/am35x.c: devconf2 =
> omap_ctrl_re
On Tue, Nov 30, 2010 at 10:30:10AM -0800, Tony Lindgren wrote:
* Felipe Balbi [101122 02:12]:
Hi,
On Mon, Nov 22, 2010 at 02:22:40PM +0530, Ajay Kumar Gupta wrote:
>Fixes compilation error as control.h APIs are not available to
>drivers/usb/musb/am35x.c file. Earlier it was getting in
* Felipe Balbi [101122 02:12]:
> Hi,
>
> On Mon, Nov 22, 2010 at 02:22:40PM +0530, Ajay Kumar Gupta wrote:
> >Fixes compilation error as control.h APIs are not available to
> >drivers/usb/musb/am35x.c file. Earlier it was getting included
> >from but now moved
Hi,
On Mon, Nov 22, 2010 at 02:22:40PM +0530, Ajay Kumar Gupta wrote:
Fixes compilation error as control.h APIs are not available to
drivers/usb/musb/am35x.c file. Earlier it was getting included
from but now moved to new location by another
pacth.
Signed-off-by: Ajay Kumar Gupta
Tony ? Do
Fixes compilation error as control.h APIs are not available to
drivers/usb/musb/am35x.c file. Earlier it was getting included
from but now moved to new location by another
pacth.
Signed-off-by: Ajay Kumar Gupta
---
Patch created against latest Linus's tree (v2.6.37-rc3)
arch/arm/plat
From: Subramaniam C.A
Added defines to avoid compilation error.
Signed-off-by: Subramaniam C.A
Acked-by: Felipe Balbi
Signed-off-by: Tony Lindgren
---
arch/arm/plat-omap/include/plat/i2c.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/arm/plat-omap/include
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Branch in linux-omap: devel-omap-misc
Initial commit ID (Likely to change): 6ce3fc011cdd5b7eb72d0cacb236bbfa51f17dad
PatchWorks
http://patchwork.kernel.org/patch/127371/
Git (Likely to change, and takes a while to get m
Hi Felipe,
> -Original Message-
> From: Felipe Balbi [mailto:felipe.ba...@nokia.com]
> Sent: Tuesday, August 24, 2010 1:49 PM
> To: C.A, Subramaniam
> Cc: linux-omap@vger.kernel.org; Gadiyar, Anand; t...@atomide.com
> Subject: Re: [PATCH]omap: i2c: Avoid compilation er
On Tue, Aug 24, 2010 at 07:14:30PM +0200, ext C.A, Subramaniam wrote:
From e3c3ee9317850b2b26e02680a0c976d3c75febab Mon Sep 17 00:00:00 2001
From: Subramaniam C.A
Date: Tue, 24 Aug 2010 12:02:28 -0500
Subject: [PATCH] omap: i2c: Avoid compilation error in case the header is
included multiple
>From e3c3ee9317850b2b26e02680a0c976d3c75febab Mon Sep 17 00:00:00 2001
From: Subramaniam C.A
Date: Tue, 24 Aug 2010 12:02:28 -0500
Subject: [PATCH] omap: i2c: Avoid compilation error in case the header is
included multiple times.
Added defines to avoid compilation error.
Signed-off
On Sat, Jul 10, 2010 at 1:48 AM, Rene Sapiens wrote:
> This patch fix a compilation error in uuid_hex_to_bin
> due to the patch "simplify and clean up"
>
> Signed-off-by: Rene Sapiens
Oh, previous version of patch was sent. Thanks for fix.
ACK.
> ---
> dri
This patch fix a compilation error in uuid_hex_to_bin
due to the patch "simplify and clean up"
Signed-off-by: Rene Sapiens
---
drivers/staging/tidspbridge/gen/uuidutil.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
mode change 100644 => 100755 drivers/staging/ti
Charulatha V writes:
> On 'origin/pm-wip/hwmods-omap4' branch, fix the following
> compilation error:
>
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c:218:
> error: 'omap34xx_sr1_hwmod' undeclared here (not in a function)
> arch/arm/mach-omap2/oma
On 'origin/pm-wip/hwmods-omap4' branch, fix the following
compilation error:
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c:218:
error: 'omap34xx_sr1_hwmod' undeclared here (not in a function)
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c:219:
error: 'omap34xx_s
Ranjith Lohithakshan writes:
> On Thu, 29-Apr-10 3:00 AM +0530, Kevin Hilman wrote:
>> Ranjith Lohithakshan writes:
>>
>>> Currently on PM branch, compilation fails when cpufreq is disabled
>>>
>>> arch/arm/mach-omap2/clock3xxx_data.c: In function 'omap3xxx_clk_init':
>>> arch/arm/mach-omap2/cl
On Thu, 29-Apr-10 3:00 AM +0530, Kevin Hilman wrote:
> Ranjith Lohithakshan writes:
>
>> Currently on PM branch, compilation fails when cpufreq is disabled
>>
>> arch/arm/mach-omap2/clock3xxx_data.c: In function 'omap3xxx_clk_init':
>> arch/arm/mach-omap2/clock3xxx_data.c:3563: error: 'struct c
Ranjith Lohithakshan writes:
> Currently on PM branch, compilation fails when cpufreq is disabled
>
> arch/arm/mach-omap2/clock3xxx_data.c: In function 'omap3xxx_clk_init':
> arch/arm/mach-omap2/clock3xxx_data.c:3563: error: 'struct clk_functions'
> has no member named 'clk_init_cpufreq_table'
>
Currently on PM branch, compilation fails when cpufreq is disabled
arch/arm/mach-omap2/clock3xxx_data.c: In function 'omap3xxx_clk_init':
arch/arm/mach-omap2/clock3xxx_data.c:3563: error: 'struct clk_functions'
has no member named 'clk_init_cpufreq_table'
arch/arm/mach-omap2/clock3xxx_data.c:3564:
Tony Lindgren writes:
> * Varadarajan, Charulatha [100317 08:09]:
>> In "origin/pm-wip/hwmods" branch, using "omap_3430sdp_defconfig" or
>> "omap3_defconfig", results in the following error.
>> Anyone working on this?
>>
>> drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' b
* Varadarajan, Charulatha [100317 08:09]:
> In "origin/pm-wip/hwmods" branch, using "omap_3430sdp_defconfig" or
> "omap3_defconfig", results in the following error.
> Anyone working on this?
>
> drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do'
> drivers/usb/musb/o
In "origin/pm-wip/hwmods" branch, using "omap_3430sdp_defconfig" or
"omap3_defconfig", results in the following error.
Anyone working on this?
drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do'
drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before
Op 12 feb 2010, om 13:20 heeft Gary Thomas het volgende geschreven:
> On 02/12/2010 03:13 AM, Niamathullah sharief wrote:
>> Hello,
>> can anyone tell me while compilaing "dbus-1.2.20" i am getting the
>> folllowing error
>> "checking for XML_ParserCreate_MM in -lexpat... no
>> configure: error:
On 02/12/2010 03:13 AM, Niamathullah sharief wrote:
Hello,
can anyone tell me while compilaing "dbus-1.2.20" i am getting the
folllowing error
"checking for XML_ParserCreate_MM in -lexpat... no
configure: error: Could not find expat.h, check config.log for failed attempts"
what is wrong?what i
Hello,
can anyone tell me while compilaing "dbus-1.2.20" i am getting the
folllowing error
"checking for XML_ParserCreate_MM in -lexpat... no
configure: error: Could not find expat.h, check config.log for failed attempts"
what is wrong?what i should install?i installed libexpat also. still i
get t
From: Tomi Valkeinen [tomi.valkei...@nokia.com]
Sent: Thursday, June 04, 2009 1:59 AM
To: Venkatesh, Subbu
Cc: Shah, Hardik; linux-omap@vger.kernel.org; Mande, Nikhil; Castaneda
Gonzalez, Axel; Miesen, Sharon
Subject: Re: DSS2: Compilation Error on Git tree
http://www.bat.org
On Wed, 2009-06-03 at 16:07 +0200, ext Venkatesh, Subbu wrote:
> Hi Tomi,
> I did git pull to update my tree, later compiling code for LDP, I am getting
> compilation error as show below. I see that I am missing declaration of
> struct omap_dss_display_config in display.h fil
Hi Tomi,
I did git pull to update my tree, later compiling code for LDP, I am getting
compilation error as show below. I see that I am missing declaration of
struct omap_dss_display_config in display.h file, could you please comment on
it...
arch/arm/mach-omap2/board-ldp.c:368: warning
On Fri, Jan 23, 2009 at 02:39:37AM -0800, David Brownell wrote:
> On Friday 23 January 2009, Felipe Balbi wrote:
> > > --- a/drivers/usb/musb/Kconfig
> > > +++ b/drivers/usb/musb/Kconfig
> > > @@ -11,6 +11,7 @@ config USB_MUSB_HDRC
> > > depends on (USB || USB_GADGET) && HAVE_CLK
> > >
On Friday 23 January 2009, Felipe Balbi wrote:
> > --- a/drivers/usb/musb/Kconfig
> > +++ b/drivers/usb/musb/Kconfig
> > @@ -11,6 +11,7 @@ config USB_MUSB_HDRC
> > depends on (USB || USB_GADGET) && HAVE_CLK
> > depends on !SUPERH
> > select TWL4030_USB if MACH_OMAP_3430SDP
> > +
On Wed, Jan 07, 2009 at 04:44:06PM +0530, Ajay Kumar Gupta wrote:
> Fixes the compilation error while musb is selected for OMAP35x EVM and
> twl4030 phy is not selected and thus USB_OTG_UTILS is also not defined.
> This causes below compilation error,
>
> drivers/built-in
Latest linux-omap#master (commit c699464bd) doesn't compile with
n800_defconfig:
arch/arm/mach-omap2/board-n800-bt.c: In function 'n800_bt_init':
arch/arm/mach-omap2/board-n800-bt.c:36: error: 'OMAP_TAG_NOKIA_BT' undeclared
(first use in this function)
arch/arm/mach-omap2/board-n800-bt.c:36: erro
Fixes the compilation error while musb is selected for OMAP35x EVM and
twl4030 phy is not selected and thus USB_OTG_UTILS is also not defined.
This causes below compilation error,
drivers/built-in.o: In function `musb_platform_init':
hid-quirks.c:(.init.text+0x4244): undefined referen
66 matches
Mail list logo
