From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: kernel@pengutronix.de, lst@pengutronix.de,
linux-arm-kernel@lists.infradead.org, linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/2] can + ARM i.MX53: use 24 MHz clock parent on i.MX53
Date: Tue, 26 Nov 2013 15:35:35 +0100 [thread overview]
Message-ID: <5294B1B7.4030006@pengutronix.de> (raw)
In-Reply-To: <20131126143258.GA5685@S2101-09.ap.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On 11/26/2013 03:33 PM, Shawn Guo wrote:
> On Tue, Nov 26, 2013 at 09:26:40AM +0100, Marc Kleine-Budde wrote:
>> The problem is, that the wrong clock is being used. An all i.mx, but not
>> on imx6, both clocks are the same, the bug doesn't show up. So before we
>> can use the 24 MHz clock on mx53, we have to fix the driver.
>
> So it sounds like a more appropriate merging path would be that,
> you send the driver fix right away to mainline via net tree with
> v3.13-rc series, and I rebase IMX tree on the -rc that has the fix,
> and then apply the DTS patch.
^^^
Clocktree not Devicetree :)
Okay, fine with me.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] can + ARM i.MX53: use 24 MHz clock parent on i.MX53
Date: Tue, 26 Nov 2013 15:35:35 +0100 [thread overview]
Message-ID: <5294B1B7.4030006@pengutronix.de> (raw)
In-Reply-To: <20131126143258.GA5685@S2101-09.ap.freescale.net>
On 11/26/2013 03:33 PM, Shawn Guo wrote:
> On Tue, Nov 26, 2013 at 09:26:40AM +0100, Marc Kleine-Budde wrote:
>> The problem is, that the wrong clock is being used. An all i.mx, but not
>> on imx6, both clocks are the same, the bug doesn't show up. So before we
>> can use the 24 MHz clock on mx53, we have to fix the driver.
>
> So it sounds like a more appropriate merging path would be that,
> you send the driver fix right away to mainline via net tree with
> v3.13-rc series, and I rebase IMX tree on the -rc that has the fix,
> and then apply the DTS patch.
^^^
Clocktree not Devicetree :)
Okay, fine with me.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131126/bd077ba2/attachment.sig>
next prev parent reply other threads:[~2013-11-26 14:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:15 [PATCH v2 1/2] can + ARM i.MX53: use 24 MHz clock parent on i.MX53 Marc Kleine-Budde
2013-11-25 21:15 ` Marc Kleine-Budde
2013-11-25 21:15 ` [PATCH v2 1/2] can: flexcan: use correct clock as base for bit rate calculation Marc Kleine-Budde
2013-11-25 21:15 ` Marc Kleine-Budde
2013-11-26 8:27 ` Marc Kleine-Budde
2013-11-26 8:27 ` Marc Kleine-Budde
2013-11-26 8:35 ` Marc Kleine-Budde
2013-11-26 8:35 ` Marc Kleine-Budde
2013-11-25 21:15 ` [PATCH v2 2/2] ARM i.MX5: set CAN peripheral clock to 24 MHz parent Marc Kleine-Budde
2013-11-25 21:15 ` Marc Kleine-Budde
2013-11-26 4:53 ` [PATCH v2 1/2] can + ARM i.MX53: use 24 MHz clock parent on i.MX53 Shawn Guo
2013-11-26 4:53 ` Shawn Guo
2013-11-26 8:26 ` Marc Kleine-Budde
2013-11-26 8:26 ` Marc Kleine-Budde
2013-11-26 14:33 ` Shawn Guo
2013-11-26 14:33 ` Shawn Guo
2013-11-26 14:35 ` Marc Kleine-Budde [this message]
2013-11-26 14:35 ` Marc Kleine-Budde
2013-12-03 10:54 ` Marc Kleine-Budde
2013-12-03 10:54 ` Marc Kleine-Budde
2013-12-03 11:46 ` Shawn Guo
2013-12-03 11:46 ` Shawn Guo
2013-12-09 5:59 ` Shawn Guo
2013-12-09 5:59 ` Shawn Guo
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=5294B1B7.4030006@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=lst@pengutronix.de \
--cc=shawn.guo@linaro.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.