From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ahci: imx: add namespace for register enums
Date: Fri, 2 May 2014 11:42:32 -0400 [thread overview]
Message-ID: <20140502154232.GI10204@htj.dyndns.org> (raw)
In-Reply-To: <1397803466-28411-2-git-send-email-shawn.guo@freescale.com>
On Fri, Apr 18, 2014 at 02:44:25PM +0800, Shawn Guo wrote:
> Update register enums a little bit to add proper namespace prefix, and
> have the names match i.MX reference manual.
>
> Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
> ---
> drivers/ata/ahci_imx.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/ata/ahci_imx.c b/drivers/ata/ahci_imx.c
> index 497c7ab..009a074 100644
> --- a/drivers/ata/ahci_imx.c
> +++ b/drivers/ata/ahci_imx.c
> @@ -29,9 +29,9 @@
> #include "ahci.h"
>
> enum {
> - PORT_PHY_CTL = 0x178, /* Port0 PHY Control */
> - PORT_PHY_CTL_PDDQ_LOC = 0x100000, /* PORT_PHY_CTL bits */
> - HOST_TIMER1MS = 0xe0, /* Timer 1-ms */
> + IMX_SATA_TIMER1MS = 0x00e0,
> + IMX_SATA_P0PHYCR = 0x0178,
P0PHYCR isn't really readily dechipherable to "Port0 PHY Control".
Probably keeping the comment is better? Also, constant names don't
necessarily have to be exactly the same as hardware manuals. If
easier to understand and map back (via comment or whatever), using
more humanly-readable names is completely fine. Also, maybe IMX_SATA_
is a bit too long for prefix?
Thanks.
--
tejun
next prev parent reply other threads:[~2014-05-02 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 6:44 [PATCH v2 0/2] ahci: imx: software workaround for phy reset issue Shawn Guo
2014-04-18 6:44 ` [PATCH v2 1/2] ahci: imx: add namespace for register enums Shawn Guo
2014-05-02 15:42 ` Tejun Heo [this message]
2014-04-18 6:44 ` [PATCH v2 2/2] ahci: imx: software workaround for phy reset issue in resume Shawn Guo
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=20140502154232.GI10204@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).