Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-06 Thread Raja, Govindraj
On Mon, Mar 5, 2012 at 7:36 PM, Koen Kooi k...@dominion.thruhere.net wrote:

 Op 5 mrt. 2012, om 12:12 heeft Govindraj.R het volgende geschreven:

 From: Govindraj.R govindraj.r...@ti.com

 On beagle some of uart mux lines are used for other
 purpose so init only uart3.

 Uart2 rx line clashes with gpio_147 used for usb ehci
 phy reset. Initializing uart2 pad_mux lines can break
 ehci module on beagle xm.
 (gpio_147 is available on uart2_rx in mode4 reference
 mux34xx.c - uart2_rx.gpio_147)

 That's only on xM revision C, right?

Applicable to all beagle boards having external usb
hub (USB2HS_nRST will require uart2_rx.gpio_147)

Beagle Rev Ax/Bx doesn't seem to have external hub
module so not applicable for those boards

Will modify and post a new patch.

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


Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-06 Thread Koen Kooi

Op 6 mrt. 2012, om 10:03 heeft Raja, Govindraj het volgende geschreven:

 On Mon, Mar 5, 2012 at 7:36 PM, Koen Kooi k...@dominion.thruhere.net wrote:
 
 Op 5 mrt. 2012, om 12:12 heeft Govindraj.R het volgende geschreven:
 
 From: Govindraj.R govindraj.r...@ti.com
 
 On beagle some of uart mux lines are used for other
 purpose so init only uart3.
 
 Uart2 rx line clashes with gpio_147 used for usb ehci
 phy reset. Initializing uart2 pad_mux lines can break
 ehci module on beagle xm.
 (gpio_147 is available on uart2_rx in mode4 reference
 mux34xx.c - uart2_rx.gpio_147)
 
 That's only on xM revision C, right?
 
 Applicable to all beagle boards having external usb
 hub (USB2HS_nRST will require uart2_rx.gpio_147)

My apologies, I was confusing it with the DVI reset GPIO (which changed in 
between revisions) and the polarity of the USB pin (which changed during xM A 
- C).

regards,

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


Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-06 Thread Raja, Govindraj
On Tue, Mar 6, 2012 at 1:30 AM, Kevin Hilman khil...@ti.com wrote:
 Govindraj.R govindraj.r...@ti.com writes:

 From: Govindraj.R govindraj.r...@ti.com

 On beagle some of uart mux lines are used for other
 purpose so init only uart3.

 OK, but you should also be clear that this patch is effectively
 disabling all UARTS (except UART3) by defatul, which I'm not sure all
 Beagle users will be happy about.


Okay, I have posted new version of the patch
[PATCH] omap3_beagle: init uart2 for beagle rev AX/BX only

which initialises uart1/3/4 on all beagle boards

and uart2 init is done for only beagle rev ax/bx
which doesn't seem to have external usb module.


 Uart2 rx line clashes with gpio_147 used for usb ehci
 phy reset. Initializing uart2 pad_mux lines can break
 ehci module on beagle xm.
 (gpio_147 is available on uart2_rx in mode4 reference
 mux34xx.c - uart2_rx.gpio_147)

 As Koen mentioned, this conflict only exists on certain boards, so
 you should be clear that this is just an example.


conflict exists all beagle rev's expect rev ax/bx.

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


Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-06 Thread Raja, Govindraj
On Tue, Mar 6, 2012 at 2:21 AM, Tony Lindgren t...@atomide.com wrote:
 * Kevin Hilman khil...@ti.com [120305 11:28]:
 Govindraj.R govindraj.r...@ti.com writes:

  From: Govindraj.R govindraj.r...@ti.com
 
  On beagle some of uart mux lines are used for other
  purpose so init only uart3.

 OK, but you should also be clear that this patch is effectively
 disabling all UARTS (except UART3) by defatul, which I'm not sure all
 Beagle users will be happy about.

  Uart2 rx line clashes with gpio_147 used for usb ehci
  phy reset. Initializing uart2 pad_mux lines can break
  ehci module on beagle xm.
  (gpio_147 is available on uart2_rx in mode4 reference
  mux34xx.c - uart2_rx.gpio_147)

 As Koen mentioned, this conflict only exists on certain boards, so
 you should be clear that this is just an example.

 OK, thanks for the comments. Also it's a bit clear if
 this really is safe to do on all beagles.

