From: "G, Manjunath Kondaiah" <manjugk@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "Varadarajan, Charulatha" <charu@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap3: Add basic support for 720MHz part
Date: Thu, 20 Jan 2011 16:50:32 +0530 [thread overview]
Message-ID: <20110120112032.GC1987@m-desktop> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59302485095F6@dbde02.ent.ti.com>
On Thu, Jan 20, 2011 at 04:28:11PM +0530, Premi, Sanjeev wrote:
> > -----Original Message-----
> > From: Varadarajan, Charulatha
> > Sent: Tuesday, January 18, 2011 2:44 PM
> > To: Premi, Sanjeev
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: [PATCH] omap3: Add basic support for 720MHz part
> >
> > Couple of minor comments.
>
> [snip]...[snip]
>
> > > --- a/arch/arm/mach-omap2/control.h
> > > +++ b/arch/arm/mach-omap2/control.h
> > > @@ -365,6 +365,13 @@
> > > #define FEAT_NEON 0
> > > #define FEAT_NEON_NONE 1
> > >
> > > +/*
> > > + * Product ID register
> > > + */
> >
> > Do not use multiline comment style for single line comments
>
> [sp] Was only following the multi-line comment stye few lines
> above...
>
> >
> > > +#define OMAP3_PRODID 0x020C
> > > +
> > > +#define OMAP3_SKUID_MASK 0x0f
> > > +#define OMAP3_SKUID_720MHZ 0x08
> > >
> > > #ifndef __ASSEMBLY__
> > > #ifdef CONFIG_ARCH_OMAP2PLUS
> > > diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
> > > index 5f9086c..53fbe01 100644
> > > --- a/arch/arm/mach-omap2/id.c
> > > +++ b/arch/arm/mach-omap2/id.c
> > > @@ -195,6 +195,15 @@ static void __init omap3_check_features(void)
> > > * TODO: Get additional info (where applicable)
> > > * e.g. Size of L2 cache.
> > > */
> > > +
> > > + /*
> > > + * Does it support 720MHz?
> > > + */
> >
> > Ditto
>
> [sp] Same here.
> But since the code is quite evident, I will remove the comment
> altogether.
>
> >
> > > + status = (OMAP3_SKUID_MASK & read_tap_reg(OMAP3_PRODID));
> > > +
> > > + if (status & OMAP3_SKUID_720MHZ) {
> > > + omap3_features |= OMAP3_HAS_720MHZ;
> > > + }
> >
> > No need of { } as there is only one line statement inside the
> > if condition.
>
> [sp] missed this.
Looks fine. Feel free to add after the above changes:
Reviewed-by: G, Manjunath Kondaiah <manjugk@ti.com>
-Manjunath
--
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
next prev parent reply other threads:[~2011-01-20 11:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 7:49 [PATCH] omap3: Add basic support for 720MHz part Sanjeev Premi
2011-01-18 9:14 ` Varadarajan, Charulatha
2011-01-20 10:58 ` Premi, Sanjeev
2011-01-20 11:12 ` Varadarajan, Charulatha
2011-01-20 11:20 ` G, Manjunath Kondaiah [this message]
2011-01-20 11:28 ` Premi, Sanjeev
2011-01-18 15:38 ` Koen Kooi
2011-01-18 16:49 ` Nishanth Menon
2011-01-18 17:18 ` Vishwanath Sripathy
2011-01-18 18:17 ` Koen Kooi
2011-01-19 8:56 ` Vishwanath Sripathy
2011-01-19 9:06 ` Nishanth Menon
2011-01-19 9:49 ` Koen Kooi
2011-01-19 10:19 ` Premi, Sanjeev
2011-01-19 9:49 ` Premi, Sanjeev
2011-01-19 9:51 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 13:07 Sanjeev Premi
2011-01-07 13:33 ` Nishanth Menon
2011-01-07 13:50 ` Premi, Sanjeev
2011-01-07 14:04 ` Nishanth Menon
2011-01-07 16:48 ` Kevin Hilman
2011-01-07 17:31 ` Premi, Sanjeev
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=20110120112032.GC1987@m-desktop \
--to=manjugk@ti.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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 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.