From: Nishanth Menon <nm@ti.com>
To: "Kahn, Gery" <geryk@ti.com>
Cc: mohamed@e-consystems.com,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
OMAP-KML <linux-omap@vger.kernel.org>
Subject: Re: How to enable dvfs in omap.
Date: Sun, 13 Feb 2011 21:13:42 +0530 [thread overview]
Message-ID: <4D57FC2E.3090400@ti.com> (raw)
In-Reply-To: <AANLkTin3MZNATS4XuY5qU3f7C=f9KogV+1A2_vZTxF-_@mail.gmail.com>
Kahn, Gery wrote, on 02/13/2011 08:39 PM:
> Thank you for the git.
> The pull worked good without problem.
>
> During compilation i found such problem:
>
> arch/arm/plat-omap/cpu-omap.c:142: error: 'struct
' has no
> member named 'loops_per_jiffy'
>
> Is there solution for the issue?
>
Aaah.. one possibility is that you may have disabled CONFIG_SMP in your
defconfig
well.. baselined to 2.6.38-rc4, it builds fine for me. I am using the
omap2plus_defconfig
http://pastebin.mozilla.org/1055575 (for output from savedefconfig)
Looking at the source, arch/arm/include/asm/cpu.h
loops_per_jiffy is under CONFIG_SMP and since the omap2plus_defconfig
builds for OMAP4 as well by default, I am guessing this bug was not
immediately visible.. You may want to comment on the appropriate patch
from Vishwa for this. might as well remove the loops_per_jiffy outside
the CONFIG_SMP
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-02-13 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 10:49 How to enable dvfs in omap Mohamed Thalib H
2011-02-12 10:57 ` Santosh Shilimkar
2011-02-12 11:12 ` Mohamed Thalib H
2011-02-12 11:51 ` Nishanth Menon
2011-02-12 12:21 ` Mohamed Thalib H
2011-02-13 15:09 ` Kahn, Gery
2011-02-13 15:43 ` Nishanth Menon [this message]
2011-02-14 9:06 ` Kahn, Gery
2011-02-14 9:21 ` Menon, Nishanth
2011-02-13 15:38 ` Koen Kooi
2011-02-13 15:47 ` Nishanth Menon
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=4D57FC2E.3090400@ti.com \
--to=nm@ti.com \
--cc=geryk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mohamed@e-consystems.com \
--cc=santosh.shilimkar@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: 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.