From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 03/15] imx: mx6ul: Update imx registers head file
Date: Sun, 12 Jul 2015 13:50:55 +0200 [thread overview]
Message-ID: <201507121350.55223.marex@denx.de> (raw)
In-Reply-To: <20150712103227.GB16931@shlinux2>
On Sunday, July 12, 2015 at 12:32:28 PM, Peng Fan wrote:
> Hi Marek,
>
> On Sun, Jul 12, 2015 at 12:11:42AM +0200, Marek Vasut wrote:
> >On Saturday, July 11, 2015 at 10:07:11 AM, Peng Fan wrote:
> >> 1. Update imx register base address for i.MX6UL.
> >> 2. Remove duplicated MXS_APBH/GPMI/BCH_BASE.
> >> 3. Remove #ifdef for register addresses that equal to
> >>
> >> "AIPS2_OFF_BASE_ADDR + 0x34000" for different chips.
> >>
> >> 4. According fuse map, complete fuse_bank4_regs.
> >> 5. Move AIPS3_ARB_BASE_ADDR and AIPS3_ARB_END_ADDR out of #ifdef
> >> CONFIG_MX6SX, because we can use runtime check
> >>
> >> Signed-off-by: Peng Fan <Peng.Fan@freescale.com>
> >> ---
> >
> >[...]
> >
> >> @@ -309,11 +311,16 @@
> >>
> >> #define PWM8_BASE_ADDR (AIPS3_ARB_BASE_ADDR + 0xB0000)
> >> #endif
> >>
> >> +/* only for i.MX6SX/UL */
> >> +#define WDOG3_BASE_ADDR (is_cpu_type(MXC_CPU_MX6UL) ? \
> >> + (AIPS2_OFF_BASE_ADDR + 0x64000) : \
> >> + (AIPS3_ARB_BASE_ADDR + 0x88000))
> >> +
> >
> >This might not work if used in assembler.
>
> I did not see any scenario that it will be used in assembler now.
Does that mean we will be fine with adding code which we know might easily
break?
> If we truely need it in assembler, then we can not avoid so many "ifdef"s.
errr ... ifdef __ASSEMBLY__ would suffice here I guess, but to be really smart
about it, I'd say you might want to define something like MX6UL_WDOG3_BASE,
MX6S_WDOG3_BASE and then define WDOG3_BASE_ADDR as (is_cpu_type(...) ?
MX6UL_WDOG3_BASE : MX6S.... ) . Then you could access the WDOG3 from assembler
and from C code with the benefit that from C code, you'd be able to access it
in a bit smoother way. I don't know if there's a way to do it easily in asm
too, sorry.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-07-12 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 8:07 [U-Boot] [PATCH V2 00/15] imx: Add i.MX6UL and basic board support Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 01/15] imx: mx6ul: Add i.MX6UL CPU type Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 02/15] imx: mx6ul: Add pins IOMUX head file Peng Fan
2015-07-11 22:10 ` Marek Vasut
2015-07-12 10:27 ` Peng Fan
2015-07-12 11:39 ` Marek Vasut
2015-07-12 11:53 ` Peng Fan
2015-07-12 14:16 ` Marek Vasut
2015-07-11 8:07 ` [U-Boot] [PATCH V2 03/15] imx: mx6ul: Update imx registers " Peng Fan
2015-07-11 22:11 ` Marek Vasut
2015-07-12 10:32 ` Peng Fan
2015-07-12 11:50 ` Marek Vasut [this message]
2015-07-12 11:55 ` Peng Fan
2015-07-12 14:14 ` Marek Vasut
2015-07-11 8:07 ` [U-Boot] [PATCH V2 04/15] imx: mx6ul Add CONFIG_SYS_CACHELINE_SIZE for i.MX6UL Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 05/15] imx-common: timer: add i.MX6UL support Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 06/15] imx: mx6ul remove errata for i.MX6UL Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 07/15] imx:mx6ul add clock support Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 08/15] imx: mx6ul select SYS_L2CACHE_OFF Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 09/15] imx: mx6ul update soc related settings Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 10/15] imx: mx6 add PAD_CTL_SPEED_LOW for i.MX6SX/UL Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 11/15] mxc: gpio add i.MX6UL support Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 12/15] mx6_common: Fix LOADADDR and SYS_TEXT_BASE for i.MX6UL Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 13/15] imx:mx6ul add dram spl configuration and header file Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 14/15] imx: imx6_spl add mx6ul support Peng Fan
2015-07-11 8:07 ` [U-Boot] [PATCH V2 15/15] imx: mx6ul_14x14_evk add basic board support Peng Fan
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=201507121350.55223.marex@denx.de \
--to=marex@denx.de \
--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