public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] do the files arch/powerpc/include/asm/fsl_{law, lbc}.h duplicate info?
Date: Mon, 14 Dec 2015 09:59:36 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1512140955320.16791@localhost> (raw)


  quite possibly a silly question but i'm looking at the header files
related to the powerpc local bus local access windows (of which i am
still woefully ignorant), and i see the following in two different
header files under arch/powerpc/include/asm.

                              fsl_law.h:

#define LAW_EN  0x80000000

#define SET_LAW_ENTRY(idx, a, sz, trgt) \
        { .index = idx, .addr = a, .size = sz, .trgt_id = trgt }

#define SET_LAW(a, sz, trgt) \
        { .index = -1, .addr = a, .size = sz, .trgt_id = trgt }

enum law_size {
        LAW_SIZE_4K = 0xb,
        LAW_SIZE_8K,
        LAW_SIZE_16K,
        LAW_SIZE_32K,
        LAW_SIZE_64K,
        LAW_SIZE_128K,
        LAW_SIZE_256K,
        LAW_SIZE_512K,
        LAW_SIZE_1M,
        LAW_SIZE_2M,
        LAW_SIZE_4M,
        LAW_SIZE_8M,
        LAW_SIZE_16M,
        LAW_SIZE_32M,
        LAW_SIZE_64M,
        LAW_SIZE_128M,
        LAW_SIZE_256M,
        LAW_SIZE_512M,
        LAW_SIZE_1G,
        LAW_SIZE_2G,
        LAW_SIZE_4G,
        LAW_SIZE_8G,
        LAW_SIZE_16G,
        LAW_SIZE_32G,
};

                               fsl_lbc.h

#define LBLAWAR_EN                      0x80000000
#define LBLAWAR_4KB                     0x0000000B
#define LBLAWAR_8KB                     0x0000000C
#define LBLAWAR_16KB                    0x0000000D
#define LBLAWAR_32KB                    0x0000000E
#define LBLAWAR_64KB                    0x0000000F
#define LBLAWAR_128KB                   0x00000010
#define LBLAWAR_256KB                   0x00000011
#define LBLAWAR_512KB                   0x00000012
#define LBLAWAR_1MB                     0x00000013
#define LBLAWAR_2MB                     0x00000014
#define LBLAWAR_4MB                     0x00000015
#define LBLAWAR_8MB                     0x00000016
#define LBLAWAR_16MB                    0x00000017
#define LBLAWAR_32MB                    0x00000018
#define LBLAWAR_64MB                    0x00000019
#define LBLAWAR_128MB                   0x0000001A
#define LBLAWAR_256MB                   0x0000001B
#define LBLAWAR_512MB                   0x0000001C
#define LBLAWAR_1GB                     0x0000001D
#define LBLAWAR_2GB                     0x0000001E

  that kind of looks like the same information, just with different
macro names. is there really a different meaning for that content
between those two files?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

                 reply	other threads:[~2015-12-14 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1512140955320.16791@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=u-boot@lists.denx.de \
    /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