Christian Mauderer commented on a discussion on bsps/aarch64/raspberrypi/i2c/raspberrypi-i2c.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/363#note_125273 > +typedef struct { > + i2c_bus base; > + uintptr_t input_clock; > + rtems_id task_id; > + uintptr_t base_address; > + raspberrypi_bsc_masters device; > + uintptr_t remaining_bytes; > + uintptr_t remaining_transfers; > + uint8_t *current_buffer; > + uintptr_t current_buffer_size; > + bool read_transfer; > +} raspberrypi_i2c_bus; > + > +static void i2c_polling_read( raspberrypi_i2c_bus *bus ) > +{ > + while ( !( S_REG( bus ) & S_DONE ) && ( bus->remaining_bytes > 0 ) ) { Maybe I missed something that @gedare noted. So please wait for his answer too. But usually, it's not necessary for the drivers to provide an additional mutex in the i2c framework. (Note that this is not true for all driver frameworks in RTEMS.) -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/363#note_125273 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
