mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 13/15] mei: bus: blacklist clients by number of connections
Date: Mon, 15 Jun 2015 21:56:53 +0300	[thread overview]
Message-ID: <1434394615-3754-14-git-send-email-tomas.winkler@intel.com> (raw)
In-Reply-To: <1434394615-3754-1-git-send-email-tomas.winkler@intel.com>

Currently we support only clients with single connection
and fixed address clients so all other clients are blacklisted

Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---
 drivers/misc/mei/bus-fixup.c | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/drivers/misc/mei/bus-fixup.c b/drivers/misc/mei/bus-fixup.c
index 9a1a0d635bd3..46d27d92db3f 100644
--- a/drivers/misc/mei/bus-fixup.c
+++ b/drivers/misc/mei/bus-fixup.c
@@ -33,6 +33,24 @@
 #define MEI_UUID_ANY NULL_UUID_LE
 
 /**
+ * number_of_connections - determine whether an client be on the bus
+ *    according number of connections
+ *    We support only clients:
+ *       1. with single connection
+ *       2. and fixed clients (max_number_of_connections == 0)
+ *
+ * @cldev: me clients device
+ */
+static void number_of_connections(struct mei_cl_device *cldev)
+{
+	dev_dbg(&cldev->dev, "running hook %s on %pUl\n",
+			__func__, mei_me_cl_uuid(cldev->me_cl));
+
+	if (cldev->me_cl->props.max_number_of_connections > 1)
+		cldev->do_match = 0;
+}
+
+/**
  * blacklist - blacklist a client from the bus
  *
  * @cldev: me clients device
@@ -434,6 +452,7 @@ static struct mei_fixup {
 	const uuid_le uuid;
 	void (*hook)(struct mei_cl_device *cldev);
 } mei_fixups[] = {
+	MEI_FIXUP(MEI_UUID_ANY, number_of_connections),
 	MEI_FIXUP(MEI_UUID_NFC_INFO, blacklist),
 };
 
-- 
2.4.3


  parent reply	other threads:[~2015-06-15 18:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 18:56 [char-misc-next 00/15 V2] revamp mei bus Tomas Winkler
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 ` Tomas Winkler [this message]
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-14-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®