From: Vernon Mauery <vernon.mauery@linux.intel.com>
To: Patrick Venture <venture@google.com>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: quanta q71l not booting with 4.13
Date: Tue, 15 May 2018 09:22:16 -0700 [thread overview]
Message-ID: <20180515162216.GA105329@mauery> (raw)
In-Reply-To: <CAO=notzi+BtDV=m5TYPE7UrtO-TYPVLe+LYhUcApX4UgvwfVyA@mail.gmail.com>
On 15-May-2018 07:26 AM, Patrick Venture wrote:
>Hi;
>
>So, i have a couple theories to test but before I ran them down I
>figured I'd just ask here. The quanta-q71l won't boot if the BMC is
>running the 4.13 kernel from openbmc. I'm theorizing that the spi mux
>is flipped somehow (maybe a default pin value is getting flipped) or
>something else is preventing the host from reading its flash.
>
>Has anyone experienced anything like this on their platform?
The 4.13 kernel has a bunch of new stuff that has to be worked out in
device tree to make pins and clocks and resets work. We had trouble
getting our hosts booting as well when we first migrated to 4.13. We had
to fix a few things in our device tree to get the espi clock working. I
think it also included a patch that Jae sent to this list for the clock
and reset driver. This may be an entirely different issue, but that was
our story.
+ espi: espi@1e6ee000 {
+ compatible = "aspeed,ast2500-espi-slave";
+ reg = <0x1e6ee000 0x100>;
+ interrupts = <23>;
+ status = "disabled";
+ clocks = <&syscon ASPEED_CLK_GATE_ESPICLK>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_espi_default>;
+ };
+
I think we also had trouble with the host video showing up after the
host powered on, this was also dependent on some clock control settings
in the dts. But Ed tells me this is a AST2400, so video is not your
problem.
--Vernon
next prev parent reply other threads:[~2018-05-15 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 14:26 quanta q71l not booting with 4.13 Patrick Venture
2018-05-15 16:22 ` Vernon Mauery [this message]
2018-05-15 16:35 ` Patrick Venture
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=20180515162216.GA105329@mauery \
--to=vernon.mauery@linux.intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.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 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.