From: Tomas Winkler <tomas.winkler@intel.com>
To: gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [char-misc-next 00/15 V2] revamp mei bus
Date: Mon, 15 Jun 2015 21:56:40 +0300 [thread overview]
Message-ID: <1434394615-3754-1-git-send-email-tomas.winkler@intel.com> (raw)
MEI bus was designed around nfc and was hard to extend.
Instead of hard coded way of adding the devices on the mei bus
we scan whole me client list and create a device for each
eligible me client
V2: Rephrase the commit message of most of the patches
Remove few patches that didn't bring substantial changes.
Split few patches to follow single change per patch policy.
Tomas Winkler (15):
mei: bus: fix drivers and devices names confusion
mei: bus: rename nfc.c to bus-fixup.c
mei: bus: move driver api functions at the start of the file
mei: bus: rename uevent handler to mei_cl_device_uevent
mei: bus: don't enable events implicitly in device enable
mei: bus: report if event registration failed
mei: bus: revamp device matching
mei: bus: revamp probe and remove functions
mei: bus: add reference to bus device in struct mei_cl_client
mei: bus: add me client device list infrastructure
mei: bus: enable running fixup routines before device registration
mei: bus: blacklist nfc info client
mei: bus: blacklist clients by number of connections
mei: bus: simplify how we build nfc bus name
mei: bus: link client devices instead of host clients
drivers/misc/mei/Makefile | 2 +-
drivers/misc/mei/bus-fixup.c | 306 ++++++++++++++
drivers/misc/mei/bus.c | 967 ++++++++++++++++++++++++++++---------------
drivers/misc/mei/client.c | 9 +-
drivers/misc/mei/init.c | 3 +-
drivers/misc/mei/mei_dev.h | 25 +-
drivers/misc/mei/nfc.c | 414 ------------------
include/linux/mei_cl_bus.h | 11 +
8 files changed, 955 insertions(+), 782 deletions(-)
create mode 100644 drivers/misc/mei/bus-fixup.c
delete mode 100644 drivers/misc/mei/nfc.c
--
2.4.3
next reply other threads:[~2015-06-15 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 18:56 Tomas Winkler [this message]
2015-06-15 18:56 ` [char-misc-next 01/15 V2] mei: bus: fix drivers and devices names confusion Tomas Winkler
2015-07-23 4:30 ` Greg KH
2015-06-15 18:56 ` [char-misc-next 02/15 V2] mei: bus: rename nfc.c to bus-fixup.c Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 03/15 V2] mei: bus: move driver api functions at the start of the file Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 04/15] mei: bus: rename uevent handler to mei_cl_device_uevent Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 05/15 V2] mei: bus: don't enable events implicitly in device enable Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 06/15 V2] mei: bus: report if event registration failed Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 07/15 V2] mei: bus: revamp device matching Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 08/15 V2] mei: bus: revamp probe and remove functions Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 09/15 V2] mei: bus: add reference to bus device in struct mei_cl_client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 10/15 V2] mei: bus: add me client device list infrastructure Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 11/15 V2] mei: bus: enable running fixup routines before device registration Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 12/15] mei: bus: blacklist the nfc info client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 13/15] mei: bus: blacklist clients by number of connections Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 14/15 V2] mei: bus: simplify how we build nfc bus name Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 15/15 V2] mei: bus: link client devices instead of host clients Tomas Winkler
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=1434394615-3754-1-git-send-email-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®