From: Tony Lindgren <tony@atomide.com>
To: balrogg@gmail.com, David Brownell <david-b@pacbell.net>
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: Ensure correct GPIO registers access width.
Date: Thu, 21 Dec 2006 15:42:14 -0800 [thread overview]
Message-ID: <20061221234214.GQ10399@atomide.com> (raw)
In-Reply-To: <11645731203663-git-send-email-balrog@zabor.org>
* Andrzej Zaborowski <balrog@zabor.org> [061126 10:31]:
> [Note that this probably gives no gain of any kind. I don't know
> if it should be applied.]
>
> Use 16-bit or 32-bit reads and writes to access GPIO registers in
> different banks according to their widths. Currently all accesses
> in gpio.c were 32-bits.
Let's wait on this a bit. I'd rather have omap1 and omap2 register
their own handlers, so let's plan on doing this along with the generic
gpio framework changes that Dave recently posted to LKML.
Regards,
Tony
prev parent reply other threads:[~2006-12-21 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 20:32 [PATCH] ARM: OMAP: Ensure correct GPIO registers access width Andrzej Zaborowski
2006-12-21 23:42 ` Tony Lindgren [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=20061221234214.GQ10399@atomide.com \
--to=tony@atomide.com \
--cc=balrogg@gmail.com \
--cc=david-b@pacbell.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox