From: Rob Herring <robh@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: Marc Zyngier <maz@kernel.org>,
devicetree@vger.kernel.org, PCI <linux-pci@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Frank Rowand <frowand.list@gmail.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Android Kernel Team <kernel-team@android.com>,
Samuel Dionne-Riel <samuel@dionne-riel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] of: address: Work around missing device_type property in pcie nodes
Date: Wed, 30 Sep 2020 15:34:10 -0500 [thread overview]
Message-ID: <CAL_Jsq+xBKbYXWipwmZ=ZidorsMUFDw2NpUyxobx4FCTn+8Hmg@mail.gmail.com> (raw)
In-Reply-To: <20200930173744.GG1516931@oden.dyn.berto.se>
On Wed, Sep 30, 2020 at 12:37 PM Niklas Söderlund
<niklas.soderlund@ragnatech.se> wrote:
>
> 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?
The fix is in Bjorn's tree[1].
Bjorn, going to send this to Linus before v5.9 is out?
Rob
[1] https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=for-linus
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: devicetree@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Android Kernel Team <kernel-team@android.com>,
Samuel Dionne-Riel <samuel@dionne-riel.com>,
Marc Zyngier <maz@kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
PCI <linux-pci@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel <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 15:34:10 -0500 [thread overview]
Message-ID: <CAL_Jsq+xBKbYXWipwmZ=ZidorsMUFDw2NpUyxobx4FCTn+8Hmg@mail.gmail.com> (raw)
In-Reply-To: <20200930173744.GG1516931@oden.dyn.berto.se>
On Wed, Sep 30, 2020 at 12:37 PM Niklas Söderlund
<niklas.soderlund@ragnatech.se> wrote:
>
> 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?
The fix is in Bjorn's tree[1].
Bjorn, going to send this to Linus before v5.9 is out?
Rob
[1] https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=for-linus
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: devicetree@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Android Kernel Team <kernel-team@android.com>,
Samuel Dionne-Riel <samuel@dionne-riel.com>,
Marc Zyngier <maz@kernel.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
PCI <linux-pci@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel <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 15:34:10 -0500 [thread overview]
Message-ID: <CAL_Jsq+xBKbYXWipwmZ=ZidorsMUFDw2NpUyxobx4FCTn+8Hmg@mail.gmail.com> (raw)
In-Reply-To: <20200930173744.GG1516931@oden.dyn.berto.se>
On Wed, Sep 30, 2020 at 12:37 PM Niklas Söderlund
<niklas.soderlund@ragnatech.se> wrote:
>
> 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?
The fix is in Bjorn's tree[1].
Bjorn, going to send this to Linus before v5.9 is out?
Rob
[1] https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=for-linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-30 20:34 UTC|newest]
Thread overview: 24+ 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 9:42 ` Marc Zyngier
2020-08-19 9:42 ` Marc Zyngier
2020-08-19 22:30 ` Rob Herring
2020-08-19 22:30 ` Rob Herring
2020-08-19 22:30 ` Rob Herring
2020-09-30 16:27 ` Niklas Söderlund
2020-09-30 16:27 ` Niklas Söderlund
2020-09-30 16:27 ` Niklas Söderlund
2020-09-30 17:23 ` Marc Zyngier
2020-09-30 17:23 ` Marc Zyngier
2020-09-30 17:23 ` Marc Zyngier
2020-09-30 17:37 ` Niklas Söderlund
2020-09-30 17:37 ` Niklas Söderlund
2020-09-30 17:37 ` Niklas Söderlund
2020-09-30 20:34 ` Rob Herring [this message]
2020-09-30 20:34 ` Rob Herring
2020-09-30 20:34 ` Rob Herring
2020-09-30 22:51 ` Bjorn Helgaas
2020-09-30 22:51 ` Bjorn Helgaas
2020-09-30 22:51 ` Bjorn Helgaas
2020-09-30 23:48 ` Niklas Söderlund
2020-09-30 23:48 ` Niklas Söderlund
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='CAL_Jsq+xBKbYXWipwmZ=ZidorsMUFDw2NpUyxobx4FCTn+8Hmg@mail.gmail.com' \
--to=robh@kernel.org \
--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=niklas.soderlund@ragnatech.se \
--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 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.