From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jianyun Li <jianyunff@gmail.com>
Cc: James.Bottomley@suse.de, Jianyun Li <jyli@marvell.com>,
"open list:SCSI SUBSYSTEM" <linux-scsi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v2] Add Marvell UMI driver
Date: Mon, 9 May 2011 12:20:51 -0700 [thread overview]
Message-ID: <20110509122051.33f1672f@jbarnes-desktop> (raw)
In-Reply-To: <1304943577-2876-1-git-send-email-jianyunff@gmail.com>
On Mon, 9 May 2011 20:19:33 +0800
Jianyun Li <jianyunff@gmail.com> wrote:
> The Marvell Universal Message Interface (UMI) defines a messaging
> interface between host and Marvell products (Plato, for example). It
> considers situations of limited system resource and optimized system
> performance.
> UMI driver translates host request to message and sends message
> to FW via UMI, FW receives message and processes it, then sends response
> to UMI driver.
> FW generates an interrupt when it needs to send information or
> response to UMI driver
>
Unless you're using the PCI ID outside of this driver, you can just put
it in your header file rather than pci_ids.h, which is meant for IDs
that are shared between modules.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-05-09 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Message-Id>
2011-05-09 12:19 ` [PATCH v2] Add Marvell UMI driver Jianyun Li
2011-05-09 19:20 ` Jesse Barnes [this message]
2011-05-09 21:23 ` Rolf Eike Beer
2011-05-11 13:17 ` li jianyun
2011-05-11 15:22 ` [PATCH v3] " jianyunff
2011-06-14 2:33 ` li jianyun
2011-08-15 11:10 ` li jianyun
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=20110509122051.33f1672f@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=James.Bottomley@suse.de \
--cc=jianyunff@gmail.com \
--cc=jyli@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@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 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).