From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] virtual-bus[v4]: Implementation of Virtual Bus
Date: Tue, 26 Nov 2019 19:44:29 +0000 [thread overview]
Message-ID: <0362d5f99b4948409239baf1571b2655@intel.com> (raw)
In-Reply-To: <2B0E3F215D1AB84DA946C8BEE234CCC97B3014A3@ORSMSX101.amr.corp.intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Ertman, David M
> Sent: Monday, November 18, 2019 8:07 PM
> To: 'intel-wired-lan at lists.osuosl.org' <intel-wired-lan@lists.osuosl.org>;
> Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>; Patil, Kiran
> <kiran.patil@intel.com>
> Subject: [Intel-wired-lan] virtual-bus[v4]: Implementation of Virtual Bus
>
> virtual-bus[v4]: Implementation of Virtual Bus
>
> From: Dave Ertman <david.m.ertman@intel.com>
>
> This is the initial implementation of the virtual bus, virtbus_device and
> virtbus_driver. The virtual bus is a software based bus intended to support
> registering virtbus_devices and virtbus_drivers and provide matching
> between them and probing of the registered drivers.
>
> The primary purpose of the virtual bus is to provide matching services to
> allow the use of a container_of to get access to a piece of desired data. This
> will allow two separate kernel objects to match up and start communication.
>
> The bus will support probe/remove shutdown and suspend/resume
> callbacks.
>
> Kconfig and Makefile alterations are included
>
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
> Signed-off-by: Kiran Patil <kiran.patil@intel.com>
> ---
> .../selftests/virtual_bus/virtual_bus_dev/Makefile | 7 +
> .../virtual_bus/virtual_bus_dev/virtual_bus_dev.c | 60 ++++++++++
> .../selftests/virtual_bus/virtual_bus_drv/Makefile | 7 +
> .../virtual_bus/virtual_bus_drv/virtual_bus_drv.c | 115
> ++++++++++++++++++++
> 4 files changed, 189 insertions(+)
> create mode 100644
> tools/testing/selftests/virtual_bus/virtual_bus_dev/Makefile
> create mode 100644
> tools/testing/selftests/virtual_bus/virtual_bus_dev/virtual_bus_dev.c
> create mode 100644
> tools/testing/selftests/virtual_bus/virtual_bus_drv/Makefile
> create mode 100644
> tools/testing/selftests/virtual_bus/virtual_bus_drv/virtual_bus_drv.c
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
prev parent reply other threads:[~2019-11-26 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 4:07 [Intel-wired-lan] virtual-bus[v4]: Implementation of Virtual Bus Ertman, David M
2019-11-26 19:44 ` Bowers, AndrewX [this message]
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=0362d5f99b4948409239baf1571b2655@intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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