From: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
To: Mariusz Bialonczyk <manio@skyboo.net>
Cc: linux-kernel@vger.kernel.org, Evgeniy Polyakov <zbr@ioremap.net>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH 2/2] w1: fix the resume command API
Date: Tue, 19 Mar 2019 09:21:16 -0400 [thread overview]
Message-ID: <6836A9A3-AF86-4E2F-9215-647CB36E22DA@gmail.com> (raw)
In-Reply-To: <20190318092737.8170-3-manio@skyboo.net>
Hi Mariusz,
I appreciate your work on this.
> On Mar 18, 2019, at 05:27, Mariusz Bialonczyk <manio@skyboo.net> wrote:
>
> From the DS2408 datasheet [1]:
> "Resume Command function checks the status of the RC flag and, if it is set,
> directly transfers control to the control functions, similar to a Skip ROM
> command. The only way to set the RC flag is through successfully executing
> the Match ROM, Search ROM, Conditional Search ROM, or Overdrive-Match ROM
> command"
Indeed, figure 12-2 flow chart shows that SKIP_ROM resets RC to 0, then RESUME
looks for RC==1 to enter the control function "mode". Nice find!
I don't know however if other slaves are like that. Since the true impact of
your suggested change is indeed null on the bus (bit count wise). I guess even
this specific slave case is enough to warrant the change in the subsys.
>
> The function currently works perfectly fine in a multidrop bus, but when we
> have only a single slave connected, then only a Skip ROM is used and Match
> ROM is not called at all. This is leading to problems e.g. with single one
> DS2408 connected, as the Resume Command is not working properly and the
> device is responding with failing results after the Resume Command.
>
> This commit is fixing this by using a Skip ROM instead in those cases.
> The bandwidth / performance advantage is exactly the same.
>
> Refs:
> [1] https://datasheets.maximintegrated.com/en/ds/DS2408.pdf
>
> Signed-off-by: Mariusz Bialonczyk <manio@skyboo.net>
> Cc: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Reviewed-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
> ---
> drivers/w1/w1_io.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/w1/w1_io.c b/drivers/w1/w1_io.c
> index 0364d3329c52..4697136b9027 100644
> --- a/drivers/w1/w1_io.c
> +++ b/drivers/w1/w1_io.c
> @@ -432,8 +432,15 @@ int w1_reset_resume_command(struct w1_master *dev)
> if (w1_reset_bus(dev))
> return -1;
>
> - /* This will make only the last matched slave perform a skip ROM. */
> - w1_write_8(dev, W1_RESUME_CMD);
> + if (dev->slave_count == 1) {
> + /* Resume Command has to be preceeded with e.g. Match ROM which is
> + * not happening on single-slave buses, just do a Skip ROM instead
> + */
> + w1_write_8(dev, W1_SKIP_ROM);
> + } else {
> + /* This will make only the last matched slave perform a skip ROM. */
> + w1_write_8(dev, W1_RESUME_CMD);
> + }
This may be a subsys maintainer's style preference, but perhaps the verbose comments
might be better suited for the git commit message. Could this then be shorted to
if (dev->slave_count == 1)
w1_write_8(dev, W1_SKIP_ROM);
else
w1_write_8(dev, W1_RESUME_CMD);
Or maybe:
w1_write_8(dev, dev->slave_count > 1 ? W1_RESUME_CMD : W1_SKIP_ROM);
I am also ok with this proposed version, hence the "reviewed-by".
> return 0;
> }
> EXPORT_SYMBOL_GPL(w1_reset_resume_command);
> --
> 2.19.0.rc1
>
next prev parent reply other threads:[~2019-03-19 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:27 [PATCH 0/2] w1: DS2408 fixes Mariusz Bialonczyk
2019-03-18 9:27 ` [PATCH 1/2] w1: ds2408: add a missing reset when retrying in output_write() Mariusz Bialonczyk
2019-03-19 14:21 ` Jean-Francois Dagenais
2019-03-19 14:25 ` Jean-Francois Dagenais
2019-03-21 10:55 ` Mariusz Bialonczyk
2019-03-21 15:18 ` [PATCH v2] w1: ds2408: reset on output_write retry with readback Jean-Francois Dagenais
2019-03-27 16:53 ` Greg Kroah-Hartman
2019-03-28 12:17 ` Jean-Francois Dagenais
2019-04-03 8:33 ` Mariusz Bialonczyk
2019-03-18 9:27 ` [PATCH 2/2] w1: fix the resume command API Mariusz Bialonczyk
2019-03-19 13:21 ` Jean-Francois Dagenais [this message]
2019-03-19 14:21 ` Evgeniy Polyakov
2019-03-21 10:11 ` Mariusz Bialonczyk
2019-03-21 10:52 ` [PATCH v2] " Mariusz Bialonczyk
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=6836A9A3-AF86-4E2F-9215-647CB36E22DA@gmail.com \
--to=jeff.dagenais@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manio@skyboo.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®