On Friday, November 19, 2010 6:20 PM, Marc Kleine-Budde wrote : >>>> - spin_unlock_irqrestore(&priv->msgif_reg_lock, flags); >>>> + pch_can_rw_msg_obj(&priv->regs->ifregs[1].creq, tx_obj_no); >>> Still we have the busy waiting in the TX path. Maybe you can move the >>> waiting before accessing the if[1] and remove the busy waiting here. >> I can't understand your saying. >> For transmitting data, calling pch_can_rw_msg_obj is mandatory. >Yes, but the busy wait is not needed. It should be enough to do the >busy-waiting _before_ accessing the if[1].
Do you mean we should create other pch_can_rw_msg_obj which doesn't have busy wait ? --- Thanks, Tomoya MORINAGA OKI SEMICONDUCTOR CO., LTD. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
