All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC PATCH] arm:omap: cleanup & split omap2/3/4_check_revision function
Date: Wed, 7 Dec 2011 15:41:19 -0800	[thread overview]
Message-ID: <20111207234119.GQ31337@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A803D9D5@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [111122 21:56]:
> > 
> > This patch doesn't change functionality or behavior of the code
> > execution; it barely cleans up the code and splits into SoC
> > specific implementation for ID and feature detection; makes
> > easier to add new SoC (especially for AM devices where we do not have
> > feature register).
...
 
> If there are not review comments, can this be merged?

Sorry for the delay, the idea is good now that we don't need the
revision check super early any longer. Few comments below.
 
> > --- a/arch/arm/mach-omap2/id.c
> > +++ b/arch/arm/mach-omap2/id.c
> > @@ -226,9 +226,9 @@ static void __init omap4_check_features(void)
> >  	}
> >  }
> > 
> > -static void __init ti816x_check_features(void)
> > +static void __init omap3_add_def_features(void)
> >  {
> > -	omap_features = OMAP3_HAS_NEON;
> > +	omap_features = OMAP3_HAS_NEON | OMAP3_HAS_L2CACHE;
> >  }
> > 
> >  static void __init omap3_check_revision(const char **cpu_rev)

Can you please split this patch a bit? First a patch that does not
change the behaviour except adds the SoC specific revision checks.

> > @@ -393,6 +394,7 @@ void __init omap2430_init_early(void)
> >  void __init omap3_init_early(void)
> >  {
> >  	omap2_set_globals_3xxx();
> > +	omap3xxx_check_revision(true);
> >  	omap_common_init_early();
> >  	omap3xxx_voltagedomains_init();
> >  	omap3xxx_powerdomains_init();
> > @@ -425,6 +427,7 @@ void __init am35xx_init_early(void)
> >  void __init ti816x_init_early(void)
> >  {
> >  	omap2_set_globals_ti816x();
> > +	omap3xxx_check_revision(false);
> >  	omap_common_init_early();
> >  	omap3xxx_voltagedomains_init();
> >  	omap3xxx_powerdomains_init();

Maybe just call ti816x_check_features separately?

	omap3xxx_check_revision();
	omap3xxx_check_features();
and
	omap3xxx_check_revision();
	ti816x_check_features();	

Regards,

Tony

  reply	other threads:[~2011-12-07 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 14:43 [RFC PATCH] arm:omap: cleanup & split omap2/3/4_check_revision function Vaibhav Hiremath
2011-11-16 14:06 ` Hiremath, Vaibhav
2011-11-23  6:31 ` Hiremath, Vaibhav
2011-12-07 23:41   ` Tony Lindgren [this message]
2011-12-08 13:40     ` Hiremath, Vaibhav
2011-12-08 17:14       ` 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=20111207234119.GQ31337@atomide.com \
    --to=tony@atomide.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.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 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.