From: Patrick Gefre <pfg@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, davidm@napali.hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Altix updates
Date: Tue, 20 Jan 2004 16:23:50 -0600 [thread overview]
Message-ID: <400DAA76.2080103@sgi.com> (raw)
In-Reply-To: <20040120202132.A20668@infradead.org>
Christoph Hellwig wrote:
>On Tue, Jan 20, 2004 at 02:12:47PM -0600, Patrick Gefre wrote:
>
>
>>Guess I don't understand your point. Do you want us to create separate
>>functions for soft-struct and bridge address
>>and TIO and non-TIO - 4 functions for each register access, rather than 1 ?
>>
>>
>
>The right fix would be to only have one, and that one would take the
>bridge_t. If you really want to have one that takes the pcibr_soft, too
>make it a small wrapper. But even that would be two and not four, where
>do the other two come from?
>
>
I had one for bridge address/TIO, one for bridge address/nonTIO, one for
soft address/TIO and one for soft address/nonTIO.
I thought that was what you were proposing. In any event, here's how the
basic code looks (leaving out type defs/error checking/
etc) - the wrapper is embedded in the macro - note that we would always
like to use the soft struct because it doesn't cost us a PIO
but in the event that the soft struct is not available the bridge
address must be used:
#define SET_TYPE_AND_PTR(ptr, type, bridge) \
if ( IS_IOADDR(ptr) ) { \
if ( IS_TIO(ptr->id) ) \
type = BT_TIO; \
else \
type = BT_PIC; \
bridge_addr = ptr; \
} else { \
type = ptr->bs_bridge_type; \
bridge_addr = ptr->bs_base; \
}
void *
pcireg_xxx_get(void *ptr)
{
SET_TYPE_AND_PTR(ptr, &type, bridge);
switch (type ) {
case BT_TIO:
return bridge_addr->ti_xxx;
case BT_PIC:
return bridge->addr->pic_xxx;
default:
/* */
}
}
Is this what you are suggesting ??
void *
pcireg_xxx_get(void *ptr)
{
if ( IS_IOADDR(ptr) )
return REAL_pcireg_xxx_get(ptr, IS_TIO(ptr) ? BT_TIO : BT_PIC);
else
return REAL_pcireg_xxx_get(ptr->bs_base, ptr->bs_bridge_type);
}
void *
REAL_pcireg_xxx_get(void *ptr, int type)
{
switch (type ) {
case BT_TIO:
return bridge_addr->ti_xxx;
case BT_PIC:
return bridge->addr->pic_xxx;
default:
/* */
}
}
next prev parent reply other threads:[~2004-01-20 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 21:54 [PATCH 2.6] Altix updates Pat Gefre
2004-01-16 2:34 ` Andrew Morton
2004-01-16 14:41 ` Christoph Hellwig
2004-01-20 17:50 ` Patrick Gefre
2004-01-20 18:08 ` Christoph Hellwig
2004-01-20 20:12 ` Patrick Gefre
2004-01-20 20:21 ` Christoph Hellwig
2004-01-20 22:23 ` Patrick Gefre [this message]
2004-01-20 23:34 ` Christoph Hellwig
2004-01-21 0:23 ` Patrick Gefre
2004-01-21 0:26 ` Christoph Hellwig
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=400DAA76.2080103@sgi.com \
--to=pfg@sgi.com \
--cc=akpm@osdl.org \
--cc=davidm@napali.hpl.hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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