From: Nikita Kiryanov <nikita@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 07/11] MX6: use macro building for MX6Q/MX6DL iomux regs
Date: Thu, 10 Apr 2014 17:51:48 +0300 [thread overview]
Message-ID: <5346B004.5000308@compulab.co.il> (raw)
In-Reply-To: <5346A5F4.3020308@compulab.co.il>
On 04/10/2014 05:08 PM, Nikita Kiryanov wrote:
> On 04/09/2014 06:46 PM, Tim Harvey wrote:
>> On Wed, Apr 9, 2014 at 7:57 AM, Nikita Kiryanov
>> <nikita@compulab.co.il> wrote:
>>> Hi Tim,
>>>
>>>
>>> On 04/03/2014 09:01 AM, Tim Harvey wrote:
>>>>
>>>> This is an attempt at using a macro to allow mx6dl-ddr.h and
>>>> mx6q-ddr.h registers to be used together which is needed for an SPL
>>>> bootloader
>>>> that can run on either CPU's and must configure MMDC iomux dynamically.
>>>>
>>>> I am trying to come up with a solution similar to Eric's approach
>>>> with the
>>>> similar issue regarding IMX pinmux but this approach is broken in that
>>>> imximage
>>>> will choke on the cfgtmp file due to the fact that the pre-processor
>>>> won't
>>>> use the enum's as it did the #defines. I'm looking for some positive
>>>> suggestions here or perhaps someone else can come up with a solution
>>>> for
>>>> this
>>>> particular issue which I haven't been able to resolve.
>>>
>>>
>>> Why can't you just rename the register name #defines without enclosing
>>> them in an anonymous enum? Then they could coexist and will be usable
>>> by imximage.
>>>
>>> --
>>> Regards,
>>> Nikita.
>>
>> Nikita,
>>
>> The cfg files are currently all written to use the IOMUX register
>> names as MX6_ (no Q vs DL) so that a single cfg file can be used for a
>> build-time configuration of IMX6Q or IMX6DL.
>
> OK now I understand. It seems to me that you only have this problem
> because you are using these address #defines as values for
> mx6_mmdc_ioregs structs to define a register mapping. You can
> also define this mapping by using a struct template that matches the
> register layout and a base address, both of which change between CPU
> types.
>
> You can find an example of this in the Wandboard SPL implementation.
Here I'm referring to the file arch/arm/include/asm/arch-mx6/mx6_ddr_regs.h
(which I'm guessing you may have already seen based on your comment on
patch 11...)
> It's not in mainline ATM so you'll have to download their BSP.
> The template + base addr method also doesn't use up additional memory
> to define this layout, which is a point in its favor.
>
>>
>> Regards,
>>
>> Tim
>>
>
>
--
Regards,
Nikita.
next prev parent reply other threads:[~2014-04-10 14:51 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:01 [U-Boot] [PATCH 00/11] MX6: SPL NAND support Tim Harvey
2014-04-03 6:01 ` [U-Boot] [PATCH 01/11] SPL: NAND: remove CONFIG_SYS_NAND_PAGE_SIZE Tim Harvey
2014-04-04 2:33 ` Masahiro Yamada
2014-04-09 14:55 ` Nikita Kiryanov
2014-04-14 11:38 ` Stefano Babic
2014-04-17 14:18 ` Tim Harvey
2014-04-18 22:23 ` Scott Wood
2014-04-03 6:01 ` [U-Boot] [PATCH 02/11] SPL: NAND: add support for mxs nand Tim Harvey
2014-04-14 11:38 ` Stefano Babic
2014-04-03 6:01 ` [U-Boot] [PATCH 03/11] MX6: provide linker script for SPL Tim Harvey
2014-04-09 14:55 ` Nikita Kiryanov
2014-04-14 12:02 ` Stefano Babic
2014-04-17 6:27 ` Tim Harvey
2014-04-18 21:10 ` Otavio Salvador
2014-04-03 6:01 ` [U-Boot] [PATCH 04/11] MX6: add common SPL configuration Tim Harvey
2014-04-09 14:55 ` Nikita Kiryanov
2014-04-09 15:32 ` Tim Harvey
2014-04-10 14:37 ` Nikita Kiryanov
2014-04-10 21:04 ` Scott Wood
2014-04-03 6:01 ` [U-Boot] [PATCH 05/11] MX6: add boot device support SPL Tim Harvey
2014-04-14 12:27 ` Stefano Babic
2014-04-17 6:16 ` Tim Harvey
2014-04-17 8:59 ` Stefano Babic
2014-04-03 6:01 ` [U-Boot] [PATCH 06/11] MX6: add struct for sharing data between SPL and uboot Tim Harvey
2014-04-09 14:55 ` Nikita Kiryanov
2014-04-14 12:35 ` Stefano Babic
2014-04-17 6:07 ` Tim Harvey
2014-04-17 9:30 ` Stefano Babic
2014-04-17 11:22 ` Igor Grinberg
2014-04-17 11:44 ` Stefano Babic
2014-04-18 6:35 ` Tim Harvey
2014-04-20 7:52 ` Igor Grinberg
2014-04-21 18:28 ` Tim Harvey
2014-04-22 7:44 ` Igor Grinberg
2014-04-03 6:01 ` [U-Boot] [PATCH 07/11] MX6: use macro building for MX6Q/MX6DL iomux regs Tim Harvey
2014-04-09 14:57 ` Nikita Kiryanov
2014-04-09 15:46 ` Tim Harvey
2014-04-10 14:08 ` Nikita Kiryanov
2014-04-10 14:51 ` Nikita Kiryanov [this message]
2014-04-11 5:23 ` Tim Harvey
2014-04-23 17:07 ` Stefano Babic
2014-04-23 19:00 ` Eric Nelson
2014-04-24 7:07 ` Igor Grinberg
2014-04-24 5:21 ` Tim Harvey
2014-04-23 15:30 ` Stefano Babic
2014-04-03 6:01 ` [U-Boot] [PATCH 08/11] MX6: add mmdc configuration for MX6Q/MX6DL Tim Harvey
2014-04-03 6:01 ` [U-Boot] [PATCH 09/11] IMX: add additional function for pinmux using an array Tim Harvey
2014-04-09 14:56 ` Nikita Kiryanov
2014-04-09 15:40 ` Tim Harvey
2014-04-10 14:41 ` Nikita Kiryanov
2014-04-23 5:03 ` Tim Harvey
2014-04-03 6:01 ` [U-Boot] [PATCH 10/11] ventana: auto-configure for IMX6Q vs IMX6DL Tim Harvey
2014-04-23 17:31 ` Stefano Babic
2014-04-24 5:04 ` Tim Harvey
2014-04-03 6:01 ` [U-Boot] [PATCH 11/11] ventana: switch to SPL Tim Harvey
2014-04-03 18:52 ` Tim Harvey
2014-04-23 18:03 ` Stefano Babic
2014-04-24 8:06 ` Tim Harvey
2014-04-24 8:18 ` Stefano Babic
2014-04-24 8:22 ` Stefan Roese
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=5346B004.5000308@compulab.co.il \
--to=nikita@compulab.co.il \
--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