Home/ Questions/Q 527743
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:54:54+00:00

For a project I’m working on I have to talk to a multi-function chip

  • 0

For a project I’m working on I have to talk to a multi-function chip via I2C. I can do this from linux user-space via the I2C /dev/i2c-1 interface.

However, It seems that a driver is talking to the same chip at the same time. This results in my I2C_SLAVE accesses to fail with An errno-value of EBUSY. Well – I can override this via the ioctl I2C_SLAVE_FORCE. I tried it, and it works. My commands reach the chip.

Question: Is it safe to do this? I know for sure that the address-ranges that I write are never accessed by any kernel-driver. However, I am not sure if forcing I2C communication that way may confuse some internal state-machine or so.(I’m not that into I2C, I just use it…)

For reference, the hardware facts:

 OS:           Linux
 Architecture: TI OMAP3 3530
 I2C-Chip:     TWL4030 (does power, audio, usb and lots of other things..)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know that particular chip, but often you have commands that require a sequence of writes, first to one address to set a certain mode, then you read or write another address — where the function of the second address changes based on what you wrote to the first one. So if the driver is in the middle of one of those operations, and you interrupt it (or vice versa), you have a race condition that will be difficult to debug. For a reliable solution, you better communicate through the chip’s driver…

    • 0