linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Add device tree file for the armadeus apf27
Date: Wed, 31 Oct 2012 08:32:16 +0100	[thread overview]
Message-ID: <20121031073216.GI1641@pengutronix.de> (raw)
In-Reply-To: <1351626944.55016.YahooMailNeo@web28804.mail.ir2.yahoo.com>

On Tue, Oct 30, 2012 at 07:55:44PM +0000, Philippe Reynes wrote:
> 
> 
> Hi Sascha,
> >> +??? ??? osc26m {
> 
> >> +??? ??? ??? compatible = "fsl,imx-osc26m", "fixed-clock";
> >> +??? ??? ??? clock-frequency = <33554432>;
> 
> >Is this really correct? The Datasheet specificies 26MHz, some boards
> >have 27Mhz, but 33?
> 
> The clock value on this board is? 32.768kHz, so 32768 * 1024.
> I've tried others value, all others produce weird behaviour on the serial.

Ok, so your board runs with the 32.768KHz clock input. I didn't know
there are boards that use this as the reference clock. It seems this
is not handled in the current clk code. Could you test the patch I just
sent to the mailing list (Cced you) and provide a Tested-by tag if it
works? The clock frequency provided in the device tree shouldn't make
a difference then anymore. You should specify it to 0 if you have
nothing connected there.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2012-10-31  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 16:29 [PATCH] Add device tree file for the armadeus apf27 Philippe Reynes
2012-10-29 21:10 ` Sascha Hauer
2012-10-30 19:55   ` Philippe Reynes
2012-10-31  7:32     ` Sascha Hauer [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=20121031073216.GI1641@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).