Hi, we're planning to connect the nRF5340 (running Audio SDK in gateway config) via I2S (and UART) to a custom device. We need to configure the nRF5340 be I2S slave even though the SDK configures it as master. The rate at which nRF5340's I2C interface receives audio data will therefore be governed by the clock source on our custom device, which could drift relative to the clock source in the nRF5340. Is this clock drift likely to be a problem? I have not been able to find the answer in the SDK source code or docs.
I'm aware that drift compensation ability is provided in the code, but it appears not to be applied when the nRF5340 is operating as a gateway - I2S audio data enters a FIFO, goes to LC3 encode, and then across to the LE audio controller on the network core.
I guess my question is, once the isochronous stream is started, does the LE audio controller require blocks of data at a rate governed by the nRF5340 system clock, or is it "flexible" enough to accept data at approximately, but not exactly, this rate?.