STRUCT I2C_BUS_RECOV(9) I2C and SMBus Subsystem STRUCT I2C_BUS_RECOV(9)NAME
struct_i2c_bus_recovery_info - I2C bus recovery information
SYNOPSIS
struct i2c_bus_recovery_info {
int (* recover_bus) (struct i2c_adapter *);
int (* get_scl) (struct i2c_adapter *);
void (* set_scl) (struct i2c_adapter *, int val);
int (* get_sda) (struct i2c_adapter *);
void (* prepare_recovery) (struct i2c_bus_recovery_info *bri);
void (* unprepare_recovery) (struct i2c_bus_recovery_info *bri);
int scl_gpio;
int sda_gpio;
};
MEMBERS
recover_bus
Recover routine. Either pass driver's recover_bus routine, or i2c_generic_scl_recovery or i2c_generic_gpio_recovery.
get_scl
This gets current value of SCL line. Mandatory for generic SCL recovery. Used internally for generic GPIO recovery.
set_scl
This sets/clears SCL line. Mandatory for generic SCL recovery. Used internally for generic GPIO recovery.
get_sda
This gets current value of SDA line. Optional for generic SCL recovery. Used internally, if sda_gpio is a valid GPIO, for generic GPIO
recovery.
prepare_recovery
This will be called before starting recovery. Platform may configure padmux here for SDA/SCL line or something else they want.
unprepare_recovery
This will be called after completing recovery. Platform may configure padmux here for SDA/SCL line or something else they want.
scl_gpio
gpio number of the SCL line. Only required for GPIO recovery.
sda_gpio
gpio number of the SDA line. Only required for GPIO recovery.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 STRUCT I2C_BUS_RECOV(9)
Check Out this Related Man Page
GPIOIIC(4) BSD Kernel Interfaces Manual GPIOIIC(4)NAME
gpioiic -- GPIO I2C controller
SYNOPSIS
gpioiic* at gpio? offset 0 mask 0x3 flag 0x0
gpioiic* at gpio?
iic* at gpioiic?
DESCRIPTION
The gpioiic driver allows bit-banging an I2C bus as a master using two GPIO pins. By default the first pin is used as a serial data (SDA)
signal and the second as a serial clock (SCL). If the flag locator is set to 0x01, the order of the SDA and SCL signals is reversed. Both
GPIO pins must be able to drive an output and the SDA pin must be also able to read an input.
The pins can be specified in the kernel configuration with the offset and the mask locators. The offset and mask can also be specified when
gpioiic is attached at runtime using the GPIOATTACH ioctl(2) on the gpio(4) device. Each bit in the mask locator defines one pin; the pin
number is calculated as an addition of the bit position and the offset locator. For example, offset 17 and mask 0x5 defines pin numbers 17
and 19.
SEE ALSO gpio(4), iic(4), intro(4)HISTORY
The gpioiic driver first appeared in OpenBSD 3.9 and NetBSD 5.0.
AUTHORS
The gpioiic driver was written by Alexander Yurchenko <grange@openbsd.org> and was ported to NetBSD by Marc Balmer <marc@msys.ch>.
CAVEATS
A gpioiic device can not be detached from the gpio(4) bus at runtime due to the fact that iic(4) busses can not detach once attached.
BSD October 2, 2011 BSD
Started an frecover from Sam, with a recovery scope and a different destination.
Here is what is happening.
Starting file recovery...
frecover(5423): incorrect volume mounted;
frecover(5424): expected volume 1, and got 2
frecover(5433): Do you wish to continue using this volume? (^/^) y... (5 Replies)
please tell me if this thinkin is correct, if not, please corret me:
disaster recovery means when something bad happens and you need to retrieved a backed up file, all you have to do is cd into the tape drive and then look for the file you want and extract it from the drive.
is this... (3 Replies)
I am looking into disaster recovery and I wanted to know what files and/or other information do I need to keep copies of to sucessfully restore my system from the ground up..... Any help is greatly appreciated. I am running Solaris 8 on an Ultra 60. (5 Replies)
I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level
My understanding is creating mksysb nim on NIM server is for new installation of LPARS
Then;
How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Dear guys
I am thanks for all to provide us these important subjects, which we need it in our work as system administrator, or technical support. As you know, In the Data center (disaster recovery) There are systems working under multi operating systems such as (AIX,HP Unix , sun... (1 Reply)
I have a 7029-6C3 that was running AIX 5.2; I tried to update to 5.2.10.5, rebooted, and the box went south. Upon further digging through the h/w logs, I found the error "Service Processor Firmware Failure"
I can't get the machine to boot - not even to CD. How can I recover from this? Or can... (10 Replies)
I'm sorting out the disaster recovery plan for a critical server. It's a Dell PowerEdge 2850 running Openserver 5.0.6a.
We have a disaster recovery agreement with HP and they have just confirmed that in the event of a total disaster such as the server being totally wiped out, they would NOT... (2 Replies)
Hey guys, I hope this is the right place to post. As i'm not too sure where this question would go.
The question is: How is backup and recovery carried out in major corporations. Even if you are not in a major corporation an answer would be great.
I'm doing some research as to how it's carried... (2 Replies)
This is a unlacky day! I deleted some data in my server by mistake. Please recommend me some data recovery programes. I don't want to carry the big thing to a company of data service.
Thanks very much to my friends (6 Replies)
Hi
Could any one explain the meaning & purpose of below mention parameters in layman term. Suppose if we set below paramet what will happen.
error-reset-recovery=boot
error-reset-recovery=sync (3 Replies)
I was recently working on a project where some gpio pins were being toggled from within the user space:
const char *const amplifierGPIO = "/sys/class/gpio/gpio107/value";
void amplifierUnmute()
{
std::ofstream amp(amplifierGPIO);
if (amp.is_open())
{
... (3 Replies)