Re: ulpi_check_integrity returning error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Fabio,

On 12/14/10 00:14, Fabio Estevam wrote:
> Hi,
>
> I am working on adding USB OTG host support for the mx31_3ds board
> (OTG PHY is a ISP1504).

ISP1504 seems like ULPI compliant transceiver.

> USB OTG in device mode works fine and I can only get OTG host mode to
> work if I force a 'return 0' into the ulpi_check_integrity function. I
> was wondering if anyone has any suggestions as to where to
> inspect/debug the fact that the read/write to the OTG PHY scratch
> register does not match.

Both ULPI specifications (1.0 and 1.1) define the Scratch register as:
"an empty register byte for testing purposes. Software can read, write,
set and clear this register; and the functionality of the PHY will not be affected."
Therefore it should be implemented in the ISP1504 as such and according to
NXP's ISP1504 datasheet it should be there...

What about the ID? Do you get the vendor/product ID value as expected?

> Thanks,
>
> Fabio Estevam
>

-- 
Regards,
Igor.

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux