All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hank Barta <hbarta@gmail.com>
To: Cyril Brulebois <kibi@debian.org>
Cc: Jim Quinlan <jim2101024@gmail.com>,
	linux-pci@vger.kernel.org,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Phil Elwell <phil@raspberrypi.com>,
	bcm-kernel-feedback-list@broadcom.com,
	james.quinlan@broadcom.com,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" 
	<linux-rpi-kernel@lists.infradead.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device
Date: Fri, 7 Apr 2023 10:06:19 -0500	[thread overview]
Message-ID: <CABTDG88MNmMmha96j0ABU4Q3-NKcLfx58wgQ2_GpyLgtAm1bxw@mail.gmail.com> (raw)
In-Reply-To: <20230406213123.wcztrbmhdpukoby2@mraw.org>

Apologies to anyone who is seeing this for the second time. I forgot
to format as plain text on the first transmission.

Cyril Brulebois kindly provided me with Debian packages for the two
kernels he built and I tested them as well. I can confirm that the one
without the three patches still had the panic on power up and when a
PCIe device is present. Otherwise it booted without difficulty. The
kernel with three patches booted successfully on all tries both cold
and warm with a PCIe/NVME installed. I was also able to mount
partitions on the NVME driver and copy data off.

My hardware

CM4 with WiFi/BT, 8GG RAM and no eMMC.
(Official) I/O board
PCIe/NVME adapter card with Intel 670p SSD installed
32GB Samsung EVO Select SD card (boot device.)

Thanks to all who contributed to this fix.


On Thu, Apr 6, 2023 at 4:31 PM Cyril Brulebois <kibi@debian.org> wrote:
>
> Hi Jim,
>
> Jim Quinlan <jim2101024@gmail.com> (2023-04-06):
> > The current driver assumes the downstream devices can provide clkreq# for
> > ASPM.  These commits accomodate devices w/ or w/o clkreq# and also handle
> > L1SS-capable devices.
> >
> > The Raspian Linux folks have already been using a PCIe RC property
> > "brcm,enable-l1ss".  These commits use the same property, in a
> > backward-compatible manner, and the implementaion adds more detail and also
> > automatically identifies devices w/o a clkreq# signal, i.e. most devices
> > plugged into an RPi CM4 IO board.
> >
> > Jim Quinlan (3):
> >   dt-bindings: PCI: brcmstb: Add two optional props
> >   PCI: brcmstb: Clkreq# accomodations of downstream device
> >   PCI: brcmstb: Allow setting the completion timeout
> >
> >  .../bindings/pci/brcm,stb-pcie.yaml           | 12 +++
> >  drivers/pci/controller/pcie-brcmstb.c         | 93 +++++++++++++++++--
> >  2 files changed, 95 insertions(+), 10 deletions(-)
> >
> >
> > base-commit: 99ddf2254febae9eab7fb0bcc02c5322243f5c49
>
> I've just verified with the exact same hardware as in Bugzilla#217276
> that latest master (v6.3-rc5-137-gf2afccfefe7b) still gets a kernel
> panic at boot, which goes away once those 3 patches are applied. Do you
> need any extra information, log excerpt, or something like that?
>
>
> Cheers,
> --
> Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant



-- 
Beautiful Sunny Winfield

WARNING: multiple messages have this Message-ID (diff)
From: Hank Barta <hbarta@gmail.com>
To: Cyril Brulebois <kibi@debian.org>
Cc: Jim Quinlan <jim2101024@gmail.com>,
	linux-pci@vger.kernel.org,
	 Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	 Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Phil Elwell <phil@raspberrypi.com>,
	 bcm-kernel-feedback-list@broadcom.com,
	james.quinlan@broadcom.com,
	 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	 "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	 open list <linux-kernel@vger.kernel.org>,
	 "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-rpi-kernel@lists.infradead.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device
Date: Fri, 7 Apr 2023 10:06:19 -0500	[thread overview]
Message-ID: <CABTDG88MNmMmha96j0ABU4Q3-NKcLfx58wgQ2_GpyLgtAm1bxw@mail.gmail.com> (raw)
In-Reply-To: <20230406213123.wcztrbmhdpukoby2@mraw.org>

Apologies to anyone who is seeing this for the second time. I forgot
to format as plain text on the first transmission.

Cyril Brulebois kindly provided me with Debian packages for the two
kernels he built and I tested them as well. I can confirm that the one
without the three patches still had the panic on power up and when a
PCIe device is present. Otherwise it booted without difficulty. The
kernel with three patches booted successfully on all tries both cold
and warm with a PCIe/NVME installed. I was also able to mount
partitions on the NVME driver and copy data off.

My hardware

