From: Evgeniy Polyakov <zbr@ioremap.net>
To: Evgeny Boger <eugenyboger@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Add strong pullup emulation to w1-gpio master driver.
Date: Tue, 12 Nov 2013 05:03:24 +0400 [thread overview]
Message-ID: <37621384218204@web11j.yandex.ru> (raw)
In-Reply-To: <5281691F.4060604@gmail.com>
Hi
12.11.2013, 03:32, "Evgeny Boger" <eugenyboger@gmail.com>:
>> Why did you drop this check? It has nothing with w1-gpio driver
> This check prevents master from implementing "set_pullup" provided it does support only "write_bit" method.
> The comment above states that
>> w1_io.c would need to support calling set_pullup before - * the last write_bit operation of a w1_write_8 which it currently - * doesn't.
> which is kind of strange, since it describes what w1_io.c actually does support.
>
> w1_write_8 (w1_io.c:154, https://github.com/torvalds/linux/blob/master/drivers/w1/w1_io.c#L154):
>> for (i = 0; i < 8; ++i) {
>> if (i == 7)
>> w1_pre_write(dev);
>> w1_touch_bit(dev, (byte >> i) & 0x1);
>> }
>
> It seems like w1_write_8() calls w1_pre_write(), which in turn calls set_pullup() just before the last write_bit().
>
> I'm not sure why this check was there in the first place.
Please add author of those lines to clarify things.
This doesn't look obvious to me
next prev parent reply other threads:[~2013-11-12 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:36 [PATCH 1/1] Add strong pullup emulation to w1-gpio master driver Evgeny Boger
2013-11-11 23:09 ` Evgeniy Polyakov
[not found] ` <5281691F.4060604@gmail.com>
2013-11-12 1:03 ` Evgeniy Polyakov [this message]
2013-11-12 1:07 ` Evgeny Boger
2013-11-12 8:01 ` David Fries
2013-11-13 1:15 ` Evgeny Boger
2013-11-13 4:07 ` David Fries
2013-11-13 22:42 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2013-11-10 23:27 Evgeny Boger
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=37621384218204@web11j.yandex.ru \
--to=zbr@ioremap.net \
--cc=eugenyboger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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