linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jason77.wang@gmail.com (Hui Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] can: flexcan: add 2nd clock to support imx53 and newer
Date: Wed, 18 Jul 2012 18:05:08 +0800	[thread overview]
Message-ID: <50068A54.80705@gmail.com> (raw)
In-Reply-To: <1342601282-1208-1-git-send-email-mkl@pengutronix.de>

Marc Kleine-Budde wrote:
> From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
>
> This patch adds support for a second clock to the flexcan driver. On
> modern freescale ARM cores like the imx53 and imx6q two clocks ("ipg"
> and "per") must be enabled in order to access the CAN core.
>
> In the original driver, the clock was requested without specifying the
> connection id, further all mainline ARM archs with flexcan support
> (imx28, imx25, imx35) register their flexcan clock without a
> connection id, too.
>
> This patch first renames the existing clk variable to clk_ipg and
> converts it to devm for easier error handling. The connection id "ipg"
> is added to the devm_clk_get() call. Then a second clock "per" is
> requested. As all archs don't specify a connection id, both clk_get
> return the same clock. This ensures compatibility to existing flexcan
> support and adds support for imx53 at the same time.
>
> After this patch hits mainline, the archs may give their existing
> flexcan clock the "ipg" connection id and implement a dummy "per"
> clock.
>
> This patch has been tested on imx28 (unmodified clk tree) and on imx53
> with a seperate "ipg" and "per" clock.
>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: Hui Wang <jason77.wang@gmail.com>
>   
Acked-by: Hui Wang <jason77.wang@gmail.com>

  reply	other threads:[~2012-07-18 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  8:48 [PATCH v2] can: flexcan: add 2nd clock to support imx53 and newer Marc Kleine-Budde
2012-07-18 10:05 ` Hui Wang [this message]
2012-07-18 10:16   ` 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=50068A54.80705@gmail.com \
    --to=jason77.wang@gmail.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).