From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: Regression with e428e250fde6 on BeagleBoard Rev C2
Date: Wed, 20 Oct 2021 20:52:56 +0300 [thread overview]
Message-ID: <2e85559a-52fe-f887-51b5-4e7505ebda1e@bitmer.com> (raw)
In-Reply-To: <YUmC/xbYDnXMrsb1@atomide.com>
Hi
On 9/21/21 10:00 AM, Tony Lindgren wrote:
> * Jarkko Nikula <jarkko.nikula@bitmer.com> [210920 16:35]:
>> On 9/20/21 4:34 PM, Tony Lindgren wrote:
>>> The patch below should take us back to the earlier configuration,
>>> can you please give it a try?
>>>
>> I double checked and unfortunate it doesn't boot at all or give any
>> output when patch is applied:
>
> Hmm I tested it with copying the beagle timer configuration to omap3.dtsi
> and things worked for me. If you can, please try adding
> CONFIG_SERIAL_EARLYCON=y and then also add "debug earlyprintk" to kernel
> command line. It might show something that I'm not able to reproduce.
> Maybe there is a bootloader dependency or something like that.
>
As discussed offline recently I triple checked your first patch in this
thread on top of v5.15-rc6 and using omap2plus_defconfig (has
CONFIG_SERIAL_EARLYCON=y) and still I'm not able to get any output with
earlyprintk.
My kernel command line included "console=ttyO2,115200n8 debug
earlyprintk=ttyO2,115200n8". Plain v5.15-rc6 boots.
Could it be possible the "secure_32k_fck" clock has some system hanging
issue on my beagle? How I understand from e428e250fde6 ("ARM: dts:
Configure system timers for omap3") that "secure_32k_fck" is not
referenced explicitly but your patch here does.
Jarkko
next prev parent reply other threads:[~2021-10-20 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 17:41 Regression with e428e250fde6 on BeagleBoard Rev C2 Jarkko Nikula
2021-09-20 13:34 ` Tony Lindgren
2021-09-20 14:52 ` Andreas Kemnade
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 16:25 ` Andreas Kemnade
2021-09-20 16:35 ` Jarkko Nikula
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 17:49 ` Jarkko Nikula
2021-09-22 10:07 ` Tony Lindgren
2021-09-22 17:21 ` Jarkko Nikula
2021-09-23 5:41 ` Tony Lindgren
2021-09-23 18:03 ` Jarkko Nikula
2021-09-24 7:02 ` Tony Lindgren
2021-09-25 14:55 ` Jarkko Nikula
2021-09-30 7:04 ` Tony Lindgren
2021-10-20 17:52 ` Jarkko Nikula [this message]
2021-10-21 13:58 ` Tony Lindgren
2021-10-21 18:10 ` Jarkko Nikula
2021-10-24 6:41 ` Tony Lindgren
2021-09-20 18:19 ` H. Nikolaus Schaller
2021-09-21 7:02 ` Tony Lindgren
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=2e85559a-52fe-f887-51b5-4e7505ebda1e@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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