All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: AM3517 Failed to request pm_wkup irq
Date: Thu, 12 Jan 2023 12:20:13 +0200	[thread overview]
Message-ID: <Y7/e3WzHuSf5Km1X@atomide.com> (raw)
In-Reply-To: <CAHCN7xKqRi+MXh97gzHM1RPo9ojBDGJABN0B0jZ6zPQYe1M=TA@mail.gmail.com>

Hi,

* Adam Ford <aford173@gmail.com> [230105 18:32]:
> When booting the AM3517-EVM, I get a few errors related to the pm.
> 
> [    2.038452] pm: Failed to request pm_wkup irq
> [    2.042846] omap2_common_pm_late_init: pm soc init failed: -22
> 
> omap3_pm_init inside pm34xx.c calls omap_prcm_event_to_irq looking for
> "wkup" which returns EINVAL .
> 
> Inside omap_prm.c, there are a bunch of data structures for
> omap_prm_data which contain for various boards for AM3, AM4, omap4,
> omap5 and dra7, but a reference to ti,omap3-prm-inst appears to be
> missing.  I looked at the TRM for the AM335X, and i can clearly see a
> nice table with addresses that correspond to the tables found in
> omap_prm.c, but after looking at both a DM3730 and AM3517 TRM, I am
> not seeing a corresponding L4_WKUP Peripheral Memory map.
> 
> If someone can point me in the right direction, I can try to setup the
> OMAP3 tables accordingly.

The older SoCs set up the prm wakeup via omap3_prcm_irq_setup. Ideally
this would be nowadays done using dts and driver/irqchip though.

Maybe see omap3xxx_check_features() and try adding flags for
OMAP3_HAS_IO_WAKEUP for am3517? Likely this is the same as for 34xx.
It may also have OMAP3_HAS_IO_CHAIN_CTRL like 36xx, but likely not.

Regards,

Tony

      reply	other threads:[~2023-01-12 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 18:32 AM3517 Failed to request pm_wkup irq Adam Ford
2023-01-12 10:20 ` Tony Lindgren [this message]

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=Y7/e3WzHuSf5Km1X@atomide.com \
    --to=tony@atomide.com \
    --cc=aford173@gmail.com \
    --cc=linux-omap@vger.kernel.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.