From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Marc Zyngier <maz@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, samuel@dionne-riel.com,
linux-pci@vger.kernel.org, Shawn Lin <shawn.lin@rock-chips.com>,
linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
kernel-team@android.com, Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] of: address: Work around missing device_type property in pcie nodes
Date: Wed, 30 Sep 2020 19:37:44 +0200 [thread overview]
Message-ID: <20200930173744.GG1516931@oden.dyn.berto.se> (raw)
In-Reply-To: <977f60f07a4cb5c59f0e5f8a9dfb3993@kernel.org>
Hi Marc,
On 2020-09-30 18:23:21 +0100, Marc Zyngier wrote:
> Hi Niklas,
>
> [+ Samuel]
>
> On 2020-09-30 17:27, Niklas Söderlund wrote:
> > Hi Marc,
> >
> > I'm afraid this commit breaks booting my rk3399 device.
> >
> > I bisected the problem to this patch merged as [1]. I'm testing on a
> > Scarlet device and I'm using the unmodified upstream
> > rk3399-gru-scarlet-inx.dtb for my tests.
> >
> > The problem I'm experience is a black screen after the bootloader and
> > the device is none responsive over the network. I have no serial console
> > to this device so I'm afraid I can't tell you if there is anything
> > useful on to aid debugging there.
> >
> > If I try to test one commit earlier [2] the system boots as expected and
> > everything works as it did for me in v5.8 and earlier. I have worked
> > little with this device and have no clue about what is really on the PCI
> > buss. But running from [2] I have this info about PCI if it's helpful,
> > please ask if somethings missing.
>
> Please see the thread at [1]. The problem was reported a few weeks back
> by Samuel, and I was expecting Rob and Lorenzo to push a fix for this.
Thanks for providing a solution.
>
> Rob, Lorenzo, any update on this?
>
> M.
>
> [1]
> https://lore.kernel.org/linux-devicetree/20200829164920.7d28e01a@DUFFMAN/
> --
> Jazz is not dead. It just smells funny...
--
Regards,
Niklas Söderlund
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2020-09-30 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 9:42 [PATCH v2] of: address: Work around missing device_type property in pcie nodes Marc Zyngier
2020-08-19 22:30 ` Rob Herring
2020-09-30 16:27 ` Niklas Söderlund
2020-09-30 17:23 ` Marc Zyngier
2020-09-30 17:37 ` Niklas Söderlund [this message]
2020-09-30 20:34 ` Rob Herring
2020-09-30 22:51 ` Bjorn Helgaas
2020-09-30 23:48 ` Niklas Söderlund
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=20200930173744.GG1516931@oden.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=heiko@sntech.de \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=samuel@dionne-riel.com \
--cc=shawn.lin@rock-chips.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 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).