From: Peng Fan <B51431@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/3] imx:mx6slevk add board level support for usb
Date: Fri, 7 Nov 2014 19:48:23 +0800 [thread overview]
Message-ID: <545CB187.5070800@freescale.com> (raw)
In-Reply-To: <201411071210.40127.marex@denx.de>
? 11/7/2014 7:10 PM, Marek Vasut ??:
> On Friday, November 07, 2014 at 12:08:03 PM, Peng Fan wrote:
>> ? 11/7/2014 4:26 PM, Marek Vasut ??:
>>> On Friday, November 07, 2014 at 02:08:14 AM, Peng Fan wrote:
>>>> Add pinmux settings, implement board_ehci_hcd_init, board_usb_phy_mode
>>>>
>>>> There are two usb port on mx6slevk board:
>>>> 1. otg port
>>>> 2. host port
>>>> The following are the connection between usb controller and board usb
>>>> interface, host port has not ID pin set:
>>>> otg1 core <---> board otg port
>>>> otg2 core <---> board host port
>>>> In order to make host port work, board_usb_phy_mode return 0 to let
>>>> ehci-mx6.c driver decide otg2 core to works in host mode.
>>>>
>>>> Signed-off-by: Peng Fan <Peng.Fan@freescale.com>
>>>> Signed-off-by: Ye Li <B37916@freescale.com>
>>>> ---
>>>
>>> [...]
>>>
>>>> @@ -150,6 +151,63 @@ static int setup_fec(void)
>>>>
>>>> }
>>>> #endif
>>>>
>>>> +#ifdef CONFIG_USB_EHCI_MX6
>>>> +#define USB_OTHERREGS_OFFSET 0x800
>>>> +#define USBPHY_CTRL 0x30
>>>> +#define UCTRL_PWR_POL (1 << 9)
>>>> +#define USBPHY_CTRL_OTG_ID 0x08000000
>>>
>>> This looks like an duplication. Aren't those bits defined somewhere in
>>> generic code already ?
>>
>> If this way 'int board_usb_phy_mode(int port, enum usb_init_type *type)'
>> can be accpeted, these bits are not needed and I'll move these bits in
>> the seperate PHY register struct access patch. Anyway, after the board
>> level usb support patch.
>
> What about abstracting that stuff into a function which returns the PHY's
> idea of the current mode instead. That way, you can determine the PHY's
> idea of the mode from both board code and the driver code.
>
struct phy register is good, but I prefer not to include this in board
level code, see my reply in this patch "usb:ehci-mx6 add
board_usb_phy_mode function" just as "board_ehci_power" and
"board_ehci_hcd_init" do. I think it is good to make it a seperate patch.
> Best regards,
> Marek Vasut
>
Regards,
Peng.
prev parent reply other threads:[~2014-11-07 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 1:08 [U-Boot] [PATCH v3 0/3] Add board level usb supporrt for mxsxsabresd and mx6slevk Peng Fan
2014-11-07 1:08 ` [U-Boot] [PATCH v3 1/3] usb:ehci-mx6 add board_usb_phy_mode function Peng Fan
2014-11-07 8:25 ` Marek Vasut
2014-11-07 11:03 ` Peng Fan
2014-11-07 11:09 ` Marek Vasut
2014-11-07 11:45 ` Peng Fan
2014-11-07 12:17 ` Marek Vasut
2014-11-08 4:07 ` Peng Fan
2014-11-08 4:35 ` Peng Fan
2014-11-08 11:33 ` Marek Vasut
2014-11-10 1:01 ` Peng Fan
2014-11-10 17:55 ` Marek Vasut
2014-11-07 1:08 ` [U-Boot] [PATCH v3 2/3] imx:mx6sxsabresd add board level support for usb Peng Fan
2014-11-07 1:08 ` [U-Boot] [PATCH v3 3/3] imx:mx6slevk " Peng Fan
2014-11-07 8:26 ` Marek Vasut
2014-11-07 11:08 ` Peng Fan
2014-11-07 11:10 ` Marek Vasut
2014-11-07 11:48 ` Peng Fan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545CB187.5070800@freescale.com \
--to=b51431@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox