public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com
Subject: Re: [PATCH] USB: Generalize usb initialization for omap hw
Date: Thu, 24 Apr 2008 12:07:43 -0700	[thread overview]
Message-ID: <200804241207.43593.david-b@pacbell.net> (raw)
In-Reply-To: <1209063112-30352-2-git-send-email-felipe.balbi@nokia.com>

Looks better to me, but:

On Thursday 24 April 2008, Felipe Balbi wrote:
> +static void setup_ehci_io_mux(void)
> +{
> +#ifdef CONFIG_OMAP_EHCI_PHY_MODE

This PHY_MODE thing should probably be provided by the board
data not Kconfig, and

> +       /* PHY mode of operation for board: 750-2083-001
> +        * ISP1504 connected to Port1 and Port2
> +        * Do Func Mux setting for 12-pin ULPI PHY mode
> +        */
> +
> +       /* Port1 */
> +       omap_cfg_reg(Y9_3430_USB1HS_PHY_STP);
> +       omap_cfg_reg(Y8_3430_USB1HS_PHY_CLK);
> 	...

All those MUX options should be driven by the board data too.

Unless it's for some reason not possible to configure only one
of the three EHCI ports at a time...

This patch being cleanup-only, I don't suggest you fix that
at this time.

- Dave



> +
> +#else
> +       /* Set Func mux for :
> +        * TLL mode of operation
> +        * 12-pin ULPI SDR TLL mode for Port1/2/3
> +        */
> +
> +       /* Port1 */
> +       omap_cfg_reg(Y9_3430_USB1HS_TLL_STP);
> +       omap_cfg_reg(Y8_3430_USB1HS_TLL_CLK);
> +       	...
> +#endif /* CONFIG_OMAP_EHCI_PHY_MODE */
> +
> +       return;
> +}


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

  reply	other threads:[~2008-04-24 19:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 13:46 [RFC][PATCH 0/2] musb init generalization Felipe Balbi
2008-04-24 13:46 ` [PATCH 1/2] OMAP: Introduce cpu_class_is_omap3() Felipe Balbi
2008-04-24 13:46   ` [PATCH 2/2] USB: Generalize usb initialization for omap hw Felipe Balbi
2008-04-24 14:13     ` Gadiyar, Anand
2008-04-24 14:18       ` Felipe Balbi
2008-04-24 17:16         ` Tony Lindgren
2008-04-24 18:27           ` Felipe Balbi
2008-04-24 18:29           ` David Brownell
2008-04-24 18:32             ` Felipe Balbi
2008-04-24 19:02               ` David Brownell
2008-04-24 18:51             ` usb generalization Felipe Balbi
2008-04-24 18:51               ` [PATCH] USB: Generalize usb initialization for omap hw Felipe Balbi
2008-04-24 19:07                 ` David Brownell [this message]
2008-04-24 20:48                   ` Tony Lindgren
2008-04-24 21:08                     ` Felipe Balbi
2008-04-24 21:31                       ` Tony Lindgren
2008-04-28 10:59                 ` Pandita, Vikram
2008-04-28 11:02                   ` Felipe Balbi
2008-04-24 17:12       ` [PATCH 2/2] " Tony Lindgren
2008-04-24 17:10     ` Tony Lindgren
2008-04-24 17:06   ` [PATCH 1/2] OMAP: Introduce cpu_class_is_omap3() Tony Lindgren

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=200804241207.43593.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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