linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] net: flexcan: clock-frequency is optional for device tree probe
Date: Thu, 28 Jun 2012 11:21:40 +0800	[thread overview]
Message-ID: <1340853701-4488-2-git-send-email-shawn.guo@linaro.org> (raw)
In-Reply-To: <1340853701-4488-1-git-send-email-shawn.guo@linaro.org>

The property clock-frequency is optional for device tree probe.  When
it's absent, the flexcan driver will try to get the frequency from clk
system by calling clk_get_rate.

Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
 .../devicetree/bindings/net/can/fsl-flexcan.txt    |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
index f31b686..8ff324e 100644
--- a/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
+++ b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
@@ -11,6 +11,9 @@ Required properties:
 
 - reg : Offset and length of the register set for this device
 - interrupts : Interrupt tuple for this device
+
+Optional properties:
+
 - clock-frequency : The oscillator frequency driving the flexcan device
 
 Example:
-- 
1.7.5.4

  reply	other threads:[~2012-06-28  3:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  3:21 [PATCH v2 0/2] flexcan driver updates Shawn Guo
2012-06-28  3:21 ` Shawn Guo [this message]
2012-06-28 11:23   ` [PATCH v2 1/2] net: flexcan: clock-frequency is optional for device tree probe Dong Aisheng
2012-06-28  3:21 ` [PATCH v2 2/2] net: flexcan: add transceiver switch gpios support Shawn Guo
2012-06-28  5:22   ` Lothar Waßmann
2012-06-28  5:30     ` Shawn Guo
2012-06-28  6:14   ` Hui Wang
2012-06-28  6:34     ` Shawn Guo
2012-06-28  7:01       ` Hui Wang
2012-06-28 10:32         ` Marc Kleine-Budde
2012-06-28 10:31   ` Marc Kleine-Budde
2012-06-28 11:21     ` Shawn Guo
2012-06-28 11:29       ` Marc Kleine-Budde
2012-06-28 11:41         ` Shawn Guo
2012-06-28 11:52           ` Shawn Guo
2012-06-28 12:05             ` Shawn Guo
2012-06-28 12:11               ` Dong Aisheng
2012-06-28 12:19             ` Lothar Waßmann
2012-06-28 12:07           ` Lothar Waßmann
2012-06-28 12:13             ` Shawn Guo
2012-06-28 12:24               ` Lothar Waßmann
2012-07-02  2:55                 ` Hui Wang
2012-06-28 12:08           ` Kurt Van Dijck
2012-06-28 12:10             ` Marc Kleine-Budde
2012-06-28 12:16             ` Shawn Guo
2012-06-28 11:39     ` Dong Aisheng
2012-06-28 11:33   ` Dong Aisheng
2012-06-28 11:46     ` Shawn Guo
2012-06-28 11:48       ` Dong Aisheng
2012-06-28 12:00         ` Shawn Guo
2012-06-28 12:02         ` Dong Aisheng
2012-06-28 12:19           ` Shawn Guo
2012-06-28 12:05       ` Marc Kleine-Budde
2012-06-28 12:18         ` Dong Aisheng
2012-06-28 12:32           ` Lothar Waßmann
2012-06-28 12:40             ` Shawn Guo
2012-06-28 12:47             ` Dong Aisheng
2012-06-28 12:39           ` Shawn Guo
2012-06-29  9:27           ` Marc Kleine-Budde

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=1340853701-4488-2-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@linaro.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 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).