All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hiremath, Vaibhav" <hvaibhav@ti.com>
To: "Hunter, Jon" <jon-hunter@ti.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: RE: [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't call _init_mpu_rt_base if no sysc
Date: Fri, 12 Apr 2013 06:18:04 +0000	[thread overview]
Message-ID: <79CD15C6BA57404B839C016229A409A83EC4EC9F@DBDE01.ent.ti.com> (raw)
In-Reply-To: <51661613.4070405@ti.com>

> -----Original Message-----
> From: Hunter, Jon
> Sent: Thursday, April 11, 2013 7:17 AM
> To: Shilimkar, Santosh
> Cc: Cousson, Benoit; linux-omap@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; tony@atomide.com; Hiremath, Vaibhav
> Subject: Re: [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't call
> _init_mpu_rt_base if no sysc
> 
> 
> On 03/19/2013 08:30 AM, Santosh Shilimkar wrote:
> > OMAP hwmod layer does the reset of the IPs in early code so that
> > we have SOC in sane state. To do the soft-reset, it needs to
> ioremap()
> > the ip address space to be able to write to sysconfig registers.
> >
> > But there are few hwmod which doesn't have sysconfig registers and
> hence
> > no need to ioremap() them in early init code.
> >
> > So this patch makes prevet calling the _init_mpu_rt_base()
> conditional
> > based on sysc availability.
> >
> > Cc: Benoit Cousson <b-cousson@ti.com>
> >
> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > ---
> >  arch/arm/mach-omap2/omap_hwmod.c |    3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-
> omap2/omap_hwmod.c
> > index 4501038..1a1f0a4 100644
> > --- a/arch/arm/mach-omap2/omap_hwmod.c
> > +++ b/arch/arm/mach-omap2/omap_hwmod.c
> > @@ -2449,7 +2449,8 @@ static int __init _init(struct omap_hwmod *oh,
> void *data)
> >  	if (oh->_state != _HWMOD_STATE_REGISTERED)
> >  		return 0;
> >
> > -	_init_mpu_rt_base(oh, NULL);
> > +	if (oh->class->sysc)
> > +		_init_mpu_rt_base(oh, NULL);
> >
> >  	r = _init_clocks(oh, NULL);
> >  	if (IS_ERR_VALUE(r)) {
> 
> I have not looked into why, but this commit is triggering the following
> panic on am335x-evm. I don't see this on the omap platforms only
> am335x.
> 
> Adding Vaibhav ...
> 
I think I have already fixed this, can you try applying below patches

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg87524.html


Thanks,
Vaibhav



Thanks,
Vaibhav

WARNING: multiple messages have this Message-ID (diff)
From: hvaibhav@ti.com (Hiremath, Vaibhav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't call _init_mpu_rt_base if no sysc
Date: Fri, 12 Apr 2013 06:18:04 +0000	[thread overview]
Message-ID: <79CD15C6BA57404B839C016229A409A83EC4EC9F@DBDE01.ent.ti.com> (raw)
In-Reply-To: <51661613.4070405@ti.com>

> -----Original Message-----
> From: Hunter, Jon
> Sent: Thursday, April 11, 2013 7:17 AM
> To: Shilimkar, Santosh
> Cc: Cousson, Benoit; linux-omap at vger.kernel.org; linux-arm-
> kernel at lists.infradead.org; tony at atomide.com; Hiremath, Vaibhav
> Subject: Re: [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't call
> _init_mpu_rt_base if no sysc
> 
> 
> On 03/19/2013 08:30 AM, Santosh Shilimkar wrote:
> > OMAP hwmod layer does the reset of the IPs in early code so that
> > we have SOC in sane state. To do the soft-reset, it needs to
> ioremap()
> > the ip address space to be able to write to sysconfig registers.
> >
> > But there are few hwmod which doesn't have sysconfig registers and
> hence
> > no need to ioremap() them in early init code.
> >
> > So this patch makes prevet calling the _init_mpu_rt_base()
> conditional
> > based on sysc availability.
> >
> > Cc: Benoit Cousson <b-cousson@ti.com>
> >
> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > ---
> >  arch/arm/mach-omap2/omap_hwmod.c |    3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-
> omap2/omap_hwmod.c
> > index 4501038..1a1f0a4 100644
> > --- a/arch/arm/mach-omap2/omap_hwmod.c
> > +++ b/arch/arm/mach-omap2/omap_hwmod.c
> > @@ -2449,7 +2449,8 @@ static int __init _init(struct omap_hwmod *oh,
> void *data)
> >  	if (oh->_state != _HWMOD_STATE_REGISTERED)
> >  		return 0;
> >
> > -	_init_mpu_rt_base(oh, NULL);
> > +	if (oh->class->sysc)
> > +		_init_mpu_rt_base(oh, NULL);
> >
> >  	r = _init_clocks(oh, NULL);
> >  	if (IS_ERR_VALUE(r)) {
> 
> I have not looked into why, but this commit is triggering the following
> panic on am335x-evm. I don't see this on the omap platforms only
> am335x.
> 
> Adding Vaibhav ...
> 
I think I have already fixed this, can you try applying below patches

http://www.mail-archive.com/linux-omap at vger.kernel.org/msg87524.html


Thanks,
Vaibhav



Thanks,
Vaibhav

  reply	other threads:[~2013-04-12  6:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 13:30 [PATCH v2 00/11] ARM: dts: OMAP5: ocp address space and few updates for 3.10 Santosh Shilimkar
2013-03-19 13:30 ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 01/11] ARM: dts: omap5-evm: Update available memory to 2032 MB Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 02/11] ARM: dts: OMAP5: Align the local timer dt node as per the current binding code Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 03/11] ARM: dts: OMAP5: Specify nonsecure PPI IRQ for arch timer Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 04/11] ARM: dts: OMAP5: Move the gic node out of ocp space Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 05/11] ARM: dts: OMAP5: Update the timer and gic nodes for HYP kernel support Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 06/11] ARM: dts: OMAP5: Update keypad reg property Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 07/11] Documentation: dt: OMAP: l3-noc: Add *reg* in required properties Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 08/11] ARM: dts: OMAP4/5: Update l3-noc dt nodes Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 09/11] ARM: dts: OMAP5: Add watchdog timer node Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 10/11] ARM: OMAP2+: hwmod: extract module address space from DT blob Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-03-19 13:30 ` [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't call _init_mpu_rt_base if no sysc Santosh Shilimkar
2013-03-19 13:30   ` Santosh Shilimkar
2013-04-11  1:46   ` Jon Hunter
2013-04-11  1:46     ` Jon Hunter
2013-04-12  6:18     ` Hiremath, Vaibhav [this message]
2013-04-12  6:18       ` Hiremath, Vaibhav
2013-03-26 14:31 ` [PATCH v2 00/11] ARM: dts: OMAP5: ocp address space and few updates for 3.10 Benoit Cousson
2013-03-26 14:31   ` Benoit Cousson
2013-03-26 14:47   ` Santosh Shilimkar
2013-03-26 14:47     ` Santosh Shilimkar

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=79CD15C6BA57404B839C016229A409A83EC4EC9F@DBDE01.ent.ti.com \
    --to=hvaibhav@ti.com \
    --cc=b-cousson@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --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 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.