Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 5 Jul 2022 23:28:01 +0200
From:   Cyril Brulebois <kibi@debian.org>
To:     Florian Fainelli <f.fainelli@gmail.com>
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>,
        bcm-kernel-feedback-list@broadcom.com, james.quinlan@broadcom.com,
        Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= <kw@linux.com>,
        "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/4] PCI: brcmstb: Re-submit reverted patchset
Message-ID: <20220705212801.u2mq6iyq2dtwzc36@mraw.org>
Organization: Debian
References: <20220701162726.31346-1-jim2101024@gmail.com>
 <1a50e8b0-1453-4561-bc3d-c428bb65288a@gmail.com>
 <20220705205551.phbaqqpgyg3pvtv7@mraw.org>
 <68af8b36-76b7-23d2-c689-d05fd62086b1@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="vzxz45xthrsgbxzp"
Content-Disposition: inline
In-Reply-To: <68af8b36-76b7-23d2-c689-d05fd62086b1@gmail.com>
Precedence: bulk


--vzxz45xthrsgbxzp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Florian Fainelli <f.fainelli@gmail.com> (2022-07-05):
> On 7/5/22 13:55, Cyril Brulebois wrote:
> > That happens with current master (v5.19-rc5-56-ge35e5b6f695d2), with
> > or without this patchset.
> >=20
> > That being said, I'm not able to reproduce the showstopper
> > regression that I reported against the initial patchset (booting was
> > breaking in the very first few seconds), so I suppose it's fine to
> > propose the following even if that's somewhat tainted by those mmc
> > issues.
>=20
> Any chance you can bisect the eMMC issues so we can investigate those
> separately? Thanks!

Definitely. I wanted to make sure I wouldn't delay the reintroduction of
this patchset (feeling partly responsible for the revert that happened
in the first place), by providing some feedback regarding a possible
come-back of the regression, as soon as possible.

Now that this is out of the way, I'll try and find time to investigate
those MMC issues. Ditto for DRM, I seem to have completely lost the HDMI
output (that's less of an issue thanks to the serial console that has
been rather reliable to gather kernel logs).

I think I started encountering both issues very early in the devel
cycle (when we were still trying to find some follow-up commits to fix
the regression instead of going for the full-on revert), but I couldn't
afford spending time chasing multiple issues at once. I haven't checked
whether reports exist already for those issues, but that's my next step.


Cheers,
--=20
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

--vzxz45xthrsgbxzp
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmLErN4ACgkQ/5FK8MKz
VSBN8w/+NpLkYZp8RmX6Fs3IM6/B5mUAYmNraZx9jYXAdkm/VBCARJxxDjs3LUWm
/5bPX98tETF0c8its+c5KyUgKG4wnNsgiL8VbvNDPZ3Kj/nKDqAqG+L8DoeL7RNp
x+9lqppkz9ZSsHOBf6DKHRL2W0btCNYqJknSkOh7yxulIG/HQNYq3NmFvKu6/vdO
/EXA4Luy8wdRwJR9/uGwlQEc294KKSOoomIZHey8gbWX5K6rnLqYgbp6CFwwbTDb
sd4c5lFFo679g1ODdog+RTxJfmxfZBQ0TCe0KJoPm4laXrDeLvanZM8kJaHGFE6f
TZ0f1TXZ2m7fwCAmAz5WmfSlL0kgEcbtvg4iYVzoJu/+nQY7nweFfMmQMMj7ksJ2
dETLCi3pD2d/PY1EtWhFyc6vrtoJiRQezTfBe453jVdiJtJZrKMxEBlG568UByXs
3yjpcSj9g5JyPtZ78anqaxjF+aCY74rhis9L8s8Pk6pyKTyvVDfO+N3Zww7l6eUq
oKaqj6hfFgwRYg9IC5VUMJeOdar7T7yGdyWbSp4iMRCi1H7xnoAgLeQmWGSVeTNR
FWaprp2dy3Y2mDlQTg7pLQoWrNo429hI7HPi3FSdVhqYwaTu0RWappOU4GbOZ4Jo
UArW/jnJHu+aWTcMklfnGQcOOXy/DFuNM8njAo3IZEWdT67a+ro=
=nTwC
-----END PGP SIGNATURE-----

--vzxz45xthrsgbxzp--