[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190321111143.c54afe794f1de222a0cd020a@skyboo.net>
Date: Thu, 21 Mar 2019 11:11:43 +0100
From: Mariusz Bialonczyk <manio@...boo.net>
To: Evgeniy Polyakov <zbr@...emap.net>
Cc: Jean-Francois Dagenais <jeff.dagenais@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: [PATCH 2/2] w1: fix the resume command API
Hi Evgeniy,
On Tue, 19 Mar 2019 17:21:09 +0300
Evgeniy Polyakov <zbr@...emap.net> wrote:
> Looks like this may break the search logic, can you check that with this patch applied
> some other single slave device will correctly 'tell' its id and it can be addressed via match rom (like, basically, just reading temperature or something like that)?
Yes, I have tested it in a mixed environment (regarding single slave/multidrop):
/sys/devices/w1_bus_master5 # ll
total 0
drwxr-xr-x 9 root 0 0 Mar 21 10:53 .
drwxr-xr-x 17 root 0 0 Mar 2 16:49 ..
drwxr-xr-x 4 root 0 0 Mar 21 10:55 28-00000921ff5e
drwxr-xr-x 3 root 0 0 Mar 21 11:04 29-0000001246a4
drwxr-xr-x 3 root 0 0 Mar 21 11:04 29-0000001246b1
drwxr-xr-x 3 root 0 0 Mar 21 11:04 29-0000001246b9
drwxr-xr-x 3 root 0 0 Mar 21 10:54 29-0000001246bc
drwxr-xr-x 3 root 0 0 Mar 21 10:53 3a-0000000f354f
/sys/devices/w1_bus_master6 # ll
total 0
drwxr-xr-x 4 root 0 0 Mar 21 10:54 .
drwxr-xr-x 17 root 0 0 Mar 2 16:49 ..
drwxr-xr-x 3 root 0 0 Mar 21 11:07 29-0000001246a9
No problem with searching and using other slaves on the bus.
regards,
--
Mariusz Białończyk | xmpp/e-mail: manio@...boo.net
https://skyboo.net | https://github.com/manio
Powered by blists - more mailing lists