From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pm9263 converted to at91 soc access
Date: Sat, 17 Apr 2010 16:09:12 -0500 [thread overview]
Message-ID: <4BCA2378.4060702@bumblecow.com> (raw)
In-Reply-To: <4BC4208C.80303@ronetix.at>
RONETIX - Asen Dimov wrote:
> Tom wrote:
>> Asen Dimov wrote:
>>> Signed-off-by: Asen Dimov <dimov@ronetix.at>
>>> ---
>>> board/ronetix/pm9263/led.c | 15 ++--
>>> board/ronetix/pm9263/pm9263.c | 195
>>> +++++++++++++++++++++--------------------
>>> include/configs/pm9263.h | 82 ++++++++---------
>>> 3 files changed, 146 insertions(+), 146 deletions(-)
<snip>
>>> +
>>> /* Enable clock */
>>> - at91_sys_write(AT91_PMC_PCER, 1 << AT91SAM9263_ID_PIOB |
>>> - 1 << AT91SAM9263_ID_PIOCDE);
>>> + writel(1 << AT91SAM9263_ID_PIOB, &pmc->pcer);
>> Missing PICOCDE..
>> Is this ok ?
>>
> The two leds are on PIOB, no leds on PIO: C, D or E.
> It is ok.
>>>
ok
>>> - at91_set_gpio_output(CONFIG_RED_LED, 1);
>>> - at91_set_gpio_output(CONFIG_GREEN_LED, 1);
<snip>
>>> - csa | AT91_MATRIX_EBI0_CS3A_SMC_SMARTMEDIA);
>>> + csa = readl(&matrix->csa[0]) | AT91_MATRIX_CSA_EBI_CS3A;
>>> + writel(csa, &matrix->csa[0]);
>> Missing SMARTMEDIA
>> Is this ok?
>>
> AT91_MATRIX_EBI0_CS3A_SMC_SMARTMEDIA sets the SMARTMEDIA bit and
> AT91_MATRIX_CSA_EBI_CS3A sets the SMARTMEDIA bit too.
> It is ok.
ok
>>>
>>> /* Configure SMC CS3 for NAND/SmartMedia */
<snip>
>>> + writel(1 << 25, &pio->pioc.puer);
>>> + writel((1 << 25) | (1 << 26), &pio->pioe.puer);
>>>
>> There should be #defines for these values.
>> There are similar cases where old #define's have be
>> converted to bit ops. The old method of #defines is preferred
> Ok. I will #define the values.
>> Tom
> Regards,
> Asen
Tom
prev parent reply other threads:[~2010-04-17 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 9:33 [U-Boot] [PATCH] pm9263 converted to at91 soc access Asen Dimov
2010-04-12 23:01 ` Tom
2010-04-13 7:43 ` RONETIX - Asen Dimov
2010-04-17 21:09 ` Tom Rix [this message]
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=4BCA2378.4060702@bumblecow.com \
--to=tom@bumblecow.com \
--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