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>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Andreas Kemnade <andreas@kemnade.info>
Subject: Re: Regression with e428e250fde6 on BeagleBoard Rev C2
Date: Wed, 22 Sep 2021 20:21:22 +0300 [thread overview]
Message-ID: <cbe53e9f-b407-d758-67bb-5fb65bddfc03@bitmer.com> (raw)
In-Reply-To: <YUsAffFIHUi1ZxEY@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On 9/22/21 1:07 PM, Tony Lindgren wrote:
>> Hmm.. no luck on top of d5f6545934c4 ("qnx4: work around gcc false
>> positive warning bug") with the patch. Nothing gets printed after
>> "Starting kernel ...". Without the patch boots fine.
>
> OK interesting. Best to keep the booting quirk handling for beagle
> rev a to b4 then. No reason to keep the timer quirks for rev b5 and c
> boards though.
>
> Can you try the following patch that removes the quirks for omap3-beagle
> by default?
>
> The patch also adds a new omap3-beagle-ab4.dts that keeps the current
> quirks and also limits the pmic capabilities for the old known buggy
> boards.
>
Better luck with this one but looks like idling cause "undefined
instruction" crash. Cache/memory etc corruption perhaps? Serial console
log attached.
I used the new omap3-beagle-ab4.dtb:
cat arch/arm/boot/dts/omap3-beagle-ab4.dtb >>arch/arm/boot/zImage; ma
LOADADDR=0x80008000 uImage
> I also noticed that omap3-beagle.dts is missing the twl power node
> probably because of the rev a to b4 quirks.
>
> Adding the twl power node with "ti,twl4030-power-idle-osc-off" similar
> to beagle xm might produce some nice power savings after the quirks are
> gone :)
>
> Needs to be tested with kernel serial console detached and serial
> port autoidle configured. That's a different patch for sure.
>
I guess the timer change would be the fix and twl changes for normal
development cycle?
Jarkko
[-- Attachment #2: minicom.cap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 18158 bytes --]
next prev parent reply other threads:[~2021-09-22 17:21 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 [this message]
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
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=cbe53e9f-b407-d758-67bb-5fb65bddfc03@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=andreas@kemnade.info \
--cc=hns@goldelico.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