From: Kalle Jokiniemi <ext-kalle.jokiniemi@nokia.com>
To: ext Rajendra Nayak <rnayak@ti.com>
Cc: "'\"Högander\" Jouni'" <jouni.hogander@nokia.com>,
"'Peter 'p2' De Schrijver'" <peter.de-schrijver@nokia.com>,
linux-omap@vger.kernel.org
Subject: RE: [PATCH 00/11] OMAP3 CPUidle patches
Date: Mon, 07 Jul 2008 12:38:40 +0300 [thread overview]
Message-ID: <1215423520.6048.16.camel@kj-ubuntu> (raw)
In-Reply-To: <011601c8ddba$c4031110$68bf18ac@ent.ti.com>
On pe, 2008-07-04 at 15:15 +0530, ext Rajendra Nayak wrote:
...
> > ext Högander Jouni <jouni.hogander@nokia.com> writes:
...
> >
> > So Rajendra sent his uImage and it works quite ok what comes to off
> > mode on my sdp board. I still see problems with serial console (slow)
> > and on boot I need to generate manually interrupts to get it to
> > boot. Otherwise board hangs at this point:
>
> Yes, I noticed this as well. It takes quite long to bootup if you don't
> generate UART interrupts.
> After bootup once RET/OFF is hit, it takes a few hits to come out of it
> as IO wakeup is missing.
Jouni had a theory that the ethernet device could cause this slowness
trouble in the startup, so I investigated the matter a little further.
By enabling the debug prints in the ethernet chip driver,
diff --git a/drivers/net/smc91x.c b/drivers/net/smc91x.c
index 776c81d..7d1eead 100644
--- a/drivers/net/smc91x.c
+++ b/drivers/net/smc91x.c
@@ -62,7 +62,7 @@ static const char version[] =
/* Debugging level */
#ifndef SMC_DEBUG
-#define SMC_DEBUG 0
+#define SMC_DEBUG 1
#endif
I was able to see, that we get lots of RX overrun interrupts with
cpu_idle, meaning that incoming stuff is not getting processed. By
generating UART interrupts, I we probably can also catch more network RX
interrupts and this helps the bootup go faster. With cpu_idle disabled,
there were no RX overruns.
I'll try to see if this can be fixed somehow.
>
> >
> > eth0: link up
> > Sending DHCP requests ., OK
> > IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.2.101
> > IP-Config: Complete:
> > device=eth0, addr=192.168.2.101, mask=255.255.255.0,
> > gw=192.168.2.1,
> > host=192.168.2.101, domain=ntc.nokia.com, nis-domain=(none),
> > bootserver=0.0.0.0, rootserver=172.22.146.197, rootpath=
> > Looking up port of RPC 100003/2 on 172.22.146.197
> > Looking up port of RPC 100005/1 on 172.22.146.197
> > VFS: Mounted root (nfs filesystem).
> > Freeing init memory: 108K
> >
> > Rajendra, are you still using .config file you sent to me? Are all the
> > changes in your tree available in l-o list.
>
> Yes, all the changes are part of the 11 patch set + 1 rework fixes patch I sent.
> To debug further, can you put a few prints in omap3_enter_idle and omap3_enter_idle_bm
> to see what states are selected by the menu gov.
> We will then know if CORE RET/OFF is attempted but not achieved due to some reason, or
> never attempted altogether.
My setup does not seem to go beyond C2 state, btw. So I'll need to debug
that also a bit. The above-mentioned patches are applied.
Br, Kalle
...
--
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
next prev parent reply other threads:[~2008-07-07 9:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 14:16 [PATCH 00/11] OMAP3 CPUidle patches Rajendra Nayak
2008-07-02 13:11 ` Peter 'p2' De Schrijver
2008-07-02 13:37 ` Rajendra Nayak
2008-07-02 15:42 ` Peter 'p2' De Schrijver
2008-07-03 8:39 ` Rajendra Nayak
2008-07-03 12:44 ` Peter 'p2' De Schrijver
2008-07-04 7:26 ` Högander Jouni
2008-07-04 9:32 ` Högander Jouni
2008-07-04 9:45 ` Koen Kooi
2008-07-04 9:45 ` Rajendra Nayak
2008-07-04 9:55 ` Högander Jouni
2008-07-04 11:08 ` Högander Jouni
2008-07-07 9:38 ` Kalle Jokiniemi [this message]
2008-07-07 9:56 ` Högander Jouni
2008-07-07 13:58 ` Premi, Sanjeev
2008-07-07 22:25 ` Woodruff, Richard
2008-07-08 6:15 ` Högander Jouni
2008-07-08 12:11 ` Woodruff, Richard
2008-07-08 13:41 ` Högander Jouni
2008-07-08 13:52 ` Woodruff, Richard
2008-07-09 6:48 ` Högander Jouni
2008-07-09 16:31 ` Woodruff, Richard
2008-07-04 11:05 ` Peter 'p2' De Schrijver
2008-07-04 11:39 ` Peter 'p2' De Schrijver
2008-07-03 5:57 ` Högander Jouni
2008-07-03 10:20 ` Rajendra Nayak
2008-07-15 13:20 ` Rajendra Nayak
2008-07-18 13:18 ` [PATCH 00/11] OMAP3 CPUidle patches - ver 2 Rajendra Nayak
[not found] ` <002f01c8f7c5$0790fea0$LocalHost@wipultra1382>
2008-08-06 13:12 ` Rajendra Nayak
2008-08-07 9:54 ` Kalle Jokiniemi
2008-08-12 12:40 ` Högander Jouni
2008-08-13 5:57 ` Rajendra Nayak
2008-08-13 6:06 ` Rajendra Nayak
2008-08-13 6:55 ` Högander Jouni
2008-08-13 12:35 ` Woodruff, Richard
2008-08-13 13:12 ` Högander Jouni
2008-08-14 5:25 ` Rajendra Nayak
2008-08-19 19:08 ` Paul Walmsley
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=1215423520.6048.16.camel@kj-ubuntu \
--to=ext-kalle.jokiniemi@nokia.com \
--cc=jouni.hogander@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.de-schrijver@nokia.com \
--cc=rnayak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox