From: Diederik de Haas <didi.debian@cknow.org>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Cc: Andrew Powers-Holmes <aholmes@omnom.net>,
Ondrej Jirman <megi@xff.cz>,
stable@vger.kernel.org, Jonas Karlman <jonas@kwiboo.se>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: rk356x: Fix PCIe register and range mappings
Date: Fri, 02 Jun 2023 23:41:16 +0200 [thread overview]
Message-ID: <4805396.GXAFRqVoOG@bagend> (raw)
In-Reply-To: <20230601132516.153934-1-frattaroli.nicolas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
On Thursday, 1 June 2023 15:25:16 CEST Nicolas Frattaroli wrote:
> The register and range mappings for the PCIe controller in Rockchip's
> RK356x SoCs are incorrect. Replace them with corrected values from the
> vendor BSP sources, updated to match current DT schema.
I have been using the exact same patch for a while now and without it my
Quartz64 Model A with a USB3 adapter card either caused a boot failure, a
fatal kernel crash or a non-fatal kernel crash (system seemed to work apart
from the USB3 adapter card).
With the patch, everything worked. So
Tested-by: Diederik de Haas <didi.debian@cknow.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-02 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 13:25 [PATCH v2] arm64: dts: rockchip: rk356x: Fix PCIe register and range mappings Nicolas Frattaroli
2023-06-02 21:41 ` Diederik de Haas [this message]
2023-06-06 17:07 ` Heiko Stuebner
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=4805396.GXAFRqVoOG@bagend \
--to=didi.debian@cknow.org \
--cc=aholmes@omnom.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=megi@xff.cz \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.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).