public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-omap@vger.kernel.org
Subject: Re: [RESUBMIT][PATCH 5/7] OMAP4: Update common omap machine specific sources.
Date: Sat, 16 May 2009 08:35:16 -0700	[thread overview]
Message-ID: <20090516153515.GL19742@atomide.com> (raw)
In-Reply-To: <20090516101106.GL15328@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [090516 03:12]:
> On Thu, May 07, 2009 at 11:59:14AM +0530, Santosh Shilimkar wrote:
> > @@ -196,7 +199,10 @@ void __init omap2_check_revision(void)
> >  	 * At this point we have an idea about the processor revision set
> >  	 * earlier with omap2_set_globals_tap().
> >  	 */
> > -	if (cpu_is_omap24xx())
> > +	if (cpu_is_omap44xx()) {
> > +		printk(KERN_INFO "FIXME: CPU revision = OMAP4430\n");
> > +		return;
> > +	} else if (cpu_is_omap24xx())
> 
> Can we keep things here in numeric order?  So leave cpu_is_omap24xx()
> at the top and add the additional omap44xx stuff at the bottoom.
> 
> > @@ -30,7 +32,9 @@
> >  #include <mach/sdrc.h>
> >  #include <mach/gpmc.h>
> >  
> > +#ifndef CONFIG_ARCH_OMAP4	/* FIXME: Remove this once clkdev is ready */
> >  #include "clock.h"
> > +#endif
> 
> Hmm.  Tony: we really need to eliminate data inside header files.  It's
> not nice to have data structures created by merely including some header
> file that also contains function prototypes.

Yeh, we should just move the clocks from clock24xx.h to the top of clock24xx.c,
and the same thing for clock34xx.h. I think those are the only remaining
places with data in header files.

Regards,

Tony

  reply	other threads:[~2009-05-16 15:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  6:29 [RESUBMIT][PATCH 1/7] OMAP4: Create architecture macros and config entries Santosh Shilimkar
2009-05-07  6:29 ` [RESUBMIT][PATCH 2/7] OMAP4: Create board support for OMAP_4430SDP Santosh Shilimkar
2009-05-07  6:29   ` [RESUBMIT][PATCH 3/7] OMAP4: Update common omap platform headers Santosh Shilimkar
2009-05-07  6:29     ` [RESUBMIT][PATCH 4/7] OMAP4: Update common omap platform common sources Santosh Shilimkar
2009-05-07  6:29       ` [RESUBMIT][PATCH 5/7] OMAP4: Update common omap machine specific sources Santosh Shilimkar
2009-05-07  6:29         ` [RESUBMIT][PATCH 6/7] OMAP4: Clock stubs since clock management framework not in Santosh Shilimkar
2009-05-07  6:29           ` [RESUBMIT][PATCH 7/7] Enable build for OMAP4 Santosh Shilimkar
2009-05-16 10:14           ` [RESUBMIT][PATCH 6/7] OMAP4: Clock stubs since clock management framework not in Russell King - ARM Linux
2009-05-16 20:21             ` Shilimkar, Santosh
2009-05-16 10:07         ` [RESUBMIT][PATCH 5/7] OMAP4: Update common omap machine specific sources Russell King - ARM Linux
2009-05-16 20:17           ` Shilimkar, Santosh
2009-05-17 13:00           ` Shilimkar, Santosh
2009-05-17 15:32             ` Russell King - ARM Linux
2009-05-18  3:59               ` Shilimkar, Santosh
2009-05-16 10:11         ` Russell King - ARM Linux
2009-05-16 15:35           ` Tony Lindgren [this message]
2009-05-16  9:53       ` [RESUBMIT][PATCH 4/7] OMAP4: Update common omap platform common sources Russell King - ARM Linux
2009-05-16 20:04         ` Shilimkar, Santosh
2009-05-18 15:50           ` Tony Lindgren
2009-05-18 15:52             ` Shilimkar, Santosh
2009-05-18 12:07         ` Shilimkar, Santosh
2009-05-18 12:15           ` Russell King - ARM Linux
2009-05-16  9:30     ` [RESUBMIT][PATCH 3/7] OMAP4: Update common omap platform headers Russell King - ARM Linux
2009-05-16  9:27   ` [RESUBMIT][PATCH 2/7] OMAP4: Create board support for OMAP_4430SDP Russell King - ARM Linux
2009-05-17  6:36     ` Shilimkar, Santosh

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=20090516153515.GL19742@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=santosh.shilimkar@ti.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