From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] i.mx: i.mx6q: Add the initial support for i.mx6q ARM2 board
Date: Mon, 14 Nov 2011 12:36:09 +0100 [thread overview]
Message-ID: <4EC0FD29.50006@denx.de> (raw)
In-Reply-To: <CAFQ4atR7rvgZ1AA0pLvXRc_i0f-N=rwCKY5sULu1hnf2O-e_ZA@mail.gmail.com>
On 11/14/2011 10:55 AM, Jason Hui wrote:
> On Mon, Nov 14, 2011 at 5:25 PM, Stefano Babic <sbabic@denx.de> wrote:
>> On 11/12/2011 11:36 AM, Jason Liu wrote:
>>> Add the initial support for Freescale i.MX6Q Armadillo2 board
>>> Support: MMC boot from slot 0/1, debug UART(UART4), usdhc.
>>>
>>> Signed-off-by: Jason Liu <jason.hui@linaro.org>
>>
>> Hi Jason,
>>
>> is mx6qarm2 the official Freescale name ?
>
> Yes, this is the official name.
Ok, fine.
>
>>
>>> +#ifdef CONFIG_FSL_ESDHC
>>> +struct fsl_esdhc_cfg usdhc_cfg[2] = {
>>> + {USDHC3_BASE_ADDR, 1},
>>> + {USDHC4_BASE_ADDR, 1},
>>> +};
>>> +
>>> +int board_mmc_getcd(u8 *cd, struct mmc *mmc)
>>> +{
>>> + struct fsl_esdhc_cfg *cfg = (struct fsl_esdhc_cfg *)mmc->priv;
>>> +
>>> + if (cfg->esdhc_base == USDHC3_BASE_ADDR)
>>> + *cd = gpio_get_value(107); /*GPIO6_11*/
>>> + else /* Don't have the CD GPIO pin on board */
>>> + *cd = 0;
>>
>> Is it the logic inverted ? If you return always zero, there is no Card
>> in the slot for the MMC framework and there is no attempt to read it. It
>> is working on USDHC4 ?
>
> The framework flow is as the following. The logic is ok.
>
I know it - this means that in case of USDHC4, card detect is read
directly from the controller ?
>
> As the comments before for Fabio, I will drop the MACH_TYPE setting since i.mx6q
> linux kernel will go device tree and there is no-need for machine type now.
Ok
>
>>
>>> + /* address of boot parameters */
>>> + gd->bd->bi_boot_params = PHYS_SDRAM + 0x100;
>>> +
>>> + /*
>>> + * Need re-initialization again since base is in BSS
>>> + * After relocation, base will be clear to zero.
>>> + */
>>> + imx_iomux_v3_init((void *)IOMUXC_BASE_ADDR);
>>
>> However, this is a trick. As general rule, we must not use BSS before
>> relocation. Is there no other way to do this ?
>
> There is no other way for it since we need uart early before the relocation.
> If you have other way, I really appreciate it.
The two things are not correlated - most IMXs (and other SOCs, too) set
up the multiplexer t0o get the console working. I am asking myself why
do you need that the base address for the iomuxc is dynamic.
void imx_iomux_v3_init(void *iomux_v3_base)
{
base = iomux_v3_base;
}
But then you initialize it with a constant - can iomux_v3_base be set to
a different address ?
Why cannot you use (or get) the base address in the iomuxv3 code from
imx-regs.h ? Or am I missing something ?
>>
>> Ethernet is not yet working, right ? How many Ethernet has this board ?
>
> yes,I will remove the last line. Only the 1Gbit ENET support on this board.
Ok, understood.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-11-14 11:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 10:36 [U-Boot] [PATCH 0/6] i.mx: add the initial i.mx6q core/board support Jason Liu
2011-11-12 10:36 ` [U-Boot] [PATCH 1/6] i.mx: i.mx5: Move some files to imx-common folder Jason Liu
2011-11-14 8:34 ` Stefano Babic
2011-11-14 8:57 ` Jason Hui
2011-11-14 11:28 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 2/6] i.mx: Add the initial support for freescale i.MX6Q processor Jason Liu
2011-11-13 23:11 ` Marek Vasut
2011-11-14 8:47 ` Jason Hui
2011-11-14 10:45 ` Marek Vasut
2011-11-15 10:10 ` Jason Hui
2011-11-15 11:08 ` Stefano Babic
2011-11-14 9:03 ` Stefano Babic
2011-11-14 9:42 ` Jason Hui
2011-11-14 11:49 ` Stefano Babic
2011-11-15 10:18 ` Jason Hui
2011-11-12 10:36 ` [U-Boot] [PATCH 3/6] i.mx: mxc_gpio: add the i.mx6q support Jason Liu
2011-11-14 9:04 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 4/6] i.mx: serial_mxc: " Jason Liu
2011-11-12 10:36 ` [U-Boot] [PATCH 5/6] i.mx: fsl_esdhc: " Jason Liu
2011-11-12 16:35 ` Marek Vasut
2011-11-14 8:37 ` Jason Hui
2011-11-14 10:42 ` Marek Vasut
2011-11-15 9:46 ` Jason Hui
2011-11-15 11:56 ` Stefano Babic
2011-11-16 1:36 ` Jason Hui
2011-11-16 2:24 ` Marek Vasut
2011-11-14 9:06 ` Stefano Babic
2011-11-12 10:36 ` [U-Boot] [PATCH 6/6] i.mx: i.mx6q: Add the initial support for i.mx6q ARM2 board Jason Liu
2011-11-12 19:42 ` Fabio Estevam
2011-11-14 8:59 ` Jason Hui
2011-11-12 20:13 ` Fabio Estevam
2011-11-14 9:10 ` Jason Hui
2011-11-13 7:04 ` Igor Grinberg
2011-11-14 9:13 ` Jason Hui
2011-11-14 9:25 ` Stefano Babic
2011-11-14 9:55 ` Jason Hui
2011-11-14 11:36 ` Stefano Babic [this message]
2011-11-16 11:34 ` Dirk Behme
2011-11-16 12:15 ` Jason Hui
2011-11-12 16:10 ` [U-Boot] [PATCH 0/6] i.mx: add the initial i.mx6q core/board support Dirk Behme
2011-11-14 8:11 ` Jason Hui
2011-11-16 11:56 ` Dirk Behme
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=4EC0FD29.50006@denx.de \
--to=sbabic@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