On 2018/11/12 下午 06:33, Arend van Spriel wrote: > On 11/12/2018 8:30 AM, Chi-Hsien Lin wrote: >> From: Wright Feng <wright.feng@xxxxxxxxxxx> >> >> AOS is a part of the SDIOD core that becomes active when the rest of >> SDIOD is sleeping to keep SDIO bus alive responding to reduced set of >> commands. >> >> Transaction between AOS and SDIOD is not protected, and if cmd 52 is >> received in AOS and in the middle of response state changed from AOS to >> SDIOD, response is corrupted and it causes to SDIO Host controller to >> hang. > > Just one question. The above sound pretty generic so does it apply to > any SDIO chip with AOS logic? > We found this issue when verifying SR feature with some SDIO cards(what we had), not sure whether every SDIO card has same problem. So we only change those chip's wake-up mechanism to noCmdDecode mode and let SDIOD_AOS just generates a wake-up request without responding. -Wright > Regards, > Arend > > >
