Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: found k2-i2c, checking if
onyx chip is on it
Mar 29 13:26:17 mapache kernel: low_i2c:xfer() chan=0, addrdir=0x47, mode=4,
subsize=1, subaddr=0x43, 1 bytes, bus /[EMAIL PROTECTED],f2000000/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_addr, isr: 6)
Mar 29 13:26:17 mapache kernel: low_i2c:KW: NAK on address
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 6)
Mar 29 13:26:17 mapache kernel: KW: wrong state. Got KW_I2C_IRQ_ADDR, state:
state_stop (isr: 06)
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 4)
Mar 29 13:26:17 mapache kernel: low_i2c:xfer error -5
Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: failed to read control
register
Mar 29 13:26:18 mapache kernel: low_i2c:xfer() chan=11, addrdir=0x93, mode=4,
subsize=1, subaddr=0x0, 2 bytes, bus /[EMAIL PROTECTED],0/[EMAIL
PROTECTED]/[EMAIL PROTECTED]
Anything else to try? The following related modules were loaded:
Looks like it is on another i2c address or bus on those machines.
Bugger. I have no idea how to find out which one.
Would the tarball of device-tree help? There must be a way ...
Is the address of the onyx codec hardwired in your code?
Eduardo.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
