From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Siva Yerramreddy <yshivakrishna@gmail.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH char-misc-next v3 2/8] misc: mic: add a bus driver for virtual MIC devices
Date: Fri, 11 Jul 2014 18:27:20 -0700 [thread overview]
Message-ID: <20140712012720.GA31863@kroah.com> (raw)
In-Reply-To: <9f7cf168a23057b5a1a251f79e004bd449f9cb59.1405109402.git.sudeep.dutt@intel.com>
On Fri, Jul 11, 2014 at 02:04:20PM -0700, Sudeep Dutt wrote:
> This MIC virtual bus driver takes the responsibility of creating all
> the virtual devices connected to the PCIe device on the host and the
> platform device on the card. The MIC bus hardware operations provide
> a way to abstract certain hardware details from the base physical devices.
> Examples of devices added on the MIC virtual bus include host DMA and card DMA.
> This abstraction enables using a common DMA driver on host and card.
>
> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Reviewed-by: Nikhil Rao <nikhil.rao@intel.com>
> Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.com>
> Signed-off-by: Siva Yerramreddy <yshivakrishna@gmail.com>
> ---
> drivers/misc/mic/Kconfig | 17 ++++
> drivers/misc/mic/Makefile | 1 +
> drivers/misc/mic/bus/Makefile | 5 +
> drivers/misc/mic/bus/mic_bus.c | 218 +++++++++++++++++++++++++++++++++++++++++
> include/linux/mic_bus.h | 110 +++++++++++++++++++++
> 5 files changed, 351 insertions(+)
> create mode 100644 drivers/misc/mic/bus/Makefile
> create mode 100644 drivers/misc/mic/bus/mic_bus.c
> create mode 100644 include/linux/mic_bus.h
Looks good, but no addition to scripts/mod/file2alias.c to allow
autoloading of mic_bus drivers?
I'll take patches 1 and 2 here, as I need some acks from the DMA people
on patch 3.
thanks,
greg k-h
next prev parent reply other threads:[~2014-07-12 1:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 21:04 [PATCH char-misc-next v3 0/8] Enable dma driver for MIC X100 Coprocessors Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 1/8] misc: mic: Add mic bus and dma driver documentation Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 2/8] misc: mic: add a bus driver for virtual MIC devices Sudeep Dutt
2014-07-12 1:27 ` Greg Kroah-Hartman [this message]
2014-07-12 1:31 ` Greg Kroah-Hartman
2014-07-12 6:49 ` Sudeep Dutt
2014-07-12 16:58 ` Greg Kroah-Hartman
2014-07-11 21:04 ` [PATCH char-misc-next v3 3/8] dma: MIC X100 DMA Driver Sudeep Dutt
2014-07-14 8:07 ` Paul Bolle
2014-07-14 14:46 ` Greg Kroah-Hartman
2014-07-11 21:04 ` [PATCH char-misc-next v3 4/8] misc: mic: add threaded irq support in host driver Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 5/8] misc: mic: add dma " Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 6/8] misc: mic: add threaded irq support in card driver Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 7/8] misc: mic: add dma " Sudeep Dutt
2014-07-11 21:04 ` [PATCH char-misc-next v3 8/8] misc: mic: add support for loading/unloading dma driver Sudeep Dutt
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=20140712012720.GA31863@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashutosh.dixit@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=sudeep.dutt@intel.com \
--cc=yshivakrishna@gmail.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
Powered by JetHome