From: tremyfr@gmail.com (Philippe Reynes)
To: linux-arm-kernel@lists.infradead.org
Subject: imx: apf27: the board no longer boot with latest git kernel
Date: Sat, 27 Jun 2015 22:38:11 +0200 [thread overview]
Message-ID: <558F09B3.9050907@gmail.com> (raw)
In-Reply-To: <CAOMZO5DgrV-divVoAa3K5QOLdxChewpGcKRLbDjMPRtpx_8KNQ@mail.gmail.com>
Hi Fabio,
On 27/06/15 21:17, Fabio Estevam wrote:
> Philippe,
>
> On Sat, Jun 27, 2015 at 2:34 PM, Fabio Estevam<festevam@gmail.com> wrote:
>
>> Yes, please submit a formal patch.
>>
>> I thought it was imx1_timer_init_dt because in imx27.dtsi we have:
>>
>> compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
>>
>> So I am wondering if this is correct or it should be
>>
>> compatible = "fsl,imx27-gpt", "fsl,imx21-gpt"; instead?
>
> In addition to the drivers/clocksource/timer-imx-gpt.c patch, could
> you also try the change below?
Yes, I do it
> --- a/arch/arm/boot/dts/imx27.dtsi
> +++ b/arch/arm/boot/dts/imx27.dtsi
> @@ -108,7 +108,7 @@
> };
>
> gpt1: timer at 10003000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x10003000 0x1000>;
> interrupts =<26>;
> clocks =<&clks IMX27_CLK_GPT1_IPG_GATE>,
> @@ -117,7 +117,7 @@
> };
>
> gpt2: timer at 10004000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x10004000 0x1000>;
> interrupts =<25>;
> clocks =<&clks IMX27_CLK_GPT2_IPG_GATE>,
> @@ -126,7 +126,7 @@
> };
>
> gpt3: timer at 10005000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x10005000 0x1000>;
> interrupts =<24>;
> clocks =<&clks IMX27_CLK_GPT3_IPG_GATE>,
> @@ -376,7 +376,7 @@
> };
>
> gpt4: timer at 10019000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x10019000 0x1000>;
> interrupts =<4>;
> clocks =<&clks IMX27_CLK_GPT4_IPG_GATE>,
> @@ -385,7 +385,7 @@
> };
>
> gpt5: timer at 1001a000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x1001a000 0x1000>;
> interrupts =<3>;
> clocks =<&clks IMX27_CLK_GPT5_IPG_GATE>,
> @@ -436,7 +436,7 @@
> };
>
> gpt6: timer at 1001f000 {
> - compatible = "fsl,imx27-gpt", "fsl,imx1-gpt";
> + compatible = "fsl,imx27-gpt", "fsl,imx21-gpt";
> reg =<0x1001f000 0x1000>;
> interrupts =<2>;
> clocks =<&clks IMX27_CLK_GPT6_IPG_GATE>,
I've tested this change, and it works fine.
In the file drivers/clocksource/timer-imx-gpt.c, there is :
#define imx21_gpt_irq_disable imx1_gpt_irq_disable
#define imx21_gpt_irq_enable imx1_gpt_irq_enable
So I think that using imx1 or imx21 has the same result;
Do you think I should put both change in on patch ?
Or is it better to do two patches please ?
Regards,
Philippe
next prev parent reply other threads:[~2015-06-27 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 13:21 imx: apf27: the board no longer boot with latest git kernel Philippe Reynes
2015-06-27 17:05 ` Fabio Estevam
2015-06-27 17:26 ` Philippe Reynes
2015-06-27 17:34 ` Fabio Estevam
2015-06-27 19:17 ` Fabio Estevam
2015-06-27 20:38 ` Philippe Reynes [this message]
2015-06-27 20:48 ` Fabio Estevam
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=558F09B3.9050907@gmail.com \
--to=tremyfr@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