From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] clk: fixup argument order when setting VCO parameters
Date: Thu, 25 Jul 2013 10:36:25 +0100 [thread overview]
Message-ID: <51F0F199.3040501@arm.com> (raw)
In-Reply-To: <CACRpkdb7UGS8ysPv=LakbWouUdL9MpKvrgYKh_v9NqSYV3TStg@mail.gmail.com>
On 25/07/13 10:33, Linus Walleij wrote:
> On Thu, Jul 25, 2013 at 11:30 AM, Jonathan Austin
> <jonathan.austin@arm.com> wrote:
>
>>> What I don't understand is why my CLCD VGA output has
>>> been working all the time :-(
>>>
>>
>> No, this confuses me too - perhaps the display you've got it plugged in to
>> is really lenient about modes and just made the best of it?
>
> I think it's because it is set up into some mode by the boot
> monitor, as I get the boot monitor prompt on the VGA
> display.
>
> Then as the VCO params get written, it is never really unlocked
> so the registers are untouched.
>
> You may have a different boot monitor?
>
Ahh, that seems highly likely. I don't ever see boot-monitor (boot
straight in to uboot) but I don't see anything on the display until the
kernel boots, so I don't think BM is setting up the VCO for me.
Jonny
next prev parent reply other threads:[~2013-07-25 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 15:42 [PATCH 0/2] Restore Integrator/CP CLCD to fully working state Jonathan Austin
2013-07-23 15:42 ` [PATCH 1/2] ARM: integrator_cp: Set LCD{0, 1} enable lines when turning on CLCD Jonathan Austin
2013-08-15 15:41 ` [PATCH 1/2] ARM: integrator_cp: Set LCD{0,1} " Jonathan Austin
2013-08-28 7:29 ` Linus Walleij
2013-07-23 15:42 ` [PATCH 2/2] clk: fixup argument order when setting VCO parameters Jonathan Austin
2013-07-24 19:32 ` Linus Walleij
2013-07-25 9:30 ` Jonathan Austin
2013-07-25 9:33 ` Linus Walleij
2013-07-25 9:36 ` Jonathan Austin [this message]
2013-07-25 14:01 ` Linus Walleij
2013-07-25 17:44 ` Mike Turquette
2013-07-29 11:01 ` Jonathan Austin
2013-07-24 23:26 ` Mike Turquette
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=51F0F199.3040501@arm.com \
--to=jonathan.austin@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.