linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: koelsch: Correct clock frequency of X2 DU clock input
Date: Tue, 4 Apr 2017 12:31:39 +0200	[thread overview]
Message-ID: <CAMuHMdXqEhjzo5PH3a7JyUsuCBpnDGibGabD5k5oVhZY=FkRow@mail.gmail.com> (raw)
In-Reply-To: <2246751.IOz92zzvZ6@avalon>

Hi Laurent,

On Tue, Apr 4, 2017 at 12:05 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Monday 03 Apr 2017 11:55:19 Geert Uytterhoeven wrote:
>> The X2 crystal oscillator on the Koelsch development board provides a
>> 74.25 MHz clock, not a 148.5 MHz clock.
>>
>> Fixes: cd21cb46e14aae3a ("ARM: shmobile: koelsch: Add DU external pixel
>> clocks to DT") Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>> Confirmed by schematics, user manual, and physical inspection of 2
>> Koelsch instances (my scope has not enough bandwidth to measure the
>> actual frequency).
>
> Stupid question, have you tested the corresponding (HDMI) DU output ? If so,

No I haven't.

Niklas, can you please fire up your display? Thanks!

> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Thanks ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2017-04-04 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  9:55 [PATCH] ARM: dts: koelsch: Correct clock frequency of X2 DU clock input Geert Uytterhoeven
2017-04-03 10:35 ` Simon Horman
2017-04-04 10:05 ` Laurent Pinchart
2017-04-04 10:31   ` Geert Uytterhoeven [this message]
2017-04-04 11:10     ` Niklas Söderlund

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='CAMuHMdXqEhjzo5PH3a7JyUsuCBpnDGibGabD5k5oVhZY=FkRow@mail.gmail.com' \
    --to=geert@linux-m68k.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).