Gedare Bloom commented on a discussion on bsps/aarch64/raspberrypi/i2c/raspberrypi-i2c.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/363#note_121843 > + > +static int rpi_i2c_transfer(i2c_bus *base, i2c_msg *msgs, uint32_t > msg_count) > +{ > + raspberrypi_i2c_bus *bus = (raspberrypi_i2c_bus *)base; > + int rv = 0; > + uint32_t i; > + > + for (i = 0; i < msg_count; ++i) > + { > + if (msgs[i].flags & I2C_M_RECV_LEN) > + { > + return RTEMS_INVALID_NUMBER; > + } > + } > + > + for (i = 0; i < msg_count; i++) It's an interesting question, what should be done in case of the error? Should none of the transfers happen, or should the erroneous one be skipped, or should the transfers stop when an error is encountered? I don't know what the right answer is. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/363#note_121843 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
