From: gerg@uclinux.org (Greg Ungerer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] ARM: imx: add support code for IMX50 based machines
Date: Wed, 06 Nov 2013 10:50:00 +1000 [thread overview]
Message-ID: <52799238.9010803@uclinux.org> (raw)
In-Reply-To: <20131105155701.GL3060@titan.lakedaemon.net>
Hi Jason,
On 06/11/13 01:57, Jason Cooper wrote:
> On Tue, Nov 05, 2013 at 01:02:06PM +1000, Greg Ungerer wrote:
>> Hi Jason,
>>
>> On 05/11/13 00:57, Jason Cooper wrote:
>>> On Mon, Nov 04, 2013 at 09:51:51AM -0500, Jason Cooper wrote:
>>>> What happened to the rest of the series?
>>>
>>> Crap. Nevermind. I just saw that Shawn had already taken the other
>>> patches into his tree. And here I thought I was caught up on
>>> everything...
>>
>> :-)
>>
>> Are you going to try and test out the imx50 support from Shawn's branch?
>
> I did manage to get it to boot, but I'm not confident in it yet. There
> is still a nagging problem (I had with my implementation as well) where
>
> $ sleep 10
>
> takes greater than 20 seconds. :( Which is why I originally asked you
> about the apll...
I have seen that. I haven't had a chance to look properly into it.
If you boot Freescales old LTIB code that supports the iMX50 it seems
they are messing with the clock setup to get it just right. It may
be that they just didn't get it right in their boot loader to start
with.
Regards
Greg
next prev parent reply other threads:[~2013-11-06 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 0:13 [PATCHv3] ARM: imx: add support code for IMX50 based machines gerg at uclinux.org
2013-11-04 3:16 ` Rob Herring
2013-11-04 13:08 ` Shawn Guo
2013-11-04 14:51 ` Jason Cooper
2013-11-04 14:57 ` Jason Cooper
2013-11-05 3:02 ` Greg Ungerer
2013-11-05 3:13 ` Shawn Guo
2013-11-05 15:57 ` Jason Cooper
2013-11-06 0:50 ` Greg Ungerer [this message]
2013-11-05 1:24 ` Shawn Guo
2013-11-05 2:56 ` Greg Ungerer
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=52799238.9010803@uclinux.org \
--to=gerg@uclinux.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).