linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michal.bachraty@gmail.com (michal.bachraty at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] clk: add si5351 i2c common clock driver
Date: Wed, 20 Mar 2013 06:55:35 -0700 (PDT)	[thread overview]
Message-ID: <6e120226-8a3c-415f-90f2-c44e7b6bbf96@googlegroups.com> (raw)
In-Reply-To: <fa.XCuSmq9Zwp3+wqFO8NEjpwADVZ0@ifi.uio.no>

Hi Sebastian,

Thanks for writing this driver!
I have tested your si5351 clock driver and his tuning capabilities. It works well, it generates proper clock frequency, but when new frequency is generated, little clock gap (1ms) is generated. Si5351 datasheet and WP claims, clock tuning can be without gaps - http://www.silabs.com/Support%20Documents/TechnicalDocs/Si5350-51-Frequency-Shifting-WP.pdf
I made some tests with Si5351A chip and I found that when tuning touch only Multisynth registers, it can tune without gaps. There is no need for soft PLL reset. I found also, accessing Multisynth registers is not atomic, so there can be another frequency at output, while not all registers are written. Writing only to one register seems to be atomic.
I'm using this chip for master audio clock frequency generator and tuning about +-50ppm. The question is, if driver you made has capability for tuning without gaps in +-50pmm (or any other) range with about 1ppm step and if not, it is possible to add this functionality? 

Thanks,

Michal

       reply	other threads:[~2013-03-20 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.WZVD0OA/Ooajh6BejiLf7TwBsJ8@ifi.uio.no>
     [not found] ` <fa.iIqrS6k+Vb5mLqAeL7iTsNsbKyo@ifi.uio.no>
     [not found]   ` <fa.L0b41q+fYFZG0WOFTGKLhn/cGPA@ifi.uio.no>
     [not found]     ` <fa.XCuSmq9Zwp3+wqFO8NEjpwADVZ0@ifi.uio.no>
2013-03-20 13:55       ` michal.bachraty at gmail.com [this message]
2013-03-20 16:48         ` [PATCH v3] clk: add si5351 i2c common clock driver Daniel Mack
2013-03-25 11:54           ` Sebastian Hesselbarth
2013-02-09 12:59 [PATCH] " Sebastian Hesselbarth
2013-03-18 10:43 ` [PATCH v3] " Sebastian Hesselbarth
2013-03-18 11:37   ` Daniel Mack
2013-03-20  0:26   ` Mike Turquette
2013-03-20  8:20     ` Sebastian Hesselbarth
2013-03-21 18:09   ` Lars-Peter Clausen
2013-03-21 21:32     ` Sebastian Hesselbarth
2013-03-23 10:07       ` Lars-Peter Clausen

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=6e120226-8a3c-415f-90f2-c44e7b6bbf96@googlegroups.com \
    --to=michal.bachraty@gmail.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 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).