linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michal.bachraty@streamunlimited.com (Michal Bachraty)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] clk: add si5351 i2c common clock driver
Date: Thu, 11 Apr 2013 09:44:47 +0200	[thread overview]
Message-ID: <11205025.2MA5VbIUoF@ganymedes> (raw)
In-Reply-To: <5165A0FD.5030308@gmail.com>

Hi Sebastian,

On Wednesday, April 10, 2013 19:27:25 Sebastian Hesselbarth wrote:
> Hmm, is there any driver using the clock output? Does it
> clk_prepare_enable() the clock? I tend not to mess with anything the
> bootloader or eeprom config left disabled. It works for me, but here the
> driver will prepare/enable the clock prior use.

For my case, disabled clock outputs in bootloader are correct. I'm working on 
module board with lot of purposes. For one I need to tune frequncy, for other 
not. In some cases I can use  clk_prepare_enable. For now, I need to tune clk, 
so I can't use clk_prepare_enable. Si5351 chip has no problem with enabling 
clock output multiple times, when calling clk_set_rate. So if this feature 
will not be in driver, I need to stay with patch upon driver.

Many thaks for writting driver,

Michal

  reply	other threads:[~2013-04-11  7:44 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 12:59 [PATCH] clk: add si5351 i2c common clock driver Sebastian Hesselbarth
2013-02-11  5:46 ` Mike Turquette
2013-02-11  9:52   ` Sebastian Hesselbarth
2013-02-18 10:19 ` Daniel Mack
2013-02-19 19:15 ` Daniel Mack
2013-02-27 10:01   ` Sebastian Hesselbarth
2013-03-01 15:01     ` Daniel Mack
2013-03-16 13:10 ` [PATCH v2] " Sebastian Hesselbarth
2013-03-16 15:10   ` Daniel Mack
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
2013-03-23 14:46   ` [PATCH v4] " Sebastian Hesselbarth
2013-04-02 23:46     ` Mike Turquette
2013-04-03 11:10       ` Sebastian Hesselbarth
2013-04-05  5:23     ` [PATCH v5] " Sebastian Hesselbarth
2013-04-07 22:50       ` [v5] " Guenter Roeck
2013-04-07 23:49         ` Sebastian Hesselbarth
2013-04-08  0:17           ` Guenter Roeck
2013-04-08  6:11             ` Sebastian Hesselbarth
2013-04-08 14:54               ` Guenter Roeck
2013-04-08 15:38                 ` Sebastian Hesselbarth
2013-04-08 17:36                   ` Mike Turquette
2013-04-08 18:32                     ` Sebastian Hesselbarth
2013-04-08 16:46       ` [PATCH v6] " Sebastian Hesselbarth
2013-04-08 17:46         ` Guenter Roeck
2013-04-08 18:24           ` Sebastian Hesselbarth
2013-04-10  9:40         ` [PATCH v7] " Sebastian Hesselbarth
2013-04-10 10:17           ` Daniel Mack
2013-04-10 14:48             ` Michal Bachraty
2013-04-10 17:27               ` Sebastian Hesselbarth
2013-04-11  7:44                 ` Michal Bachraty [this message]
2013-04-11  8:22                   ` Sebastian Hesselbarth
2013-04-10 19:34           ` Guenter Roeck
2013-04-11 19:42           ` [PATCH v8] " Sebastian Hesselbarth
2013-04-12 11:43             ` Michal Bachraty
2013-04-12 18:19             ` 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=11205025.2MA5VbIUoF@ganymedes \
    --to=michal.bachraty@streamunlimited.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).