public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: Guenter Roeck <linux@roeck-us.net>, <mturquette@linaro.org>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lee.jones@linaro.org>, <andrey@elphel.com>,
	<sebastian.hesselbarth@gmail.com>, <rabeeh@solid-run.com>
Subject: Re: clock driver
Date: Tue, 26 May 2015 17:32:13 -0700	[thread overview]
Message-ID: <5565108D.2020502@freescale.com> (raw)
In-Reply-To: <55650DBA.5000304@freescale.com>

Michael,

Can you give me some guidance here?


On 05/26/2015 05:20 PM, York Sun wrote:
> 
> 
> On 05/26/2015 03:38 PM, Guenter Roeck wrote:
>> On Tue, May 26, 2015 at 12:12:11PM -0700, York Sun wrote:
>>> Linux experts,
>>>
>>> I have rewritten a driver for Silicon Labs SI5338 programmable clock chip. The
>>> original driver was written by Andrey (CC'ed), but was floatingn outside of the
>>> kernel. The driver was written to use sysfs as the interface, not the common
>>> clock framework. I wonder if I have to rewrite the driver following common clock
>>> framework. One concern is to support a feature to accept ClockBuilder (TM)
>>> output on sysfs. I don't see sysfs support on common clock framework. Please
>>> correct me if I am wrong.
>>>
>>> If not using common clock framework is acceptable, I would like to send a RFC
>>> patch for review.
>>>
>> My original driver for si570 was rejected because it didn't support the clock
>> framework, so you might face an uphill battle.
>>
>> SI provides a document for SI5338 describing how to configure it without
>> using clockbuilder [1]. Can that be used to implement generic code which
>> doesn't need clockbuilder ?
>>
> 
> The driver is capable to handle the user's input and enable the clocks. Removing
> the support of importing is a step back. At least it is a feature I am using. I
> believe Andrey also used this feature when the driver was first drafted.
> 
> That being said, my application relies on setting multiple clock chips on a PCIe
> device. That means I cannot put the configuration into device tree. There may be
> a way to fill device tree, but I am not ready to explore yet. Without a sysfs
> interface, can I change the configuration for each clock?
> 
> I also found COMMON_CLK is a bool, not tristate. It is only selected by others.
> Is there a reason for doing so? My current platform (P1022DS) doesn't have
> CONFIG_COMMON_CLK enabled.
> 

If converting my driver to common clock framework, I need to find a way to
configure the clocks without recompiling the kernel. I will have about 30 clock
chips (with different frequency) on multiple PCIe cards.

York

  reply	other threads:[~2015-05-27  0:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 19:12 clock driver York Sun
2015-05-26 22:38 ` Guenter Roeck
2015-05-27  0:20   ` York Sun
2015-05-27  0:32     ` York Sun [this message]
2015-05-27  7:09       ` Sebastian Hesselbarth
2015-05-27 15:07         ` York Sun
2015-05-27 16:42           ` Sebastian Hesselbarth
2015-05-27 16:46             ` York Sun
2015-05-27 17:09               ` Guenter Roeck
2015-05-27 17:10                 ` York Sun
2015-05-27 17:30       ` Michael Turquette
2015-05-27 17:45         ` York Sun
2015-05-27 18:15           ` Guenter Roeck
2015-05-27 18:24             ` York Sun
2015-05-27 18:54               ` Guenter Roeck
2015-05-27 18:58                 ` York Sun
     [not found]                   ` <14d96cd6d64.f62a1a09739217.9114963256886461171@elphel.com>
2015-05-27 23:08                     ` Guenter Roeck
2015-05-27 23:58                       ` andrey
2015-05-28  0:10                         ` Guenter Roeck
2015-05-28  0:29                           ` andrey
2015-05-28  6:11                             ` Michael Turquette
2015-05-28 15:24                               ` York Sun
2015-06-10  0:40         ` York Sun

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=5565108D.2020502@freescale.com \
    --to=yorksun@freescale.com \
    --cc=andrey@elphel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mturquette@linaro.org \
    --cc=rabeeh@solid-run.com \
    --cc=sebastian.hesselbarth@gmail.com \
    /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