Hi Wolfram-san, > From: Wolfram Sang, Sent: Wednesday, June 27, 2018 5:44 PM > > Hi, > > thanks for the discussion on this topic! > > > > The hardware team said: > > > - In CPG point of view: > > > - such polling doesn't need (because the reset pulse is generated > > > correctly). > > > - About the interval after deassert the reset, this is depend on each > > > hardware module. > > > (In other words, if each hardware module has a special handling > > > about after the deassert interval, > > > we should follow the special handling.) > > > - The I2C controller needs an interval of reading SRCR at least (this is > > > a special handling). > > > > > > So, I think adding this code is not good fit in CPG point of view. > > > > Calling reset_control_status() from i2c-rcar is fine for me. > > < snip > > > Where is this special handling documented BTW, I can't find it.
Please refer to "57.5.4 Usage note for the transmission and reception procedure" in the datasheet Rev. 1.00. I agree waiting for maximum 1024ms > The BSP waits for maximum 1024ms which seems excessive to me. The BSP waits for maximum 1024us, not 1024ms. Best regards, Yoshihiro Shimoda
