From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] AM35x: Workaround to use generic OMAP3 hwmods
Date: Thu, 10 Mar 2011 09:39:31 +0100 [thread overview]
Message-ID: <4D788E43.4040201@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103091933260.15132@utopia.booyaka.com>
Salut Paul,
On 3/10/2011 3:37 AM, Paul Walmsley wrote:
>
> Hi,
>
> I just queued a patch to fix the SmartReflex problem. It's the part that
> fixes the incorrect data:
>
> http://marc.info/?l=linux-omap&m=129972435510631&w=2
>
> Benoît, if you are happy with it, care to send an Acked-by:? Also, I
> guess we should revisit the other part of your patch at some point.
I'm almost fine with it, but if you do not want to remove the other
masters ports of the interconnect, then you should move SR ocp_if from
slaves to masters first, like it was supposed to be during the
introduction of the SR data?
And then remove all the interconnect master list in a second patch?
Benoit
--
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-03-10 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 13:48 [RFC] AM35x: Workaround to use generic OMAP3 hwmods Sanjeev Premi
2011-02-25 17:02 ` Cousson, Benoit
2011-03-03 23:15 ` Paul Walmsley
2011-03-03 23:53 ` Paul Walmsley
2011-03-04 9:23 ` Cousson, Benoit
2011-03-04 18:41 ` Paul Walmsley
2011-03-10 2:37 ` Paul Walmsley
2011-03-10 8:39 ` Cousson, Benoit [this message]
2011-03-10 10:23 ` Cousson, Benoit
2011-03-10 11:09 ` Paul Walmsley
2011-03-11 8:33 ` 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=4D788E43.4040201@ti.com \
--to=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox