Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1686974

Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C

From Brendan Higgins <brendanhiggins@google.com>
Newsgroups linux.kernel
Subject Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C
Date 2017-07-14 00:50 +0200
Message-ID <u2V5L-39v-11@gated-at.bofh.it> (permalink)
References (2 earlier) <tVBOy-5Jh-19@gated-at.bofh.it> <tWUcq-6mA-23@gated-at.bofh.it> <tWUFs-6Nx-15@gated-at.bofh.it> <tX8p4-7z8-19@gated-at.bofh.it> <tXfTz-3W1-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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.

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C Brendan Higgins <brendanhiggins@google.com> - 2017-07-14 00:50 +0200
  Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C Wolfram Sang <wsa@the-dreams.de> - 2017-07-14 09:20 +0200

csiph-web