From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4 v3] arm: Support new Xilinx Zynq platform
Date: Fri, 14 Sep 2012 13:09:53 +0200 [thread overview]
Message-ID: <50531081.60005@monstr.eu> (raw)
In-Reply-To: <201209141258.33805.marex@denx.de>
On 09/14/2012 12:58 PM, Marek Vasut wrote:
> Dear Michal Simek,
>
>> On 09/14/2012 11:59 AM, Marek Vasut wrote:
>>> Dear Michal Simek,
>>>
>>>> On 09/14/2012 09:50 AM, Marek Vasut wrote:
>>>>> Dear Michal Simek,
>>>>>
>>>>>> Add timer driver.
>>>>>>
>>>>>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>>>>>> CC: Joe Hershberger <joe.hershberger@gmail.com>
>>>>>> CC: Marek Vasut <marex@denx.de>
>>>>>>
>>>>>> ---
>>>>>> v2: Move lowlevel_init.S from board to cpu folder
>>>>>>
>>>>>> Remove XPSS prefix
>>>>>> Rename XSCUTIMER -> SCUTIMER
>>>>>>
>>>>>> v3: Using clrsetbits_le32
>>>>>>
>>>>>> Fix compilation warning
>>>>>> Move reset_cpu from board to cpu.c
>>>>>> Move lowlevel_init to cpu.c
>>>>>
>>>>> [...]
>>>>>
>>>>>> +#include <common.h>
>>>>>> +
>>>>>> +inline void lowlevel_init(void) {}
>>>>>> +
>>>>>> +void reset_cpu(ulong addr)
>>>>>> +{
>>>>>> + while (1)
>>>>>> + ;
>>>>>> +}
>>>>>
>>>>> I wonder how useful such CPU is if simple endless loop restarts it ;-)
>>>>
>>>> Don't be scared it will be fixed when slcr is ready.
>>>
>>> Nay, I was just rambling and giving you a bit of torture :-)
>> :
>> :-)
>> :
>>> What's SLCR ?
>>
>> System level control registers. For example for clock setup, unit reset,
>> ddr setup configuration pin setup, etc.
>
> Shouldn't that be part of this patchset then?
No. Basic setup is done in first stage bootloader. I will talk with
Xilinx how to handle this. I think that special driver(in zynq cpu folder)
for slcr make sense to have all SLCR operation at one place and not
to call it directly.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-09-14 11:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 6:23 [U-Boot] [PATCH 1/4 v3] serial: Add Zynq serial driver Michal Simek
2012-09-14 6:23 ` [U-Boot] [PATCH 2/4 v3] net: Add driver for Zynq Gem IP Michal Simek
2012-09-14 7:48 ` Marek Vasut
2012-09-28 16:04 ` Joe Hershberger
2012-09-14 6:23 ` [U-Boot] [PATCH 3/4 v3] arm: Support new Xilinx Zynq platform Michal Simek
2012-09-14 7:50 ` Marek Vasut
2012-09-14 8:10 ` Michal Simek
2012-09-14 9:59 ` Marek Vasut
2012-09-14 10:42 ` Michal Simek
2012-09-14 10:58 ` Marek Vasut
2012-09-14 11:09 ` Michal Simek [this message]
2012-09-14 6:23 ` [U-Boot] [PATCH 4/4 v4] xilinx: Add new Zynq board Michal Simek
2012-09-14 7:51 ` Marek Vasut
2012-09-28 19:30 ` Albert ARIBAUD
2012-09-28 20:00 ` Michal Simek
2012-09-14 6:38 ` [U-Boot] [PATCH 1/4 v3] serial: Add Zynq serial driver Michal Simek
2012-09-14 7:45 ` Marek Vasut
2012-09-14 8:19 ` Michal Simek
2012-09-14 10:03 ` Marek Vasut
2012-09-14 10:49 ` Michal Simek
2012-09-14 11:00 ` Marek Vasut
2012-09-14 11:05 ` Michal Simek
2012-09-14 16:58 ` Marek Vasut
2012-09-14 18:53 ` Joe Hershberger
2012-09-19 10:40 ` Michal Simek
2012-09-19 10:52 ` Marek Vasut
2012-09-19 10:56 ` Michal Simek
2012-09-19 17:38 ` Tom Rini
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=50531081.60005@monstr.eu \
--to=monstr@monstr.eu \
--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