From: Marc Zyngier <maz@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
Rob Herring <robh@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
kernelci-results@groups.io, gtucker@collabora.com,
linux-kernel@vger.kernel.org,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
kernel@collabora.com
Subject: Re: mainline/master bisection: baseline.bootrr.rockchip-pcie-probed on rk3399-gru-kevin
Date: Mon, 17 Aug 2020 13:41:49 +0100 [thread overview]
Message-ID: <b04b51a9130660f40ba7d7e8e7c67167@kernel.org> (raw)
In-Reply-To: <cc089ea6-2484-7d7c-29a2-cd45daa47817@collabora.com>
On 2020-08-17 11:11, Enric Balletbo i Serra wrote:
> Hi Guillaume et all,
>
> On 17/8/20 12:02, Guillaume Tucker wrote:
>> Hi,
>>
>> Please see the bisection report below about a driver probe
>> regression with rockchip-pcie.
>>
>> Reports aren't automatically sent to the public while we're
>> trialing new bisection features on kernelci.org but this one
>> looks valid.
>>
>
> Thank you for make it public. It's nice to see kernelCI catching these
> things.
>
>> It seems to be due to this error:
>>
>> <6>[ 16.842128] rockchip-pcie f8000000.pcie: no vpcie12v regulator
>> found
>>
>
> I just noticed some patches in the ML that might help to fix the issue.
> It is
> not related to the above message though.
This message is always there, and is harmless (the regulator is
optional).
>
> I suspect the following series sent by Marc (cc'ied in this email) will
> fix the
> issue [1]. I'd expect the patches to land as a fix for this release.
This is indeed related to the rk3399 DT issue, and how the bisected
patch
only makes it plain that the DT has always been broken. The patches you
point
to should paper over the problem, and I'd appreciate some feedback on
them.
There may be a few more systems affected by this issue (at least MTK and
QC
systems could be affected as well).
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2020-08-17 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f394e3f.1c69fb81.4accc.4cf0@mx.google.com>
2020-08-17 10:02 ` mainline/master bisection: baseline.bootrr.rockchip-pcie-probed on rk3399-gru-kevin Guillaume Tucker
2020-08-17 10:11 ` Enric Balletbo i Serra
2020-08-17 12:41 ` Marc Zyngier [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=b04b51a9130660f40ba7d7e8e7c67167@kernel.org \
--to=maz@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=frowand.list@gmail.com \
--cc=gtucker@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.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 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.