I have clarified the same in reply to Kevin Hilman and Koen Kooi
in the same thread.


  Cc: Tony Lindgren t...@atomide.com
  Cc: Kevin Hilman khil...@ti.com
  Tested-by: Peter Ujfalusi peter.ujfal...@ti.com
  Tested-by: Robert Nelson robertcnel...@gmail.com
  Signed-off-by: Govindraj.R govindraj.r...@ti.com

 [...]

  +
  +static inline void board_serial_init(void)

 Should be __init

 [...]

  +static inline void board_serial_init(void)

 here too.

 ..so dropping the patch for now until these are fixed
 and we have some tested-bys for non-xm beagles too.


Okay fine, I have new version of the patch
[PATCH] omap3_beagle: init uart2 for beagle rev AX/BX only

This patch shouldn't have any impact and should work on beagles.

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


Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-05 Thread Kevin Hilman
Govindraj.R govindraj.r...@ti.com writes:

 From: Govindraj.R govindraj.r...@ti.com

 On beagle some of uart mux lines are used for other
 purpose so init only uart3.

OK, but you should also be clear that this patch is effectively
disabling all UARTS (except UART3) by defatul, which I'm not sure all
Beagle users will be happy about.

 Uart2 rx line clashes with gpio_147 used for usb ehci
 phy reset. Initializing uart2 pad_mux lines can break
 ehci module on beagle xm.
 (gpio_147 is available on uart2_rx in mode4 reference 
 mux34xx.c - uart2_rx.gpio_147)

As Koen mentioned, this conflict only exists on certain boards, so
you should be clear that this is just an example.

 Cc: Tony Lindgren t...@atomide.com
 Cc: Kevin Hilman khil...@ti.com
 Tested-by: Peter Ujfalusi peter.ujfal...@ti.com
 Tested-by: Robert Nelson robertcnel...@gmail.com
 Signed-off-by: Govindraj.R govindraj.r...@ti.com

[...]

 +
 +static inline void board_serial_init(void)

Should be __init

[...]

 +static inline void board_serial_init(void)

here too.

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


Re: [PATCH] omap3_beagle: Init only uart3 used for console

2012-03-05 Thread Tony Lindgren
* Kevin Hilman khil...@ti.com [120305 11:28]:
 Govindraj.R govindraj.r...@ti.com writes:
 
  From: Govindraj.R govindraj.r...@ti.com
 
  On beagle some of uart mux lines are used for other
  purpose so init only uart3.
 
 OK, but you should also be clear that this patch is effectively
 disabling all UARTS (except UART3) by defatul, which I'm not sure all
 Beagle users will be happy about.
 
  Uart2 rx line clashes with gpio_147 used for usb ehci
  phy reset. Initializing uart2 pad_mux lines can break
  ehci module on beagle xm.
  (gpio_147 is available on uart2_rx in mode4 reference 
  mux34xx.c - uart2_rx.gpio_147)
 
 As Koen mentioned, this conflict only exists on certain boards, so
 you should be clear that this is just an example.

OK, thanks for the comments. Also it's a bit clear if
this really is safe to do on all beagles.
 
  Cc: Tony Lindgren t...@atomide.com
  Cc: Kevin Hilman khil...@ti.com
  Tested-by: Peter Ujfalusi peter.ujfal...@ti.com
  Tested-by: Robert Nelson robertcnel...@gmail.com
  Signed-off-by: Govindraj.R govindraj.r...@ti.com
 
 [...]
 
  +
  +static inline void board_serial_init(void)
 
 Should be __init
 
 [...]
 
  +static inline void board_serial_init(void)
 
 here too.

..so dropping the patch for now until these are fixed
and we have some tested-bys for non-xm beagles too.

Regards,

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