From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: David Russell <david.russell73@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [EXTERNAL] OMAP2430 kernel hangs on ioremap of IVA2.1 addresses
Date: Wed, 9 Jun 2021 09:20:39 +0300 [thread overview]
Message-ID: <YMBdt8dDdvySofuC@atomide.com> (raw)
In-Reply-To: <cb562f9f798d4431a09f19e8efd24727@ti.com>
Hi,
* Woodruff, Richard <r-woodruff2@ti.com> [210607 15:40]:
> Guess: this bit in JTAG script used for IVA tests probably is missing and needs to be worked in. The generic linux-omap clock code probably handles the IVA clock but maybe not the resets.
>
> /* Enable IVA-ss functional clock (set bit 0) */
> (*(int*)0x49006800) |= 0x1;
>
> /* Release l3s_idle_req */
> (*(int*)0x49006810) |= (1 << 1);
>
> /* Release L3S reset and power-on reset (clear bit 1) at the same time */
> (*(int*)0x49006850) &= ~(( 1 << 1));
Heh and I thought nobody is using 2430 any longer :)
FYI, the current mainline kernel actually can deal with all that using
reset driver and genpd, see for example commits:
ae57d1558908 ("ARM: dts: Configure interconnect target module for dra7 iva")
effe89e40037 ("soc: ti: omap-prm: Fix occasional abort on reset deassert for dra7 iva")
Similar setup should also work for 2430 but needs the power domains
configured for drivers/soc/ti/omap_prm.c at least for iva.
David, I think what you're seeing is iva getting released from reset with
an unconfigured MMU, and then the system will hang.
Regards,
Tony
next prev parent reply other threads:[~2021-06-09 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:01 OMAP2430 kernel hangs on ioremap of IVA2.1 addresses David Russell
2021-06-07 15:40 ` [EXTERNAL] " Woodruff, Richard
2021-06-09 6:20 ` Tony Lindgren [this message]
2021-06-09 12:11 ` David Russell
2021-06-11 4:43 ` Tony Lindgren
2021-08-11 12:54 ` David Russell
2021-08-11 14:17 ` Woodruff, Richard
2021-08-12 6:32 ` Tony Lindgren
2021-08-12 19:05 ` Woodruff, Richard
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=YMBdt8dDdvySofuC@atomide.com \
--to=tony@atomide.com \
--cc=david.russell73@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.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 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.