From: Dragan Simic <dsimic@manjaro.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
Date: Tue, 02 Apr 2024 01:07:27 +0200 [thread overview]
Message-ID: <fd6b90fc4d277bb4034a919e72959e94@manjaro.org> (raw)
In-Reply-To: <171200852040.1394042.4883299945962544319.b4-ty@sntech.de>
On 2024-04-01 23:55, Heiko Stuebner wrote:
> On Mon, 1 Apr 2024 00:20:56 +0200, Dragan Simic wrote:
>> Remove a redundant node from the Pine64 Pinebook Pro dts, which is
>> intended
>> to provide a value for the delay in PCI Express enumeration, but that
>> isn't
>> supported without additional out-of-tree kernel patches.
>>
>> There were already efforts to upstream those kernel patches, because
>> they
>> reportedly make some PCI Express cards (such as LSI SAS HBAs) usable
>> in
>> Pine64 RockPro64 (which is also based on the RK3399); otherwise,
>> those PCI
>> Express cards fail to enumerate. However, providing the required
>> background
>> and explanations proved to be a tough nut to crack, which is the
>> reason why
>> those patches remain outside of the kernel mainline for now.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] arm64: dts: rockchip: Remove unsupported node from the Pinebook
> Pro dts
> commit: 43853e843aa6c3d47ff2b0cce898318839483d05
Great, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-01 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 22:20 [PATCH] arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts Dragan Simic
2024-04-01 21:55 ` Heiko Stuebner
2024-04-01 23:07 ` Dragan Simic [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=fd6b90fc4d277bb4034a919e72959e94@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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