From: linus.luessing@c0d3.blue (Linus Lüssing)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM: dts: meson: fixing USB support on Meson6, Meson8 and Meson8b
Date: Thu, 28 Sep 2017 16:51:41 +0200 [thread overview]
Message-ID: <20170928145141.GG6726@otheros> (raw)
In-Reply-To: <20170925224802.GA31386@ingrassia.epigenesys.com>
On Tue, Sep 26, 2017 at 12:48:02AM +0200, Emiliano Ingrassia wrote:
> Could you list all the kernels you have tried (included versions and patches) ?
I tried your two patches with:
A) a clean multi_v7_defconfig and no extra patches on:
* 4.13.2
* 4.13.3
B) a multi_v7_defconfig excluding CONFIG_DRM_TEGRA
(causes build errors):
* 4.14.0-rc1, no extra patches
* 4.14.0-rc2, no extra patches
* 4.14.0-rc1, with SMP patches [0]
All these kernels hung for me for the mentioned stress-ng tests
almost immediately.
I was also lucky to at least get a glimpse at a kernel crash
output during a chdir test once. Unfortunately still cut very early:
~~~
[ 97.499390] Unhandled fault: external abort on non-linefetch (0x1008) at 0
~~~
Regards, Linus
[0]:
81d519f ARM: dts: meson8b: add support for booting the secondary CPU cores
85ded56 ARM: dts: meson8: add support for booting the secondary CPU cores
c70daa9 ARM: meson: Add SMP bringup code for Meson8 and Meson8b
a39342c ARM: smp_scu: allow the platform code to read the SCU CPU status
0b1863d ARM: smp_scu: add a helper for powering on a specific CPU
27efddb dt-bindings: Amlogic: Add Meson8 and Meson8b SMP related documentation
next prev parent reply other threads:[~2017-09-28 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 11:57 [PATCH] ARM: dts: meson: fixing USB support on Meson6, Meson8 and Meson8b Emiliano Ingrassia
2017-09-23 13:15 ` Martin Blumenstingl
2017-09-28 16:35 ` Linus Lüssing
2017-09-24 4:28 ` Linus Lüssing
2017-09-24 4:42 ` Linus Lüssing
2017-09-25 22:48 ` Emiliano Ingrassia
2017-09-28 14:51 ` Linus Lüssing [this message]
2017-09-28 15:56 ` Linus Lüssing
2017-09-28 18:37 ` Emiliano Ingrassia
2017-10-06 22:24 ` Kevin Hilman
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=20170928145141.GG6726@otheros \
--to=linus.luessing@c0d3.blue \
--cc=linus-amlogic@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