Hi Boris, Vitor, This repository does not contain full kernel sources, but it should be enough to discuss mastership request feature. https://github.com/przemekgaj/i3c-linux/commit/d54fe68a9d3e573c0c454a2c6f1afafc20142ec5 Please keep in mind that this is initial version, but mastership works correctly. I added one property to DT to reflect relationship between masters. It is possible to request mastership on demand (using sysfs. Useful in case when Linux machine is equipped only with secondary master controller) or automatically change operation mode when device driver wants to read/write something from/to device. I'm sure I will have to rework something because this was implemented on sources from PATCH v4. I saw that Boris released v7 yesterday :) Thanks, Przemek On 9/3/18, 11:33 AM, "vitor" <Vitor.Soares@xxxxxxxxxxxx> wrote: EXTERNAL MAIL Hi Przemek, On 30-08-2018 20:00, Przemyslaw Gaj wrote: > So, per my understanding since the Main master support the hand-off of > the bus you accept all incoming MR, right? Or do you check all devices BCR? > > I'm not sure what do you mean here. Mastership request(MR) is from secondary master > to current master. Current master can NACK this request if for example it comes from > wrong device. If it's ok, current master sends GETACCMST command and secondary master > may ACK or NACK this command. It it's acked, secondary master becomes current master. > > Best regards, > Vitor Soares > > Please let me know if something is unclear. > > Regards, > Przemek > Sorry, it s not clear yet. For instances there is a bus with several secondary master. If each of them request the bus mastership (one at a time), will you accept all by default? Because you can only accept only some of them. Regards, Vitor Soares
