linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Saeed Bishara <saeed@marvell.com>
Subject: Re: [PATCH 06/07] sata_mv: cosmetic renames
Date: Mon, 06 Apr 2009 16:12:01 -0400	[thread overview]
Message-ID: <49DA6211.203@rtr.ca> (raw)
In-Reply-To: <49DA5D30.4000704@pobox.com>

Jeff Garzik wrote:
> Mark Lord wrote:
>> Add _OFS suffix to more of the register offset names,
>> for consistency with the rest of the driver.
>>
>> Also tag the defines for LTMODE and PHY_MODE4 to note
>> that read-after-write is necessary when updating those regs.
>>
>> No code changes here.
>>
>> Signed-off-by: Mark Lord <mlord@pobox.com>
>>
>> --- old/drivers/ata/sata_mv.c    2009-04-06 14:20:53.000000000 -0400
>> +++ new/drivers/ata/sata_mv.c    2009-04-06 15:00:16.000000000 -0400
>> @@ -272,17 +272,17 @@
>>     SATA_FIS_IRQ_CAUSE_OFS    = 0x364,
>>     SATA_FIS_IRQ_AN        = (1 << 9),    /* async notification */
>>
>> -    LTMODE_OFS        = 0x30c,
>> +    LTMODE_OFS        = 0x30c,    /* requires read-after-write */
>>     LTMODE_BIT8        = (1 << 8),    /* unknown, but necessary */
>>
>> -    PHY_MODE3        = 0x310,
>> -    PHY_MODE4        = 0x314,
>> +    PHY_MODE2_OFS        = 0x330,
>> +    PHY_MODE3_OFS        = 0x310,
>> +    PHY_MODE4_OFS        = 0x314,    /* requires read-after-write */
>>     PHY_MODE4_CFG_MASK    = 0x00000003,    /* phy internal config 
>> field */
>>     PHY_MODE4_CFG_VALUE    = 0x00000001,    /* phy internal config 
>> field */
>>     PHY_MODE4_RSVD_ZEROS    = 0x5de3fffa,    /* Gen2e always write 
>> zeros */
>>     PHY_MODE4_RSVD_ONES    = 0x00000005,    /* Gen2e always write ones */
> 
> _OFS suffix is redundant, and not often used in other Linux drivers.
..

Yeah, I agree it's kinda fugly, too.
But that's what was there from the earlier maintainers
(Brett and yourself, I guess), so for now I'm just keeping it consistent.

I might now try patch 08 follow-up to rename all of that stuff,
if you're happy with the series thus far.  Plan is to drop the _OFS stuff,
and also make a bunch of the register prefixes more consistent as well.

Currenly, some regs use MV_ whereas others don't, and some have SATA_
at the start but related registers don't.

Any preferences there?  It's all the same to me.

Cheers

  reply	other threads:[~2009-04-06 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 16:29 [PATCH 01/03] sata_mv: revert SoC irq breakage Mark Lord
2009-04-06 16:30 ` [PATCH 02/03] sata_mv: fix irq mask races Mark Lord
2009-04-06 16:31   ` [PATCH 03/03] sata_mv: replace 0x1f with ATA_PIO4 Mark Lord
2009-04-06 19:22     ` [PATCH 03/03] sata_mv: replace 0x1f with ATA_PIO4 (v2) Mark Lord
2009-04-06 19:24       ` [PATCH 04/07] sata_mv: workaround errata PCI#7 Mark Lord
2009-04-06 19:24         ` [PATCH 05/07] sata_mv: workaround errata SATA#26 Mark Lord
2009-04-06 19:25           ` [PATCH 06/07] sata_mv: cosmetic renames Mark Lord
2009-04-06 19:26             ` [PATCH 07/07] sata_mv: workaround errata SATA#13 Mark Lord
2009-04-06 20:43               ` [PATCH 08/08] sata_mv: shorten register names Mark Lord
2009-04-06 19:51             ` [PATCH 06/07] sata_mv: cosmetic renames Jeff Garzik
2009-04-06 20:12               ` Mark Lord [this message]
2009-04-07  0:16 ` [PATCH 01/03] sata_mv: revert SoC irq breakage Jeff Garzik

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=49DA6211.203@rtr.ca \
    --to=liml@rtr.ca \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=saeed@marvell.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;
as well as URLs for NNTP newsgroup(s).