linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: Fix I/O chain clock line assertion timed out error
Date: Fri, 12 Sep 2014 13:39:41 -0500	[thread overview]
Message-ID: <20140912183941.GA15272@kahuna> (raw)
In-Reply-To: <1410544222-25913-1-git-send-email-tony@atomide.com>

On 10:50-20140912, Tony Lindgren wrote:
> We are getting "PRM: I/O chain clock line assertion timed out" errors
> on early omaps for device tree based booting. This is because we are
> unconditionally calling reconfigure_io_chain while legacy booting
> has omap3_has_io_chain_ctrl() checks in place in omap_hwmod.c.
> 
> For device tree based booting, we are calling reconfigure_io_chain
> unconditionally from pinctrl framework. So we need to add a check for
> omap3_has_io_chain_ctrl() to avoid the errors for trying to access
> a register that does not exist.
> 
> For es3.0, the documentation in "4.11.2 Device Off-Mode Configuration"
> just mentions PM_WKEN_WKUP[8] bit. For es3.1, there's a new chapter in
> documentation for "4.11.2.2 I/O Wake-Up Mechanism" that describes the
> PM_WKEN_WKUP[16] ST_IO_CHAIN bit. So PM_WKEN_WKUP[16] bit did not get
> added until in es3.1 probaly to fix issues with flakey wake-up events.
> 
> We are doing proper checks for ST_IO_CHAIN already in id.c and with
> omap3_has_io_chain_ctrl(). For more information, see also commit
> b02b917211d5 ("ARM: OMAP3: PM: fix I/O wakeup and I/O chain clock
> control detection").
> 
> Let's fix the issue by selecting the right function during init for
> reconfigure_io_chain depending on the omap revision. For es3.0 and
> earlier we need to just toggle EN_IO. By doing this, we can move the
> check for omap3_has_io_chain_ctrl() from omap_hwmod.c to the init code
> in prm_3xxx.c. And then we can unconditionally call reconfigure_io_chain.
> 
> Thanks to Paul Walmsley and Nishanth Menon for help with debugging the
> issue.
> 
> Fixes: 30a69ef785e8 ("ARM: OMAP: Move DT wake-up event handling over to use pinctrl-single-omap")
> Cc: Kevin Hilman <khilman@kernel.org>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
Reviewed-by: Nishanth Menon <nm@ti.com>

-- 
Regards,
Nishanth Menon

      reply	other threads:[~2014-09-12 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 17:50 [PATCH] ARM: OMAP3: Fix I/O chain clock line assertion timed out error Tony Lindgren
2014-09-12 18:39 ` Nishanth Menon [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=20140912183941.GA15272@kahuna \
    --to=nm@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).