All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Dmitry Khromov <dk@icelogic.net>, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, Evgeniy Polyakov <zbr@ioremap.net>
Subject: Re: [PATCH] Introduce an ability to specify microseconds bus scanning intervals in w1 core
Date: Tue, 14 Apr 2015 10:15:13 -0700	[thread overview]
Message-ID: <552D4B21.4020803@infradead.org> (raw)
In-Reply-To: <552CC487.70402@icelogic.net>

On 04/14/15 00:40, Dmitry Khromov wrote:
> DS1990* "iButtons" and compatible RFID card readers commonly found at
> physical access control systems are usually attached/generate presence
> for as short as 100 ms - hence the tens-to-hundreds milliseconds scan
> intervals are required.
> 
> Tested on Raspberry Pi model B+ with DS2482-100 bus master,
> tens-of-milliseconds intervals are easily achieved without significant
> CPU load (and with unknown accuracy), and though I doubt
> microseconds-scale intervals are really feasible in terms of practical
> use and underlying buses timings, I believe it makes sense to give the
> ability of using them to those willing to try.
> 
> Signed-off-by: Dmitry Khromov <dk@icelogic.net>
> Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
> 
>  drivers/w1/w1.c | 17 ++++++++++++++++-
>  1 file changed, 16 insertions(+), 1 deletion(-)
> ---
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
> index 181f41c..73b4e2d 100644
> --- a/drivers/w1/w1.c
> +++ b/drivers/w1/w1.c
> @@ -46,11 +46,15 @@ MODULE_AUTHOR("Evgeniy Polyakov <zbr@ioremap.net>");
>  MODULE_DESCRIPTION("Driver for 1-wire Dallas network protocol.");
>  
>  static int w1_timeout = 10;
> +static int w1_timeout_us = 0;
>  int w1_max_slave_count = 64;
>  int w1_max_slave_ttl = 10;
>  
>  module_param_named(timeout, w1_timeout, int, 0);
>  MODULE_PARM_DESC(timeout, "time in seconds between automatic slave searches");
> +module_param_named(timeout_us, w1_timeout_us, int, 0);
> +MODULE_PARM_DESC(timeout, "time in microseconds between automatic slave"
> +                         "searches");

The description string needs a space between "slave" and "searches".

>  /* A search stops when w1_max_slave_count devices have been found in that
>   * search.  The next search will start over and detect the same set of devices
>   * on a static 1-wire bus.  Memory is not allocated based on this number, just


-- 
~Randy

  reply	other threads:[~2015-04-14 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55292A69.5020106@icelogic.net>
     [not found] ` <1040571428797306@web8j.yandex.ru>
2015-04-14  7:40   ` [PATCH] Introduce an ability to specify microseconds bus scanning intervals in w1 core Dmitry Khromov
2015-04-14 17:15     ` Randy Dunlap [this message]
2015-04-22 21:55       ` [PATCH v2] w1: introduce an ability to specify microseconds bus scanning intervals Dmitry Khromov
2015-04-22 23:22         ` Evgeniy Polyakov
2015-04-23  9:20         ` Greg KH
2015-04-23 11:30           ` Dmitry Khromov
2015-04-23 11:33             ` [PATCH v3] " Dmitry Khromov
2015-05-12 19:29           ` Dmitry Khromov
2015-05-13 15:00             ` Evgeniy Polyakov
2015-05-13 15:31               ` gregkh

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=552D4B21.4020803@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dk@icelogic.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.