From: Brendan Higgins <brendanhiggins@google.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
"David S . Miller" <davem@davemloft.net>,
mchehab@kernel.org, Joel Stanley <joel@jms.id.au>,
martin.petersen@oracle.com,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-i2c@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C
Date: Thu, 13 Jul 2017 15:44:40 -0700 [thread overview]
Message-ID: <CAFd5g45V0Ya0UdBZMCoazvE0Sh33F3_oMb84-kLXn1qH0h=b3A@mail.gmail.com> (raw)
In-Reply-To: <20170628074515.GA1550@katana>
Sorry, went on vacation and then forgot about our conversion.
>> the struct i2c_bus_recovery_info. Is i2c_generic_scl_recovery supposed
>> to be part of the user interface, or is it just intended to help put the
>> main recovery function together?
>
> Sorry, I don't understand the question. What do you mean?
>
What I meant is that it looks like the only use of it is putting
together a default
recovery function, but I was wondering if it is fair to use it on its own.
Basically what I was asking is whether I could use i2c_generic_scl_recovery
in the case where SCL is hung.
I think I have a pretty good idea of what to do, I should probably just put
together an RFC patch.
next prev parent reply other threads:[~2017-07-13 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:15 [PATCH v11 0/4] i2c: aspeed: added driver for Aspeed I2C Brendan Higgins
2017-06-20 21:15 ` [PATCH v11 1/4] MAINTAINERS: add entry for Aspeed I2C driver Brendan Higgins
2017-06-23 18:40 ` Wolfram Sang
2017-06-20 21:15 ` [PATCH v11 2/4] i2c: aspeed: added documentation " Brendan Higgins
2017-06-23 18:41 ` Wolfram Sang
2017-06-20 21:15 ` [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C Brendan Higgins
2017-06-23 18:43 ` Wolfram Sang
2017-06-26 6:18 ` Joel Stanley
2017-06-27 8:36 ` Brendan Higgins
2017-06-27 8:28 ` Brendan Higgins
2017-06-27 9:00 ` Wolfram Sang
2017-06-27 23:47 ` Brendan Higgins
2017-06-28 7:45 ` Wolfram Sang
2017-07-13 22:44 ` Brendan Higgins [this message]
2017-07-14 7:18 ` Wolfram Sang
2017-06-20 21:15 ` [PATCH v11 4/4] i2c: aspeed: added slave support for Aspeed I2C driver Brendan Higgins
2017-06-23 18:41 ` Wolfram Sang
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='CAFd5g45V0Ya0UdBZMCoazvE0Sh33F3_oMb84-kLXn1qH0h=b3A@mail.gmail.com' \
--to=brendanhiggins@google.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=mchehab@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).