From: Andre Guedes <andre.guedes@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 3/6] Bluetooth: Set discovery parameters
Date: Fri, 9 Aug 2013 20:12:31 -0300 [thread overview]
Message-ID: <1376089954-13639-4-git-send-email-andre.guedes@openbossa.org> (raw)
In-Reply-To: <1376089954-13639-1-git-send-email-andre.guedes@openbossa.org>
This patch adds support for setting discovery parameters through
debugfs filesystem.
Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
---
net/bluetooth/hci_sysfs.c | 45 ++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 44 insertions(+), 1 deletion(-)
diff --git a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
index 90cb53b..17ebc4a 100644
--- a/net/bluetooth/hci_sysfs.c
+++ b/net/bluetooth/hci_sysfs.c
@@ -553,9 +553,52 @@ static int discovery_parameters_open(struct inode *inode, struct file *file)
return single_open(file, discovery_parameters_show, inode->i_private);
}
+static ssize_t discovery_parameters_write(struct file *file,
+ const char __user *data,
+ size_t count, loff_t *offset)
+{
+ struct seq_file *sfile = file->private_data;
+ struct hci_dev *hdev = sfile->private;
+ struct discovery_param param;
+ char *buf;
+ int n;
+ ssize_t res = 0;
+
+ /* We don't allow partial writes */
+ if (*offset != 0)
+ return 0;
+
+ buf = kzalloc(count, GFP_KERNEL);
+ if (!buf)
+ return 0;
+
+ if (copy_from_user(buf, data, count))
+ goto out;
+
+ memset(¶m, 0, sizeof(param));
+
+ n = sscanf(buf, "%hhx %hx %hx %u %u %hhx %hhx",
+ ¶m.scan_type, ¶m.scan_interval, ¶m.scan_window,
+ ¶m.le_scan_duration, ¶m.interleaved_scan_duration,
+ ¶m.interleaved_inquiry_length,
+ ¶m.bredr_inquiry_length);
+ if (n != 7)
+ goto out;
+
+ hci_dev_lock(hdev);
+ memcpy(&hdev->discovery_param, ¶m, sizeof(param));
+ hci_dev_unlock(hdev);
+
+ res = count;
+out:
+ kfree(buf);
+ return res;
+}
+
static const struct file_operations discovery_parameters_fops = {
.open = discovery_parameters_open,
.read = seq_read,
+ .write = discovery_parameters_write,
.llseek = seq_lseek,
.release = single_release,
};
@@ -602,7 +645,7 @@ int hci_add_sysfs(struct hci_dev *hdev)
debugfs_create_file("auto_accept_delay", 0444, hdev->debugfs, hdev,
&auto_accept_delay_fops);
- debugfs_create_file("discovery_parameters", 0444, hdev->debugfs, hdev,
+ debugfs_create_file("discovery_parameters", 0644, hdev->debugfs, hdev,
&discovery_parameters_fops);
return 0;
}
--
1.8.3.4
next prev parent reply other threads:[~2013-08-09 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 23:12 [PATCH 0/6] LE parameters via debugfs Andre Guedes
2013-08-09 23:12 ` [PATCH 1/6] Bluetooth: Discovery parameters per hci_dev Andre Guedes
2013-08-09 23:12 ` [PATCH 2/6] Bluetooth: Export discovery parameters on debugfs Andre Guedes
2013-08-09 23:12 ` Andre Guedes [this message]
2013-08-10 16:09 ` [PATCH 3/6] Bluetooth: Set discovery parameters Marcel Holtmann
2013-08-21 20:41 ` Andre Guedes
2013-08-21 22:56 ` Marcel Holtmann
2013-08-22 20:01 ` Andre Guedes
2013-08-09 23:12 ` [PATCH 4/6] Bluetooth: Keep the LE connection parameters in its own structure Andre Guedes
2013-08-09 23:12 ` [PATCH 5/6] Bluetooth: Add LE connection parameters to debugfs Andre Guedes
2013-08-10 16:10 ` Marcel Holtmann
2013-08-21 20:41 ` Andre Guedes
2013-08-09 23:12 ` [PATCH 6/6] Bluetooth: Add support for setting LE connection parameters via debugfs Andre Guedes
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=1376089954-13639-4-git-send-email-andre.guedes@openbossa.org \
--to=andre.guedes@openbossa.org \
--cc=linux-bluetooth@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