CM4 with WiFi/BT, 8GG RAM and no eMMC.
(Official) I/O board
PCIe/NVME adapter card with Intel 670p SSD installed
32GB Samsung EVO Select SD card (boot device.)

Thanks to all who contributed to this fix.


On Thu, Apr 6, 2023 at 4:31 PM Cyril Brulebois <kibi@debian.org> wrote:
>
> Hi Jim,
>
> Jim Quinlan <jim2101024@gmail.com> (2023-04-06):
> > The current driver assumes the downstream devices can provide clkreq# for
> > ASPM.  These commits accomodate devices w/ or w/o clkreq# and also handle
> > L1SS-capable devices.
> >
> > The Raspian Linux folks have already been using a PCIe RC property
> > "brcm,enable-l1ss".  These commits use the same property, in a
> > backward-compatible manner, and the implementaion adds more detail and also
> > automatically identifies devices w/o a clkreq# signal, i.e. most devices
> > plugged into an RPi CM4 IO board.
> >
> > Jim Quinlan (3):
> >   dt-bindings: PCI: brcmstb: Add two optional props
> >   PCI: brcmstb: Clkreq# accomodations of downstream device
> >   PCI: brcmstb: Allow setting the completion timeout
> >
> >  .../bindings/pci/brcm,stb-pcie.yaml           | 12 +++
> >  drivers/pci/controller/pcie-brcmstb.c         | 93 +++++++++++++++++--
> >  2 files changed, 95 insertions(+), 10 deletions(-)
> >
> >
> > base-commit: 99ddf2254febae9eab7fb0bcc02c5322243f5c49
>
> I've just verified with the exact same hardware as in Bugzilla#217276
> that latest master (v6.3-rc5-137-gf2afccfefe7b) still gets a kernel
> panic at boot, which goes away once those 3 patches are applied. Do you
> need any extra information, log excerpt, or something like that?
>
>
> Cheers,
> --
> Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant



-- 
Beautiful Sunny Winfield

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-04-07 15:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 12:46 [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device Jim Quinlan
2023-04-06 12:46 ` Jim Quinlan
2023-04-06 12:46 ` [PATCH v1 1/3] dt-bindings: PCI: brcmstb: Add two optional props Jim Quinlan
2023-04-06 12:46   ` Jim Quinlan
2023-04-06 15:39   ` Stefan Wahren
2023-04-06 15:39     ` Stefan Wahren
2023-04-06 16:58     ` Jim Quinlan
2023-04-06 16:58       ` Jim Quinlan
2023-04-06 18:35       ` Krzysztof Kozlowski
2023-04-06 18:35         ` Krzysztof Kozlowski
2023-04-06 18:47         ` Florian Fainelli
2023-04-06 18:47           ` Florian Fainelli
2023-04-06 18:53           ` Krzysztof Kozlowski
2023-04-06 18:53             ` Krzysztof Kozlowski
2023-04-06 18:34   ` Krzysztof Kozlowski
2023-04-06 18:34     ` Krzysztof Kozlowski
2023-04-06 18:53     ` Florian Fainelli
2023-04-06 18:53       ` Florian Fainelli
2023-04-06 18:54       ` Krzysztof Kozlowski
2023-04-06 18:54         ` Krzysztof Kozlowski
2023-04-06 12:46 ` [PATCH v1 2/3] PCI: brcmstb: Clkreq# accomodations of downstream device Jim Quinlan
2023-04-06 12:46   ` Jim Quinlan
2023-04-06 19:09   ` Bjorn Helgaas
2023-04-06 19:09     ` Bjorn Helgaas
2023-04-06 20:03     ` Jim Quinlan
2023-04-06 20:03       ` Jim Quinlan
2023-04-06 12:46 ` [PATCH v1 3/3] PCI: brcmstb: Allow setting the completion timeout Jim Quinlan
2023-04-06 12:46   ` Jim Quinlan
2023-04-06 15:59   ` Stefan Wahren
2023-04-06 15:59     ` Stefan Wahren
2023-04-06 17:15     ` Jim Quinlan
2023-04-06 17:15       ` Jim Quinlan
2023-04-06 21:31 ` [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device Cyril Brulebois
2023-04-06 21:31   ` Cyril Brulebois
2023-04-07 15:06   ` Hank Barta [this message]
2023-04-07 15:06     ` Hank Barta

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=CABTDG88MNmMmha96j0ABU4Q3-NKcLfx58wgQ2_GpyLgtAm1bxw@mail.gmail.com \
    --to=hbarta@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=james.quinlan@broadcom.com \
    --cc=jim2101024@gmail.com \
    --cc=kibi@debian.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nsaenz@kernel.org \
    --cc=phil@raspberrypi.com \
    --cc=robh@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 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.