linux-toradex.git/drivers/w1/w1.c, branch v4.9.123

1wire: family module autoload fails because of upper/lower case mismatch.

2018-07-03T09:23:06+00:00

commit 065c09563c872e52813a17218c52cd642be1dca6 upstream.

1wire family module autoload fails because of upper/lower
  case mismatch.

Signed-off-by: Ingo Flaschberger 
Acked-by: Evgeniy Polyakov 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

w1: don't leak refcount on slave attach failure in w1_attach_slave_device()

2017-03-12T05:41:48+00:00

commit d2ce4ea1a0b0162e5d2d7e7942ab6f5cc2063d5a upstream.

Near the beginning of w1_attach_slave_device() we increment a w1 master
reference count.
Later, when we are going to exit this function without actually attaching
a slave device (due to failure of __w1_attach_slave_device()) we need to
decrement this reference count back.

Signed-off-by: Maciej S. Szmigiero 
Fixes: 9fcbbac5ded489 ("w1: process w1 netlink commands in w1_process thread")
Cc: Evgeniy Polyakov 
Signed-off-by: Greg Kroah-Hartman

w1: fix timeout_us parameter description

2016-08-31T11:56:05+00:00

Fix 'timeout_us' parameter description.

Signed-off-by: Wei Yongjun 
Signed-off-by: Greg Kroah-Hartman

w1: silence an uninitialized variable warning

2016-05-01T21:04:19+00:00

If kstrtoint() returns -ERANGE then "tmp" is uninitialized.

Signed-off-by: Dan Carpenter 
Acked-by: Evgeniy Polaykov 
Signed-off-by: Greg Kroah-Hartman

w1: w1_process() is not freezable kthread

2016-02-12T03:23:28+00:00

w1_process() calls try_to_freeze(), but the thread doesn't mark itself
freezable through set_freezable(), so the try_to_freeze() call is useless.

Acked-by: Evgeniy Polyakov 
Signed-off-by: Jiri Kosina 
Signed-off-by: Greg Kroah-Hartman

w1: introduce an ability to specify microseconds bus scanning intervals

2015-05-24T19:08:59+00:00

Some of 1-Wire devices commonly associated with physical access control
systems are attached/generate presence for as short as 100 ms - hence
the tens-to-hundreds milliseconds scan intervals are required.

Signed-off-by: Dmitry Khromov 
Acked-by: Evgeniy Polyakov 
Signed-off-by: Greg Kroah-Hartman

w1: support auto-load of w1_bq27000 module.

2014-11-27T03:09:02+00:00

1/ change request_module call to zero-pad single digit
   family numbers.  This appears to be the intention of
   the code, but not what it actually does.

   This means that the alias created for W1_FAMILY_SMEM_01
   might actually be useful.

2/ Define a family name for the BQ27000 battery charge monitor.
   Unfortunately this is the same number as W1_FAMILY_SMEM_01
   so if both a compiled on a system, one module might need to
   be blacklisted.

3/ Add a MODULE_ALIAS for the bq27000.

Acked-by: Evgeniy Polyakov 
Signed-off-by: NeilBrown 
Signed-off-by: Greg Kroah-Hartman

w1: use pr_* instead of printk

2014-06-20T00:46:51+00:00

This patch replaces all calls to the "printk" function within the main "w1"
directory by calls to the appropriate "pr_*" function thus addressing
the following warning generated by the checkpatch script:

WARNING: Prefer [subsystem eg: netdev]_err([subsystem]dev, ...
        then dev_err(dev, ... then pr_err(...  to printk(KERN_ERR ...

Signed-off-by: Fjodor Schelichow 
Signed-off-by: Roman Sommer 
Acked-by: Evgeniy Polyakov 
Signed-off-by: Greg Kroah-Hartman

w1: do not unlock unheld list_mutex in __w1_remove_master_device()

2014-05-27T21:08:46+00:00

w1_process_callbacks() expects to be called with dev->list_mutex held,
but it is the fact only in w1_process(). __w1_remove_master_device()
calls w1_process_callbacks() after it releases list_mutex.

The patch fixes __w1_remove_master_device() to acquire list_mutex
for w1_process_callbacks().

Found by Linux Driver Verification project (linuxtesting.org).

Signed-off-by: Alexey Khoroshilov 
Acked-by: David Fries 
Acked-by: Evgeniy Polyakov 
Cc: stable  # 3.15
Signed-off-by: Greg Kroah-Hartman

w1: avoid recursive device_add

2014-04-16T21:07:51+00:00

__w1_attach_slave_device calls device_add which calls w1_bus_notify
which calls the w1_bq27000 slave driver, which calls
platform_device_add and device_add and deadlocks on getting
&(&priv->bus_notifier)->rwsem as it is still held in the previous
device_add.  This avoids the problem by processing the family
add/remove outside of the slave device_add call.

Commit 47eba33a0997fc7362a introduced this deadlock and added
a KOBJ_ADD, as the add was already reported in device_register two add
events were being sent.  This change suppresses the device_register
add so that any slave device sysfs entries are setup before the add
goes out.

Belisko Marek reported this change fixed the deadlock he was seeing on
ARM device tree, while testing on my x86-64 system never saw the
deadlock.

Reported-by: Belisko Marek 
Signed-off-by: David Fries 
Signed-off-by: Greg Kroah-Hartman