From: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
To: Mariusz Bialonczyk <manio@skyboo.net>
Cc: open list <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <zbr@ioremap.net>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH 1/2] w1: ds2408: add a missing reset when retrying in output_write()
Date: Tue, 19 Mar 2019 10:25:50 -0400 [thread overview]
Message-ID: <3E9B4A8B-6409-4102-A3A2-40853AD04DB1@gmail.com> (raw)
In-Reply-To: <DF2ABF87-116D-4287-8A18-89C2C59124AF@gmail.com>
> On Mar 19, 2019, at 10:21, Jean-Francois Dagenais <jeff.dagenais@gmail.com> wrote:
>
> I can do a proper patch submission if you guys provide positive response on this
> early RFC. Or better yet, you can take it and own it yourself as your v2
> Mariusz. ;)
Just FYI, here's what the retry loop looks like after this suggested patch:
do {
w1_buf[0] = W1_F29_FUNC_CHANN_ACCESS_WRITE;
w1_buf[1] = *buf;
w1_buf[2] = ~(*buf);
w1_write_block(sl->master, w1_buf, 3);
readBack = w1_read_8(sl->master);
if (readBack == W1_F29_SUCCESS_CONFIRM_BYTE &&
optional_read_back_valid(sl, *buf)) {
bytes_written = 1;
goto out;
}
if (w1_reset_resume_command(sl->master))
goto out; /* unrecoverable error */
/* try again, the slave is ready for a command */
} while (--retries);
Much better on the eyes.
next prev parent reply other threads:[~2019-03-19 14:25 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 [this message]
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
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=3E9B4A8B-6409-4102-A3A2-40853AD04DB1@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®