linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/5] OMAP: mailbox: fix rx interrupt disable in omap4
Date: Mon, 22 Nov 2010 15:55:47 +0100	[thread overview]
Message-ID: <4CEA8473.3040404@ti.com> (raw)
In-Reply-To: <20101122100815.GM2446@legolas.emea.dhcp.ti.com>

On 11/22/2010 11:08 AM, Balbi, Felipe wrote:
> On Fri, Nov 19, 2010 at 03:50:02PM +0100, Cousson, Benoit wrote:
>> Most of the time, we do not want to use the IP revision because it is
>> un-accurate and does not reflect the change we'd like to track.
>> For example some time a minor change in the RTL that will not impact
>> the SW at all might trigger a change in the IP revision, whereas on
>> the other hand a major bug fix that will impact the SW is not capture
>> in the IP revision... yeah, that's bad, but this can happen.
>>
>> That's why we are relying on a rev field in the hwmod.
>
> But then, what's inside this rev field ? Is it some internal revision of
> hwmod or do you read from the hw ?

So far we are using a artificial SW IP revision that reflect the 
difference we'd like to highlight v1, v2.

Benoit

  parent reply	other threads:[~2010-11-22 14:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 19:15 [PATCH v3 0/5] OMAP: mailbox: enhancements and fixes Hari Kanigeri
2010-11-18 19:15 ` [PATCH v3 1/5] OMAP: mailbox: change full flag per mailbox queue instead of global Hari Kanigeri
2010-11-18 23:22   ` Cousson, Benoit
2010-11-18 19:15 ` [PATCH v3 2/5] OMAP: mailbox: fix rx interrupt disable in omap4 Hari Kanigeri
2010-11-18 23:28   ` Cousson, Benoit
2010-11-19  0:07     ` Kanigeri, Hari
2010-11-19  8:32       ` Felipe Balbi
2010-11-19 14:22         ` Kanigeri, Hari
2010-11-19 14:50           ` Cousson, Benoit
2010-11-22 10:08             ` Felipe Balbi
2010-11-22 11:46               ` Kanigeri, Hari
2010-11-22 11:51                 ` Felipe Balbi
2010-11-22 11:58                   ` Kanigeri, Hari
2010-11-22 14:57                   ` Cousson, Benoit
2010-11-22 14:55               ` Cousson, Benoit [this message]
2010-11-23  8:10                 ` Felipe Balbi
2010-11-19  8:32   ` Felipe Balbi
2010-11-18 19:15 ` [PATCH v3 3/5] OMAP: mailbox: fix checkpatch warnings Hari Kanigeri
2010-11-19  8:33   ` Felipe Balbi
2010-11-19 11:52     ` Kanigeri, Hari
2010-11-18 19:15 ` [PATCH v3 4/5] OMAP: mailbox: send message in process context Hari Kanigeri
2010-11-19  8:34   ` Felipe Balbi
2010-11-18 19:15 ` [PATCH v3 5/5] OMAP: mailbox: add notification support for multiple readers Hari Kanigeri
2010-11-19  8:50   ` Felipe Balbi
2010-11-19 11:50     ` Kanigeri, Hari
2010-11-19 12:09       ` Felipe Balbi
2010-11-19 12:29         ` Kanigeri, Hari
2010-11-19 12:53           ` Felipe Balbi
2010-11-19 13:57             ` Kanigeri, Hari
2010-11-19 14:25               ` Felipe Balbi
2010-11-19 14:44                 ` Kanigeri, Hari
2010-11-19 23:07                   ` Felipe Balbi
2010-11-20  4:01                     ` Kanigeri, Hari
2010-11-20 11:31                       ` Felipe Balbi
2010-11-20 13:26                         ` Kanigeri, Hari

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=4CEA8473.3040404@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).