Add IC guy Best regards, Peter Chen > -----Original Message----- > From: Fabio Estevam [mailto:festevam@xxxxxxxxx] > Sent: Tuesday, August 14, 2012 10:01 AM > To: Chen Peter-B29397 > Cc: balbi@xxxxxx; Sean Cross; linux-usb@xxxxxxxxxxxxxxx; Estevam Fabio- > R49496; Zhao Richard-B20223; Shawn Guo; Marek Vasut; Li Frank-B20596 > Subject: Re: mxs-phy on i.MX233 not enumerating > > Peter, > > On 8/13/12, Chen Peter-B29397 <B29397@xxxxxxxxxxxxx> wrote: > > > According to IC guys, the logic of handling HOSTDISCONDETECT is the > same > > between i.mx28 and i.mx23. > > As pointed out by Sean, on mx23 reference manual we have the following > text describing HOSTDISCONDETECT: > > "Due to a on chip issue (Errata #2791), software must > pay attention to when to assert the HOSTDISCONDETECT bit description > has the following: > > ENHOSTDISCONDETECT bit in HW_USBPHY_CTRL register: > 1. Only set HW_USBPHY_CTRL.ENHOSTDISCONDETECT > during high speed host mode. > 2. Do not set HW_USBPHY_CTRL.ENHOSTDISCONDETECT > during the reset and speed negotiation period. > 3. Do not set HW_USBPHY_CTRL.ENHOSTDISCONDETECT > during host suspend/resume sequence." > > and the same is not present on mx28 reference manual. > > How can we make sure we are not violating the point 2 above? > > Thanks, > > Fabio Estevam ��.n��������+%������w��{.n�����{���)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