linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.nelson@boundarydevices.com (Eric Nelson)
To: linux-arm-kernel@lists.infradead.org
Subject: [BISECT] v3.18-rc1 doesn't boot on nitrogen6x i.MX6 board
Date: Thu, 23 Oct 2014 20:21:11 -0700	[thread overview]
Message-ID: <5449C5A7.7090204@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5Bbm_C-2p=XQwN0rxfW+vL0MNMWwHvqgTggGbz_waY95g@mail.gmail.com>

Thanks Fabio (and Richard).

On 10/23/2014 06:43 PM, Fabio Estevam wrote:
> On Thu, Oct 23, 2014 at 6:46 PM, Fabio Estevam <festevam@gmail.com> wrote:
> 
>>> I really haven't looked into what might be wrong, I just wanted to let
>>> you know that this fix apparently breaks some boards.
>>
>> Adding Eric and Troy in case they could comment. I don't know why this
>> commit would cause failure on nitrogen board.
> 
> Ok, so I am able to reproduce this issue on a mx6qsabresd if I don't
> pass the PCI gpio reset (like in nitrogen):
> 
> --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> @@ -521,7 +521,6 @@
>  &pcie {
>         pinctrl-names = "default";
>         pinctrl-0 = <&pinctrl_pcie>;
> -       reset-gpio = <&gpio7 12 0>;
>         status = "okay";
>  };
> 
> 
> Richard Zhu sent a fix for this, but 	it has not been applied yet:
> http://www.spinics.net/lists/linux-pci/msg34748.html
> 
> With his patch applied the kernel can boot fine.
> 
> Regards,
> 
> Fabio Estevam
> 

      reply	other threads:[~2014-10-24  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20141023203034.GR12732@glaurung.lavos.net>
2014-10-23 20:46 ` [BISECT] v3.18-rc1 doesn't boot on nitrogen6x i.MX6 board Fabio Estevam
2014-10-23 20:58   ` Eric Nelson
2014-10-24  1:43   ` Fabio Estevam
2014-10-24  3:21     ` Eric Nelson [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=5449C5A7.7090204@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).