From: christopher.lee.bostic@gmail.com
To: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
gregkh@linuxfoundation.org, mturquette@baylibre.com,
geert+renesas@glider.be, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, joel@jms.id.au,
jk@ozlabs.org, linux-kernel@vger.kernel.org, andrew@aj.id.au,
alistair@popple.id.au, benh@kernel.crashing.org
Cc: Chris Bostic <cbostic@us.ibm.com>
Subject: [PATCH v2 13/18] drivers/fsi: Remove all scanned devices during master unregister
Date: Thu, 12 Jan 2017 16:34:09 -0600 [thread overview]
Message-ID: <1484260449-80182-1-git-send-email-christopher.lee.bostic@gmail.com> (raw)
From: Chris Bostic <cbostic@us.ibm.com>
Master will remove all previously scanned devices during an
unregister operation. This will be necessary should any master
attempt to register more than once.
Signed-off-by: Chris Bostic <cbostic@us.ibm.com>
---
V2 - Remove list heads and explicit master device list management
int the fsi master and fsi slave structs. Instead utilize the
device_for_each_child method already available.
---
drivers/fsi/fsi-core.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/fsi/fsi-core.c b/drivers/fsi/fsi-core.c
index af7965f..28b82d1 100644
--- a/drivers/fsi/fsi-core.c
+++ b/drivers/fsi/fsi-core.c
@@ -428,12 +428,26 @@ int fsi_master_register(struct fsi_master *master)
}
EXPORT_SYMBOL_GPL(fsi_master_register);
+static int fsi_slave_device_remove(struct device *dev, void *data)
+{
+ put_device(dev);
+ return 0;
+}
+
+static int fsi_master_slave_remove(struct device *dev, void *data)
+{
+ device_for_each_child(dev, NULL, fsi_slave_device_remove);
+ device_unregister(dev);
+ return 0;
+}
+
void fsi_master_unregister(struct fsi_master *master)
{
if (!master || !master->dev)
return;
ida_simple_remove(&master_ida, master->idx);
+ device_for_each_child(master->dev, NULL, fsi_master_slave_remove);
put_device(master->dev);
}
EXPORT_SYMBOL_GPL(fsi_master_unregister);
--
1.8.2.2
reply other threads:[~2017-01-12 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1484260449-80182-1-git-send-email-christopher.lee.bostic@gmail.com \
--to=christopher.lee.bostic@gmail.com \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=cbostic@us.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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