From: Wolfgang Grandegger <wg@grandegger•com>
To: Bhaskar Upadhaya <Bhaskar.Upadhaya@freescale•com>
Cc: SocketCAN Core Mailing List <socketcan-core@lists•berlios.de>,
devicetree-discuss@lists•ozlabs.org,
linuxppc-dev@lists•ozlabs.org, inuxppc-dev@linux•freescale.net
Subject: Re: [PATCH][upstream] powerpc: Adding bindings for flexcan controller
Date: Sun, 26 Jun 2011 21:10:47 +0200 [thread overview]
Message-ID: <4E078437.5010708@grandegger.com> (raw)
In-Reply-To: <1303221511-12903-1-git-send-email-Bhaskar.Upadhaya@freescale.com>
On 04/19/2011 03:58 PM, Bhaskar Upadhaya wrote:
> From: Bhaskar Upadhaya <bhaskar.upadhaya@freescale•com>
>
> Signed-off-by: Bhaskar Upadhaya <bhaskar.upadhaya@freescale•com>
> Acked-By: Scott Wood <scottwood@freescale•com>
> ---
> Based upon git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (branch -> master)
>
> .../devicetree/bindings/net/can/fsl-flexcan.txt | 61 ++++++++++++++++++++
> 1 files changed, 61 insertions(+), 0 deletions(-)
> create mode 100755 Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
>
> diff --git a/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
> new file mode 100755
> index 0000000..1a729f0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
> @@ -0,0 +1,61 @@
> +CAN Device Tree Bindings
> +------------------------
> +2011 Freescale Semiconductor, Inc.
> +
> +fsl,flexcan-v1.0 nodes
> +-----------------------
> +In addition to the required compatible-, reg- and interrupt-properties, you can
> +also specify which clock source shall be used for the controller.
> +
> +CPI Clock- Can Protocol Interface Clock
> + This CLK_SRC bit of CTRL(control register) selects the clock source to
> + the CAN Protocol Interface(CPI) to be either the peripheral clock
> + (driven by the PLL) or the crystal oscillator clock. The selected clock
> + is the one fed to the prescaler to generate the Serial Clock (Sclock).
> + The PRESDIV field of CTRL(control register) controls a prescaler that
> + generates the Serial Clock (Sclock), whose period defines the
> + time quantum used to compose the CAN waveform.
> +
> +Can Engine Clock Source
> + There are two sources for CAN clock
> + - Platform Clock It represents the bus clock
> + - Oscillator Clock
> +
> + Peripheral Clock (PLL)
> + --------------
> + |
> + --------- -------------
> + | |CPI Clock | Prescaler | Sclock
> + | |---------------->| (1.. 256) |------------>
> + --------- -------------
> + | |
> + -------------- ---------------------CLK_SRC
> + Oscillator Clock
> +
> +- fsl,flexcan-clock-source : CAN Engine Clock Source.This property selects
> + the peripheral clock. PLL clock is fed to the
> + prescaler to generate the Serial Clock (Sclock).
> + Valid values are "oscillator" and "platform"
> + "oscillator": CAN engine clock source is oscillator clock.
> + "platform" The CAN engine clock source is the bus clock
> + (platform clock).
> +
> +- fsl,flexcan-clock-divider : for the reference and system clock, an additional
> + clock divider can be specified.
> +- clock-frequency: frequency required to calculate the bitrate for FlexCAN.
> +
> +Note:
> + - v1.0 of flexcan-v1.0 represent the IP block version for P1010 SOC.
> + - P1010 does not have oscillator as the Clock Source.So the default
> + Clock Source is platform clock.
> +Examples:
> +
> + can0@1c000 {
> + compatible = "fsl,flexcan-v1.0";
> + reg = <0x1c000 0x1000>;
> + interrupts = <48 0x2>;
> + interrupt-parent = <&mpic>;
> + fsl,flexcan-clock-source = "platform";
> + fsl,flexcan-clock-divider = <2>;
> + clock-frequency = <fixed by u-boot>;
> + };
I just realized that this patch has hit the mainline kernel but I do not
find the implementation for that new binding. Have I missed something?
Wolfgang.
prev parent reply other threads:[~2011-06-26 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 13:58 [PATCH][upstream] powerpc: Adding bindings for flexcan controller Bhaskar Upadhaya
2011-05-19 6:06 ` Kumar Gala
2011-06-26 19:10 ` Wolfgang Grandegger [this message]
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=4E078437.5010708@grandegger.com \
--to=wg@grandegger$(echo .)com \
--cc=Bhaskar.Upadhaya@freescale$(echo .)com \
--cc=devicetree-discuss@lists$(echo .)ozlabs.org \
--cc=inuxppc-dev@linux$(echo .)freescale.net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=socketcan-core@lists$(echo .)berlios.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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