public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Anson Huang <Anson.Huang@nxp.com>
Subject: Re: ARM iMX6sx board fails to boot with kernel 6.17
Date: Tue, 07 Oct 2025 14:35:52 +0300	[thread overview]
Message-ID: <87ldlngd0n.fsf@osv.gnss.ru> (raw)
In-Reply-To: <CAOMZO5Dvc9AhudPkEuM6BL7F4n=5S4M6d52jzomWnJvCOWVaaQ@mail.gmail.com> (Fabio Estevam's message of "Mon, 6 Oct 2025 23:05:06 -0300")

Fabio Estevam <festevam@gmail.com> writes:

> On Mon, Oct 6, 2025 at 6:22 PM Sergey Organov <sorganov@gmail.com> wrote:
>
>> It is built form multiple .dtsi, so I figure I attach the one after
>> pre-processing stage. Please let me know if you'd prefer I rather
>> manually insert all the custom .dtsi into a single .dts, and send that
>> one instead.
>
> This format is hard to follow.
>
> To make things easier for debugging, you could create a minimal board
> dts file with only UART and eMMC nodes to reproduce the problem.
>
> It's not clear to me the relationship between the ANATOP regulators
> and the eMMC power on your board.

Thanks, Fabio! OK, I'll do, re-check, and get back to you.

-- Sergey Organov


  reply	other threads:[~2025-10-07 11:35 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 [this message]
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
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=87ldlngd0n.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=Anson.Huang@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox