public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: tero.kristo@nokia.com, Kevin Hilman <khilman@deeprootsystems.com>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] adding back some features
Date: Wed, 17 Jun 2009 02:58:03 -0700	[thread overview]
Message-ID: <20090617095802.GI6605@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906170233400.3382@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [090617 01:35]:
> code comment below:
> 
> On Wed, 17 Jun 2009, Tony Lindgren wrote:
> 
> > * Kevin Hilman <khilman@deeprootsystems.com> [090615 09:05]:
> > > Kevin Hilman <khilman@deeprootsystems.com> writes:
> > > 
> > > > Tony Lindgren <tony@atomide.com> writes:
> > > >
> > > >> Hi,
> > > >>
> > > >> * Kevin Hilman <khilman@deeprootsystems.com> [090612 15:13]:
> > > >>> Here's a couple patches to add-back some feature dropped in the
> > > >>> mainline sync.  These are needed for the PM branch among other things.
> > > >>> 
> > > >>> Applies to linux-omap master.
> > > >>> 
> > > >>> Kevin Hilman (1):
> > > >>>   OMAP2/3: SoC IDs: add omap_type() for determining GP/EMU/HS
> > > >>
> > > >> Is there any reason to get this one into mainline early?
> > > >
> > > > Well, the PM branch has a dependency, but also the recenetly submitted
> > > > qwatchdog driver has a dependency.
> > > >
> > > >> If not, I suggest you keep this in your pm branch for next merge
> > > >> window that I can keep merging to l-o master as needed.
> > > >>
> > > >> However, if omap_type() is by other queues earlier, then I can
> > > >> add it into my upstream queue. If this blocks several queues
> > > >> from being rebased against mainline kernel, that alone might
> > > >> already be a good enough reason to get it in early.
> > > >
> > > > I think it should go via your upstream queue.  I imagine some of the
> > > > other upcoming driver submissions from TI will have a dependency as
> > > > well since there is still some missing EMU/HS support ind drivers.
> > > 
> > > Also, I'm carrying this SRAM patch below for HS/EMU that could go into
> > > Paul's SRAM/SDRC queue if this omap_type() gets merged sooner rather
> > > than later.
> > 
> > Hmm, the HS omap sram.c patch below for sure justifies fixing it as
> > incorrect SRAM size can cause nasty bugs.
> > 
> > Will add both omap_type and the sram.c patch below to omap-fixes.
> > 
> > Regards,
> > 
> > Tony
> >  
> > > Kevin
> > > 
> > > commit 106588e30f070d9a8d5906d409e0b9aad89edc9e
> > > Author: Tero Kristo <tero.kristo@nokia.com>
> > > Date:   Thu Oct 9 17:47:02 2008 +0300
> > > 
> > >     OMAP3: SRAM size fix for HS/EMU devices
> > >     
> > >     Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
> > >     Signed-off-by: Kevin Hilman <khilman@ti.deeprootsystems.com>
> > > 
> > > diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
> > > old mode 100644
> > > new mode 100755
> > > index 65006df..f40bd2d
> > > --- a/arch/arm/plat-omap/sram.c
> > > +++ b/arch/arm/plat-omap/sram.c
> > > @@ -131,9 +131,15 @@ void __init omap_detect_sram(void)
> > >  	if (cpu_class_is_omap2()) {
> > >  		if (is_sram_locked()) {
> > >  			if (cpu_is_omap34xx()) {
> > > -				omap_sram_base = OMAP3_SRAM_PUB_VA;
> > > -				omap_sram_start = OMAP3_SRAM_PUB_PA;
> > > -				omap_sram_size = 0x8000; /* 32K */
> > > +				if (omap_type() == OMAP2_DEVICE_TYPE_GP) {
> > > +					omap_sram_base = OMAP3_SRAM_PUB_VA;
> > > +					omap_sram_start = OMAP3_SRAM_PUB_PA;
> > > +					omap_sram_size = 0x8000; /* 32K */
> > > +				} else {
> 
> This would be better if it specifically tested for HS and EMU devices.  
> There are at least two other omap_type() possibilities here, "TEST" and 
> "BAD"

Tero, can you please repost? I will hold on sending out the omap-fixes
for that, and refresh omap-fixes with the updated patch.

Tony

 
> > > +					omap_sram_base = OMAP3_SRAM_PUB_VA;
> > > +					omap_sram_start = OMAP3_SRAM_PUB_PA;
> > > +					omap_sram_size = 0x7000; /* 28K */
> > > +				}
> > >  			} else {
> > >  				omap_sram_base = OMAP2_SRAM_PUB_VA;
> > >  				omap_sram_start = OMAP2_SRAM_PUB_PA;
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> 
> - Paul

  reply	other threads:[~2009-06-17  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 22:11 [PATCH 0/2] adding back some features Kevin Hilman
2009-06-12 22:11 ` [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining GP/EMU/HS Kevin Hilman
2009-06-12 22:11   ` [PATCH 2/2] OMAP3: DMA: Enable idlemodes for DMA OCP Kevin Hilman
2009-06-15  8:56     ` [APPLIED] " Tony Lindgren
2009-06-17  8:33   ` [APPLIED] [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining Tony Lindgren
2009-06-15  8:00 ` [PATCH 0/2] adding back some features Tony Lindgren
2009-06-15 14:55   ` Kevin Hilman
2009-06-15 16:05     ` Kevin Hilman
2009-06-17  8:31       ` Tony Lindgren
2009-06-17  8:35         ` Paul Walmsley
2009-06-17  9:58           ` Tony Lindgren [this message]
2009-06-17 13:56             ` Tero.Kristo
2009-06-17 14:04               ` Kevin Hilman
2009-06-18  0:00               ` Kevin Hilman
2009-06-17  8:39       ` [APPLIED] " Tony Lindgren

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=20090617095802.GI6605@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tero.kristo@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox