From: Timo Teras <timo.teras@solidboot.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Basic N800 support
Date: Wed, 7 Feb 2007 08:10:35 +0200 [thread overview]
Message-ID: <20070207061035.GA10633@mail.solidboot.com> (raw)
In-Reply-To: <000101c74a77$39e94120$c7a3580a@swcenter.sec.samsung.co.kr>
Hi,
On Wed, Feb 07, 2007 at 02:16:58PM +0900, Kyungmin Park wrote:
> Finally it don't need to configure IOBE in omap2_onenand_wait
>
> #if 0
> /* Turn interrupts on */
> syscfg = omap2_onenand_readw(info->onenand.base +
> ONENAND_REG_SYS_CFG1);
> syscfg |= ONENAND_SYS_CFG1_IOBE;
> omap2_onenand_writew(syscfg, info->onenand.base +
> ONENAND_REG_SYS_CFG1);
> #endif
> #if 0
> /* Turn interrupts off */
> syscfg = omap2_onenand_readw(info->onenand.base +
> ONENAND_REG_SYS_CFG1);
> syscfg &= ~ONENAND_SYS_CFG1_IOBE;
> omap2_onenand_writew(syscfg, info->onenand.base +
> ONENAND_REG_SYS_CFG1);
> #endif
Yes, this is not strictly necessery. But we noticed that using polling
instead of interrupts for some operations give slightly better
performance.
Cheers,
Timo
next prev parent reply other threads:[~2007-02-07 6:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 7:55 Basic N800 support Kyungmin Park
2007-01-22 17:12 ` Tony Lindgren
2007-02-06 21:36 ` Tony Lindgren
2007-02-07 5:16 ` Kyungmin Park
2007-02-07 6:10 ` Timo Teras [this message]
2007-03-01 13:45 ` Jarkko Lavinen
2007-03-02 0:44 ` Kyungmin Park
2007-03-02 16:48 ` Jarkko Lavinen
2007-03-04 10:05 ` [PATCH] Move N800 specific OneNand setup to N800 platform file, was: " Dirk Behme
2007-03-07 11:57 ` Tony Lindgren
2007-03-08 1:18 ` Kyungmin Park
2007-03-08 9:34 ` Kyungmin Park
2007-03-09 19:29 ` Jarkko Lavinen
2007-03-29 20:15 ` Tony Lindgren
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=20070207061035.GA10633@mail.solidboot.com \
--to=timo.teras@solidboot.com \
--cc=kmpark@infradead.org \
--cc=linux-omap-open-source@linux.omap.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.