From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev@lists.infradead.org
Subject: [PATCH] ssb: cc: prepare clockmode support for cores rev 10+
Date: Wed, 27 Apr 2011 23:37:49 +0200 [thread overview]
Message-ID: <1303940269.31395.6.camel@maggie> (raw)
In-Reply-To: <BANLkTikJj4vA6obyCkqwsiG+Ha7aOnz=SQ@mail.gmail.com>
On Wed, 2011-04-27 at 22:52 +0200, Rafa? Mi?ecki wrote:
> 2011/4/27 Michael B?sch <m@bues.ch>:
> >> + /* udelay(150); TODO: not available in early init */
> >
> > udelay() should be available at this point. Are you confusing it with
> > msleep(), which is not available that early?
>
> I had no idea about this difference, thanks.
>
> However I still think about initializing ChipCommon later, to let it
> *sleep* and no to delay boot process. Should this be fine? Or are
> there some important reasons to init ChipCommon early?
I don't think it matters it all, if the boot process takes
150 microseconds longer or not. So I'd rather not change it for
no good reason.
This new 0.00015 seconds (150 us) delay in chipcommon seems perfectly
fine.
Even a few MMIO bus accesses will take longer than this tiny delay.
And there are thousands of MMIO accesses on bootup.
So it will hardly be measureable.
--
Greetings Michael.
prev parent reply other threads:[~2011-04-27 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:40 [PATCH] ssb: cc: prepare clockmode support for cores rev 10+ Rafał Miłecki
2011-04-27 17:58 ` Larry Finger
2011-04-27 20:41 ` Michael Büsch
2011-04-27 20:52 ` Rafał Miłecki
2011-04-27 21:37 ` Michael Büsch [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=1303940269.31395.6.camel@maggie \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=zajec5@gmail.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