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 13:58:59 -0700 [thread overview]
Message-ID: <54496C13.7070903@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5CaWzfqjj2orX4nh8Vjk2o8bS_sQ7vPA_SwwfdFpFwXDQ@mail.gmail.com>
Thanks for the report Brian (and Fabio).
On 10/23/2014 01:46 PM, Fabio Estevam wrote:
> Hi Brian,
>
> On Thu, Oct 23, 2014 at 6:30 PM, Brian Downing <bdowning@lavos.net> wrote:
>> Hi all; apologies for not posting to the linux-arm-kernel mailing list,
>> but lists.infradead.org seems, well, dead:
>>
>> $ host lists.infradead.org
>> Host lists.infradead.org not found: 3(NXDOMAIN)
>>
>> v3.18-rc1 doesn't boot on my Boundary Devices nitrogen6x board.
>> (Specifically, imx6q-nitrogen6x.dtb). It fails before any console output.
>> I bisected it down to this commit:
>>
>> commit 3fce0e882f61513c45c67e15bd0fde03341b58a5
>> Author: Tim Harvey <tharvey@gateworks.com>
>> Date: Thu Aug 7 23:36:40 2014 -0700
>>
>> PCI: imx6: Delay enabling reference clock for SS until it stabilizes
>>
>> According to the IMX6 reference manuals, REF_SSP_EN (Reference clock enable
>> for SS function) must remain deasserted until the reference clock is
>> running at the appropriate frequency.
>>
>> Delay enabling the reference clock for the SS function until it has
>> stabilized. This prevents a high link failure rate (>5%) on certain IMX6
>> boards at various temperatures.
>>
>> [bhelgaas: reword changelog slightly]
>> Tested-by: Fabio Estevam <festevam@gmail.com>
>> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>> Acked-by: Marek Vasut <marex@denx.de>
>> Acked-by: Lucas Stach <l.stach@pengutronix.de>
>>
>> With that one commit reverted v3.18-rc1 fires up just fine for me.
>>
>> I really haven't looked into what might be wrong, I just wanted to let
>> you know that this fix apparently breaks some boards.
We'll dig in and let you know what we find.
Regards,
Eric
next prev parent reply other threads:[~2014-10-23 20:58 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 [this message]
2014-10-24 1:43 ` Fabio Estevam
2014-10-24 3:21 ` Eric Nelson
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=54496C13.7070903@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.