public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 10/20] aic94xx: aic94xx_reg.c Register access
Date: Mon, 12 Sep 2005 13:04:16 -0400	[thread overview]
Message-ID: <4325B510.4010205@adaptec.com> (raw)
In-Reply-To: <20050911102649.GA2742@elf.ucw.cz>

On 09/11/05 06:26, Pavel Machek wrote:
> Hi!
> 
> 
>>+/* We know that the register wanted is in the range
>>+ * of the sliding window.
>>+ */
>>+#define ASD_READ_SW(ww, type, ord)                                     \
>>+static inline type asd_read_##ww##_##ord (struct asd_ha_struct *asd_ha,\
>>+					  u32 reg)                     \
>>+{                                                                      \
>>+	struct asd_ha_addrspace *io_handle = &asd_ha->io_handle[0];    \
>>+	u32 map_offs=(reg - io_handle-> ww##_base )+asd_mem_offs_##ww ();\
>>+	return asd_read_##ord (asd_ha, (unsigned long) map_offs);      \
>>+}
>>+
>>+#define ASD_WRITE_SW(ww, type, ord)                                    \
>>+static inline void asd_write_##ww##_##ord (struct asd_ha_struct *asd_ha,\
>>+				  u32 reg, type val)                   \
>>+{                                                                      \
>>+	struct asd_ha_addrspace *io_handle = &asd_ha->io_handle[0];    \
>>+	u32 map_offs=(reg - io_handle-> ww##_base )+asd_mem_offs_##ww ();\
>>+	asd_write_##ord (asd_ha, (unsigned long) map_offs, val);       \
>>+}
>>+
>>+ASD_READ_SW(swa, u8,  byte);
>>+ASD_READ_SW(swa, u16, word);
>>+ASD_READ_SW(swa, u32, dword);
>>+
>>+ASD_READ_SW(swb, u8,  byte);
>>+ASD_READ_SW(swb, u16, word);
>>+ASD_READ_SW(swb, u32, dword);
>>+
>>+ASD_READ_SW(swc, u8,  byte);
>>+ASD_READ_SW(swc, u16, word);
>>+ASD_READ_SW(swc, u32, dword);
>>+
>>+ASD_WRITE_SW(swa, u8,  byte);
>>+ASD_WRITE_SW(swa, u16, word);
>>+ASD_WRITE_SW(swa, u32, dword);
>>+
>>+ASD_WRITE_SW(swb, u8,  byte);
>>+ASD_WRITE_SW(swb, u16, word);
>>+ASD_WRITE_SW(swb, u32, dword);
>>+
>>+ASD_WRITE_SW(swc, u8,  byte);
>>+ASD_WRITE_SW(swc, u16, word);
>>+ASD_WRITE_SW(swc, u32, dword);
> 
> 
> This is certainly nice entry into "best abuse of macros" contest. Do
> you really need all those inline functions?

Hehehee, you may be right Pavel.  I just wanted to minimize bugs which
could be introduced by syntax errors (not necessarily compilation errors).

Yes, reading byte/word/dword from HA memory is needed.

>>+static void __asd_write_reg_byte(struct asd_ha_struct *asd_ha, u32 reg, u8 val)
>>+{
>>+	struct asd_ha_addrspace *io_handle=&asd_ha->io_handle[0];
>>+	BUG_ON(reg >= 0xC0000000 || reg < ALL_BASE_ADDR);
> 
> 
> Will this work correctly with 2GB/2GB split kernels?

"reg" is an address in the host adapter's memory.  Will this matter?

	Luben



      reply	other threads:[~2005-09-12 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:34 [PATCH 2.6.13 10/20] aic94xx: aic94xx_reg.c Register access Luben Tuikov
2005-09-11 10:26 ` Pavel Machek
2005-09-12 17:04   ` Luben Tuikov [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=4325B510.4010205@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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