public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peng Fan <B51431@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] imx:mx6sxsabresd add usb support
Date: Mon, 3 Nov 2014 21:32:46 +0800	[thread overview]
Message-ID: <545783FE.90108@freescale.com> (raw)
In-Reply-To: <54577507.5070509@denx.de>


Hi,

? 11/3/2014 8:28 PM, Stefano Babic ??:
> Hi Peng,
>
> On 01/11/2014 03:19, Peng Fan wrote:
>> Add usb support for mx6sxsabresd board.
>>
>> Signed-off-by: Peng Fan <Peng.Fan@freescale.com>
>> Signed-off-by: Ye.Li <B37916@freescale.com>
>> ---
>>   board/freescale/mx6sxsabresd/mx6sxsabresd.c | 29 +++++++++++++++++++++++++++++
>>   include/configs/mx6sxsabresd.h              | 14 ++++++++++++++
>>   2 files changed, 43 insertions(+)
>>
>> diff --git a/board/freescale/mx6sxsabresd/mx6sxsabresd.c b/board/freescale/mx6sxsabresd/mx6sxsabresd.c
>> index 256ea29..016b8e8 100644
>> --- a/board/freescale/mx6sxsabresd/mx6sxsabresd.c
>> +++ b/board/freescale/mx6sxsabresd/mx6sxsabresd.c
>> @@ -296,3 +296,32 @@ int checkboard(void)
>>
>>   	return 0;
>>   }
>> +
>> +#ifdef CONFIG_USB_EHCI_MX6
>> +iomux_v3_cfg_t const usb_otg1_pads[] = {
>> +	MX6_PAD_GPIO1_IO09__USB_OTG1_PWR | MUX_PAD_CTRL(NO_PAD_CTRL),
>> +	MX6_PAD_GPIO1_IO10__ANATOP_OTG1_ID | MUX_PAD_CTRL(NO_PAD_CTRL)
>> +};
>> +
>> +iomux_v3_cfg_t const usb_otg2_pads[] = {
>> +	MX6_PAD_GPIO1_IO12__USB_OTG2_PWR | MUX_PAD_CTRL(NO_PAD_CTRL),
>> +};
>> +
>> +int board_ehci_hcd_init(int port)
>> +{
>> +	switch (port) {
>> +	case 0:
>> +		imx_iomux_v3_setup_multiple_pads(usb_otg1_pads,
>> +						 ARRAY_SIZE(usb_otg1_pads));
>> +		break;
>> +	case 1:
>> +		imx_iomux_v3_setup_multiple_pads(usb_otg2_pads,
>> +						 ARRAY_SIZE(usb_otg2_pads));
>> +		break;
>> +	default:
>> +		printf("MXC USB port %d not yet supported\n", port);
>> +		return 1;
>> +	}
>> +	return 0;
>> +}
>> +#endif
>
> Frankly, I am expecting that this function power up the bus instead of
> pin multiplexing. If the pins are reserved for USB, why should we set
> the pinmux each time board_ehci_hcd_init() is called ? And, in any case,
> pins are not reset after their usage for USB. You can move this setup in
> board_init() or in another init function.

Because otg power problem which is pointed out by Ye Li, I'll do power 
enable/disable in board_ehci_power function and move the pin settings to 
board_init.
And sent patch v2.

Thanks,
Peng.
>
> Best regards,
> Stefano Babic
>

  reply	other threads:[~2014-11-03 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01  2:19 [U-Boot] [PATCH 0/5] add usb support for mx6 board Peng Fan
2014-11-01  2:19 ` [U-Boot] [PATCH 1/5] imx:mx6sxsabresd add usb support Peng Fan
2014-11-01  7:45   ` Li Ye-B37916
2014-11-01 13:45   ` Fabio Estevam
2014-11-03 12:28   ` Stefano Babic
2014-11-03 13:32     ` Peng Fan [this message]
2014-11-01  2:19 ` [U-Boot] [PATCH 2/5] imx:mx6slevk " Peng Fan
2014-11-01 13:44   ` Fabio Estevam
2014-11-01  2:19 ` [U-Boot] [PATCH 3/5] arm:imx-common introduce a new function to set gpr Peng Fan
2014-11-01  7:39   ` Li Ye-B37916
2014-11-01 10:49     ` Peng Fan
2014-11-01 13:44   ` Wolfgang Denk
2014-11-01  2:19 ` [U-Boot] [PATCH 4/5] imx:mx6qarm2 add usb support Peng Fan
2014-11-01  2:19 ` [U-Boot] [PATCH 5/5] imx:mx6sabresd " Peng Fan

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=545783FE.90108@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