6 May
2016
6 May
'16
6:31 p.m.
On 05/06/2016 01:59 AM, Stefan Agner wrote:
There could be runtime determined board specific reason why a EHCI initialization fails (e.g. ENODEV if a Port is not available). In this case, properly return the error code. While at it, that function (board_ehci_hcd_init) has actually two documentation blocks... Use the correct function name for the documentation block of board_usb_phy_mode.
Signed-off-by: Stefan Agner stefan@agner.ch
Applied, thanks.
Best regards, Marek Vasut