From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: ryder.lee@mediatek.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
linux-mediatek@lists.infradead.org, jianjun.wang@mediatek.com,
linux-kernel@vger.kernel.org, robh@kernel.org,
kernel@collabora.com, p.zabel@pengutronix.de,
matthias.bgg@gmail.com, bhelgaas@google.com,
nfraprado@collabora.com, kw@linux.com
Subject: Re: [PATCH] PCI: mediatek-gen3: Assert resets to ensure expected init state
Date: Wed, 11 May 2022 15:26:27 +0100 [thread overview]
Message-ID: <165227916327.28061.3388397168727783283.b4-ty@arm.com> (raw)
In-Reply-To: <20220404144858.92390-1-angelogioacchino.delregno@collabora.com>
On Mon, 4 Apr 2022 16:48:58 +0200, AngeloGioacchino Del Regno wrote:
> The controller may have been left out of reset by the bootloader,
> in which case, before the powerup sequence, the controller will be
> found preconfigured with values that were set before booting the
> kernel: this produces a controller failure, with the result of
> a failure during the mtk_pcie_startup_port() sequence as the PCIe
> link never gets up.
>
> [...]
Applied to pci/mediatek, thanks!
[1/1] PCI: mediatek-gen3: Assert resets to ensure expected init state
https://git.kernel.org/lpieralisi/pci/c/1d565935e3
Thanks,
Lorenzo
prev parent reply other threads:[~2022-05-11 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 14:48 [PATCH] PCI: mediatek-gen3: Assert resets to ensure expected init state AngeloGioacchino Del Regno
2022-05-09 12:18 ` AngeloGioacchino Del Regno
2022-05-09 17:16 ` Bjorn Helgaas
2022-05-10 7:59 ` AngeloGioacchino Del Regno
2022-05-11 14:26 ` Lorenzo Pieralisi [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=165227916327.28061.3388397168727783283.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bhelgaas@google.com \
--cc=jianjun.wang@mediatek.com \
--cc=kernel@collabora.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.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).