public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: mx6: Disable PCIe on SABRE Lite/Nitrogen6x
Date: Sun, 23 Mar 2014 01:11:34 +0100	[thread overview]
Message-ID: <201403230111.34356.marex@denx.de> (raw)
In-Reply-To: <532DF7AC.1000801@free.fr>

On Saturday, March 22, 2014 at 09:50:52 PM, Thierry Bultel wrote:
> When I communicated about the bug I had,
> and said that my temporary workaround was to disable the PCIe,
> my intention was not to make the suppression become a standard,
> and I believe it is a little bit frustrating for Marek.

It's not frustrating for me ;-)

> The AMOS820, based on the sabrelite/nitrogen has a PCIe slot on the main
> board,
> so there might be some interest of having the PCIe support enabled.

Do you have the PERST routed correctly and handled correctly ? If so, it does 
not matter whether or not you probed the PCIe bus in U-Boot , since toggling the 
PERST will cause Fundamental Reset (See [1]).

> To my mind, the bug is in the kernel I am using, it should be robust
> to the fact that PCIe has been formerly probed.

Freescale's 3.0.35 is crap, that's no news. If possible (read: you don't need 
GPU/VPU), use mainline.

> Wouldn't that be smarter to have the PCIe enabled or not,
> by an environment variable (defaulted to YES, and that the user could
> set to NO eventually for older kernels) ?
> Best regards

No, read [1] and probably the entire thread . For example [2] is also of 
interest here. If you soft-reset the system, your PCIe link will still be up 
from the previously running Linux instance (just like if it was started in U-
Boot) and you'll run into the same problem with the newly booted instance if 
Linux kernel.

So once again, did you correctly implement PERST so you can do FR properly ?

[1] http://lists.denx.de/pipermail/u-boot/2014-February/172496.html
[2] http://lists.denx.de/pipermail/u-boot/2014-February/172509.html

Best regards,
Marek Vasut

  parent reply	other threads:[~2014-03-23  0:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 11:28 [U-Boot] Running mx6qsabrelite at 1Gz with Freescale kernel rel_imx_3.0.35_4.1.0 tbultel at free.fr
2014-03-18 12:34 ` Stefano Babic
2014-03-21 18:47   ` Thierry Bultel
2014-03-21 22:50     ` Eric Nelson
2014-03-22  1:33       ` Marek Vasut
2014-03-22 15:13         ` Eric Nelson
2014-03-22 15:17         ` [U-Boot] [PATCH] ARM: mx6: Disable PCIe on SABRE Lite/Nitrogen6x Eric Nelson
2014-03-22 18:26           ` Marek Vasut
2014-03-22 20:50             ` Thierry Bultel
2014-03-22 21:49               ` Eric Nelson
2014-03-23  0:15                 ` Marek Vasut
2014-03-23  0:11               ` Marek Vasut [this message]
2014-03-23 16:50               ` Stefano Babic
2014-03-23 16:48             ` Stefano Babic
2014-04-01  8:17           ` Stefano Babic

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=201403230111.34356.marex@denx.de \
    --to=marex@denx.de \
    --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