All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: si570: Add a driver for SI570 oscillators
Date: Mon, 16 Sep 2013 10:34:28 -0600	[thread overview]
Message-ID: <52373314.5070806@wwwdotorg.org> (raw)
In-Reply-To: <1379033737-30015-2-git-send-email-soren.brinkmann@xilinx.com>

On 09/12/2013 06:55 PM, Soren Brinkmann wrote:
> Add a driver for SILabs 570, 571, 598, 599 programmable oscillators.
> The devices generate low-jitter clock signals and are reprogrammable via
> an I2C interface.

> diff --git a/Documentation/devicetree/bindings/clock/silabs,si570.txt b/Documentation/devicetree/bindings/clock/silabs,si570.txt

> +Required properties:
> + - compatible: Shall be one of "silabs,si57x", "silabs,si59x".
> + - reg: I2C device address.
> + - #clock-cells: From common clock bindings: Shall be 0.
> + - factory-fout: Factory set default frequency

So, there's no way to query this from the device at all? Looking at the
data-sheet, all the frequency generation parameters are in registers,
and the device supports I2C read commands. As such, I'm not convinced
this property is necessary.

> +Optional properties:
> + - initial-fout: Initial output frequency to set during probe

"probe" is a Linux-specific concept. This property should be removed. If
the driver is asked to set a specific frequency, it should do so, but I
don't think it should program something pro-actively just because it
starts up.

If this property is acceptable, it'd be better to describe it more along
the lines of the following:

initial-fout: The frequency at which the system requires the clock to
operate.

> + - temperature-stability-7ppm: Indicate a device with a temperature stability
> +			       of 7ppm
> +
> +Example:
> +	si570: clock-generator at 5d {
> +		#clock-cells = <0>;
> +		compatible = "silabs,si570";
> +		reg = <0x5d>;
> +		factory-fout = <156250000>;
> +	};

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: Rob Herring <rob.herring@calxeda.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Rob Landley <rob@landley.net>,
	Mike Turquette <mturquette@linaro.org>,
	Grant Likely <grant.likely@linaro.org>,
	Guenter Roeck <linux@roeck-us.net>,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Hyun Kwon <hyunk@xilinx.com>
Subject: Re: [PATCH] clk: si570: Add a driver for SI570 oscillators
Date: Mon, 16 Sep 2013 10:34:28 -0600	[thread overview]
Message-ID: <52373314.5070806@wwwdotorg.org> (raw)
In-Reply-To: <1379033737-30015-2-git-send-email-soren.brinkmann@xilinx.com>

On 09/12/2013 06:55 PM, Soren Brinkmann wrote:
> Add a driver for SILabs 570, 571, 598, 599 programmable oscillators.
> The devices generate low-jitter clock signals and are reprogrammable via
> an I2C interface.

> diff --git a/Documentation/devicetree/bindings/clock/silabs,si570.txt b/Documentation/devicetree/bindings/clock/silabs,si570.txt

> +Required properties:
> + - compatible: Shall be one of "silabs,si57x", "silabs,si59x".
> + - reg: I2C device address.
> + - #clock-cells: From common clock bindings: Shall be 0.
> + - factory-fout: Factory set default frequency

So, there's no way to query this from the device at all? Looking at the
data-sheet, all the frequency generation parameters are in registers,
and the device supports I2C read commands. As such, I'm not convinced
this property is necessary.

> +Optional properties:
> + - initial-fout: Initial output frequency to set during probe

"probe" is a Linux-specific concept. This property should be removed. If
the driver is asked to set a specific frequency, it should do so, but I
don't think it should program something pro-actively just because it
starts up.

If this property is acceptable, it'd be better to describe it more along
the lines of the following:

initial-fout: The frequency at which the system requires the clock to
operate.

> + - temperature-stability-7ppm: Indicate a device with a temperature stability
> +			       of 7ppm
> +
> +Example:
> +	si570: clock-generator@5d {
> +		#clock-cells = <0>;
> +		compatible = "silabs,si570";
> +		reg = <0x5d>;
> +		factory-fout = <156250000>;
> +	};


  parent reply	other threads:[~2013-09-16 16:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  0:55 [PATCH] SI570 clock driver Soren Brinkmann
2013-09-13  0:55 ` Soren Brinkmann
2013-09-13  0:55 ` [PATCH] clk: si570: Add a driver for SI570 oscillators Soren Brinkmann
2013-09-13  0:55   ` Soren Brinkmann
2013-09-13  0:55   ` Soren Brinkmann
2013-09-13 17:00   ` Guenter Roeck
2013-09-13 17:00     ` Guenter Roeck
2013-09-13 17:26     ` Sören Brinkmann
2013-09-13 17:26       ` Sören Brinkmann
2013-09-13 17:26       ` Sören Brinkmann
2013-09-13 19:48       ` Guenter Roeck
2013-09-13 19:48         ` Guenter Roeck
2013-09-13 21:05         ` Sören Brinkmann
2013-09-13 21:05           ` Sören Brinkmann
2013-09-13 21:05           ` Sören Brinkmann
2013-09-13 21:14           ` Guenter Roeck
2013-09-13 21:14             ` Guenter Roeck
2013-09-14  8:01       ` Sebastian Hesselbarth
2013-09-14  8:01         ` Sebastian Hesselbarth
2013-09-14  8:01         ` Sebastian Hesselbarth
2013-09-16 16:34   ` Stephen Warren [this message]
2013-09-16 16:34     ` Stephen Warren
2013-09-16 16:49     ` Guenter Roeck
2013-09-16 16:49       ` Guenter Roeck
2013-09-16 16:59       ` Stephen Warren
2013-09-16 16:59         ` Stephen Warren
2013-09-16 16:59         ` Stephen Warren
2013-09-16 17:35         ` Guenter Roeck
2013-09-16 17:35           ` Guenter Roeck
2013-09-16 17:35           ` Guenter Roeck
2013-09-16 18:37           ` Stephen Warren
2013-09-16 18:37             ` Stephen Warren
2013-09-16 18:37             ` Stephen Warren
2013-09-16 19:14             ` Guenter Roeck
2013-09-16 19:14               ` Guenter Roeck
2013-09-17  7:59             ` Sebastian Hesselbarth
2013-09-17  7:59               ` Sebastian Hesselbarth
2013-09-17 13:08               ` Guenter Roeck
2013-09-17 13:08                 ` Guenter Roeck
2013-09-17 16:14               ` Stephen Warren
2013-09-17 16:14                 ` Stephen Warren
2013-09-18 20:41                 ` Sören Brinkmann
2013-09-18 20:41                   ` Sören Brinkmann
2013-09-18 20:41                   ` Sören Brinkmann

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=52373314.5070806@wwwdotorg.org \
    --to=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.