linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] bus: omap_l3_noc: Fix offset for DRA7 CLK1_HOST_CLK1_2 instance
Date: Mon, 4 May 2015 09:27:32 -0700	[thread overview]
Message-ID: <20150504162731.GO24469@atomide.com> (raw)
In-Reply-To: <1429224150-28712-1-git-send-email-nm@ti.com>

* Nishanth Menon <nm@ti.com> [150416 15:43]:
> From: Illia Smyrnov <illia.smyrnov@globallogic.com>
> 
> The base address for DRA7 CLK1_HOST_CLK1_2 host instance is
> 0x44800000, so correct offset is 0x800000. DRA7 TRM rev X(fewb 2015)
> has updates for this information.
> 
> With wrong offset these errors are not correctly cleared by the L3
> IRQ handler and cause an continuous interrupt scenario and system lockup.
> 
> Signed-off-by: Illia Smyrnov <illia.smyrnov@globallogic.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
>  drivers/bus/omap_l3_noc.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/bus/omap_l3_noc.h b/drivers/bus/omap_l3_noc.h
> index 95254585db86..a314d800f394 100644
> --- a/drivers/bus/omap_l3_noc.h
> +++ b/drivers/bus/omap_l3_noc.h
> @@ -274,7 +274,7 @@ static struct l3_flagmux_data dra_l3_flagmux_clk1 = {
>  
>  static struct l3_target_data dra_l3_target_data_clk2[] = {
>  	{0x0,	"HOST CLK1",},
> -	{0x0,	"HOST CLK2",},
> +	{0x800000, "HOST CLK2",},
>  	{0xdead, L3_TARGET_NOT_SUPPORTED,},
>  	{0x3400, "SHA2_2",},
>  	{0x0900, "BB2D",},

Applying into omap-for-v4.1/fixes thanks.

Tony

      reply	other threads:[~2015-05-04 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 22:42 [PATCH] bus: omap_l3_noc: Fix offset for DRA7 CLK1_HOST_CLK1_2 instance Nishanth Menon
2015-05-04 16:27 ` 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=20150504162731.GO24469@atomide.com \
    --to=tony@atomide.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).