From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: linux-kernel@vger.kernel.org
Cc: Ming Lei <ming.lei@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths
Date: Wed, 10 Oct 2012 11:56:25 +0100 [thread overview]
Message-ID: <1349866585-24883-3-git-send-email-dp@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1349866585-24883-1-git-send-email-dp@opensource.wolfsonmicro.com>
This patch provides the aforementioned procfs file that lists
the default firmware paths that are used during firmware lookup.
The file contains a white space separated list of paths.
There will be another patch on top of this that adds the functionality
to modify the paths at runtime.
Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
---
drivers/base/firmware_class.c | 55 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 2153eab..22cef4d 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -27,6 +27,8 @@
#include <linux/pm.h>
#include <linux/suspend.h>
#include <linux/syscore_ops.h>
+#include <linux/proc_fs.h>
+#include <linux/seq_file.h>
#include <generated/utsrelease.h>
@@ -1430,6 +1432,56 @@ err_fwp_alloc:
return -ENOMEM;
}
+static void *fw_path_seq_start(struct seq_file *seq, loff_t *pos)
+{
+ return seq_list_start_head(&fw_path_list, *pos);
+}
+
+static void *fw_path_seq_next(struct seq_file *seq, void *v, loff_t *pos)
+{
+ return seq_list_next(v, &fw_path_list, pos);
+}
+
+static int fw_path_seq_show(struct seq_file *seq, void *v)
+{
+ const struct fw_path_rec *fwp;
+ struct list_head *l = v;
+
+ if (l == &fw_path_list)
+ return 0;
+ fwp = list_entry(v, struct fw_path_rec, list);
+ seq_puts(seq, fwp->name);
+ if (l->next != &fw_path_list)
+ seq_putc(seq, ' ');
+ else
+ seq_putc(seq, '\n');
+ return 0;
+}
+
+static void fw_path_seq_stop(struct seq_file *seq, void *v)
+{
+}
+
+static const struct seq_operations fw_path_ops = {
+ .start = fw_path_seq_start,
+ .next = fw_path_seq_next,
+ .stop = fw_path_seq_stop,
+ .show = fw_path_seq_show,
+};
+
+static int fw_path_open(struct inode *inode, struct file *file)
+{
+ return seq_open(file, &fw_path_ops);
+}
+
+static const struct file_operations fw_path_seq_fops = {
+ .owner = THIS_MODULE,
+ .open = fw_path_open,
+ .read = seq_read,
+ .llseek = seq_lseek,
+ .release = seq_release,
+};
+
static void __init fw_cache_init(void)
{
spin_lock_init(&fw_cache.lock);
@@ -1465,6 +1517,8 @@ static int __init firmware_class_init(void)
return ret;
}
+ proc_create("fw_path", S_IRUGO, NULL, &fw_path_seq_fops);
+
return class_register(&firmware_class);
}
@@ -1474,6 +1528,7 @@ static void __exit firmware_class_exit(void)
unregister_syscore_ops(&fw_syscore_ops);
unregister_pm_notifier(&fw_cache.pm_notify);
#endif
+ remove_proc_entry("fw_path", NULL);
fw_free_path_list();
class_unregister(&firmware_class);
}
--
1.7.12.2
next prev parent reply other threads:[~2012-10-10 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 10:56 [PATCH 0/2] Expose firmware paths via procfs Dimitris Papastamos
2012-10-10 10:56 ` [PATCH 1/2] firmware: Convert firmware path setup from an array to a list Dimitris Papastamos
2012-10-22 15:42 ` Greg Kroah-Hartman
2012-10-23 9:43 ` Dimitris Papastamos
2012-10-10 10:56 ` Dimitris Papastamos [this message]
2012-10-10 13:36 ` [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths Greg Kroah-Hartman
2012-10-10 13:40 ` Josh Boyer
2012-10-10 13:45 ` Dimitris Papastamos
2012-10-10 14:41 ` Dimitris Papastamos
2012-10-10 15:14 ` [PATCH 0/2] Expose firmware paths via procfs Ming Lei
-- strict thread matches above, loose matches on Subject: below --
2012-10-09 22:50 [PATCH 2/2] firmware: Add /proc/fw_path entry to list the firmware paths Dimitris Papastamos
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=1349866585-24883-3-git-send-email-dp@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.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