From: Tony Lindgren <tony@atomide.com>
To: "Pedanekar, Hemant" <hemantp@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Subject: Re: [PATCH v2 3/6] TI816X: Update common OMAP machine specific sources
Date: Fri, 10 Dec 2010 17:51:03 -0800 [thread overview]
Message-ID: <20101211015103.GC3054@atomide.com> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B036A17C7A5@dbde02.ent.ti.com>
* Pedanekar, Hemant <hemantp@ti.com> [101210 16:58]:
> Tony Lindgren wrote on Monday, December 06, 2010 10:23 PM:
>
> [...]
> >> Similarly, we will also need to add TI816X specific hwmods.
> >>
> >> 4) TI816X series shares similarity with OMAP4 too - e.g., various IPs are
> >> same, CM module is closer to OMAP4 than OMAP3. Thus, regaring (1) above, I
> >> could use OMAP4 code instead of adding new "else if". Of course, again,
> >> there are above mentioned differences too.
> >
> > We really want to use same code for the shared modules so
> > using feature
> > based detection is the way to go.
> >
> Tony,
>
> Just wanted to confirm: so you are suggesting we do not have any
> cpu_is_ti81xx() check in the code - is that correct?
We can have that, but we should avoid it where possible.
And ideally cpu_is_ti81xx() would be just something like:
#define cpu_is_ti81xx() \\
cpu_is_omap34xx() && omap_has_aaa() && omap_has_bbb()
Regards,
Tony
next prev parent reply other threads:[~2010-12-11 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 17:11 [PATCH v2 3/6] TI816X: Update common OMAP machine specific sources Hemant Pedanekar
2010-09-16 22:25 ` Tony Lindgren
2010-10-22 18:07 ` Pedanekar, Hemant
2010-11-05 20:59 ` Tony Lindgren
2010-11-29 17:17 ` Pedanekar, Hemant
2010-11-29 19:29 ` Tony Lindgren
2010-12-01 1:46 ` Pedanekar, Hemant
2010-12-06 16:53 ` Tony Lindgren
2010-12-11 0:58 ` Pedanekar, Hemant
2010-12-11 1:51 ` Tony Lindgren [this message]
2010-12-11 1:53 ` Pedanekar, Hemant
2010-12-04 0:20 ` Pedanekar, Hemant
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=20101211015103.GC3054@atomide.com \
--to=tony@atomide.com \
--cc=hemantp@ti.com \
--cc=khilman@deeprootsystems.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.