From: Sergey Organov <sorganov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>
Subject: Re: ARM iMX6sx board fails to boot with kernel 6.17
Date: Wed, 01 Oct 2025 23:04:14 +0300 [thread overview]
Message-ID: <87a52afkxt.fsf@osv.gnss.ru> (raw)
In-Reply-To: <CAOMZO5DG=cQtqyzihrFarEq6=1AOAPAMkeXajjGxiW0yvFRa0Q@mail.gmail.com> (Fabio Estevam's message of "Tue, 30 Sep 2025 16:09:13 -0300")
Hi Fabio,
Fabio Estevam <festevam@gmail.com> writes:
> Hi Sergey,
>
> On Tue, Sep 30, 2025 at 12:49 PM Sergey Organov <sorganov@gmail.com> wrote:
>>
>> Hello,
>>
>> I'm looking for help with the following issue.
>>
>> I'm trying to upgrade kernel on my custom iMX6sx board from very old
>> 4.9.146 to resent 6.17. The board has eMMC connected to usdhc4, and
>> u-boot happily starts kernel from eMMC. The kernel boot sequence,
>> however, hangs waiting for root file-system as it doesn't see eMMC.
>
> I tried booting 6.17 on an imx6sx-sdb board and it booted
> successfully:
Thank you so much for checking! I think I'll try to compare my build to
this one, as I still have no other idea how to debug my problem. Could
you please send me resulting DTB file as well so that I can check my
build system against yours?
That said,
> Starting kernel ...
[...]
> [ 0.032394] /soc/bus@2000000/clock-controller@20c4000: Fixed
> dependency cycle(s) with /soc/bus@2000000/gpc@20dc000
> [ 0.032536] /soc/bus@2000000/gpc@20dc000: Fixed dependency cycle(s)
> with /soc/bus@2000000/clock-controller@20c4000
> [ 0.034758] /soc/bus@2000000/clock-controller@20c4000: Fixed
> dependency cycle(s) with /soc/bus@2000000/gpc@20dc000
> [ 0.034894] /soc/bus@2000000/gpc@20dc000: Fixed dependency cycle(s)
> with /soc/bus@2000000/clock-controller@20c4000
> [ 0.045375] /soc/bus@2000000/gpc@20dc000: Fixed dependency cycle(s)
> with /soc/bus@2000000/clock-controller@20c4000
> [ 0.057574] /soc/bus@2200000/spba-bus@2240000/lcdif@2220000: Fixed
> dependency cycle(s) with /panel
> [ 0.057688] /panel: Fixed dependency cycle(s) with
> /soc/bus@2200000/spba-bus@2240000/lcdif@2220000
You have these cycles as well. Is it expected? I fail to see why gpc and
clock-controller end-up being mutually dependent. Besides, they are not
mutually dependent in the hardware, or are they?
I also have a few more doubts about imx6sx.dtsi:
1. Documentation/usage-model.rst suggests "interrupt-parent = <&intc>;"
to be root node property, not of /soc as in imx6sx.dtsi. Is this
essential?
2. intc: in imx6sx.dtsi is interrupt-parent of itself? If it needs to
be, this asks for an explanation in a comment?
intc: interrupt-controller@a01000 {
compatible = "arm,cortex-a9-gic";
#interrupt-cells = <3>;
interrupt-controller;
reg = <0x00a01000 0x1000>,
<0x00a00100 0x100>;
interrupt-parent = <&intc>;
};
3. Some nodes have <&intc>, and some <&gpc> as interrupt-parent. Could
somebody please re-check if it makes sense? Besides, "gpc" is not true
interrupt controller, right?
Thanks,
-- Sergey Organov
next prev parent reply other threads:[~2025-10-01 20:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 15:49 ARM iMX6sx board fails to boot with kernel 6.17 Sergey Organov
2025-09-30 19:09 ` Fabio Estevam
2025-09-30 19:11 ` Fabio Estevam
2025-10-06 20:11 ` Sergey Organov
2025-10-06 20:20 ` Fabio Estevam
2025-10-06 21:22 ` Sergey Organov
2025-10-07 2:05 ` Fabio Estevam
2025-10-07 11:35 ` Sergey Organov
2025-10-07 15:19 ` Ulf Hansson
2025-10-07 21:17 ` Sergey Organov
2025-10-07 21:29 ` Fabio Estevam
2025-10-07 21:44 ` Fabio Estevam
2025-10-08 12:53 ` Sergey Organov
2025-10-08 17:04 ` Sergey Organov
2025-10-01 20:04 ` Sergey Organov [this message]
2025-10-02 0:45 ` Fabio Estevam
2025-10-09 14:46 ` Sergey Organov
2025-10-09 15:50 ` Fabio Estevam
2025-10-09 16:29 ` Sergey Organov
2025-10-09 17:26 ` Fabio Estevam
2025-10-09 21:51 ` Sergey Organov
2025-10-09 22:40 ` Fabio Estevam
2025-10-10 14:59 ` Sergey Organov
2025-10-10 15:14 ` Fabio Estevam
2025-10-11 20:57 ` Sergey Organov
2025-10-14 0:45 ` Fabio Estevam
2025-10-14 12:04 ` Sergey Organov
2025-10-20 21:30 ` Sergey Organov
2025-10-27 14:39 ` Sergey Organov
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=87a52afkxt.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@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.