All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
	"Randolph Lin" <randolph@andestech.com>,
	"Samuel Holland" <samuel.holland@sifive.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Charles Mirabile" <cmirabil@redhat.com>,
	tim609@andestech.com, "Maciej W. Rozycki" <macro@orcam.me.uk>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 4/4] PCI: dwc: Fix missing iATU setup when ECAM is enabled
Date: Tue, 27 Jan 2026 16:02:49 +0100	[thread overview]
Message-ID: <aXjTmX6R2f4bZNgN@fedora> (raw)
In-Reply-To: <7fd4fced-86c0-4fe9-843e-60a30a9b74a9@kernel.org>

On Sat, Jan 24, 2026 at 05:53:36AM +1100, Damien Le Moal wrote:
> On 2026/01/24 5:28, Niklas Cassel wrote:
> > From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> > 
> > When ECAM is enabled, the driver skipped calling dw_pcie_iatu_setup()
> > before configuring ECAM iATU entries. This left IO and MEM outbound
> > windows unprogrammed, resulting in broken IO transactions. Additionally,
> > dw_pcie_config_ecam_iatu() was only called during host initialization,
> > so ECAM-related iATU entries were not restored after suspend/resume,
> > leading to failures in configuration space access
> > 
> > To resolve these issues, the ECAM iATU configuration is moved into
> > dw_pcie_iatu_setup(), and dw_pcie_iatu_setup() is invoked when ECAM is
> > enabled.
> > 
> > Furthermore, error checks are added in dw_pcie_prog_outbound_atu() and
> > dw_pcie_prog_inbound_atu() such that an error is returned if trying to
> > program an iATU that is outside the number of iATUs provided by the
> > controller.
> > 
> > Fixes: f6fd357f7afb ("PCI: dwc: Prepare the driver for enabling ECAM mechanism using iATU 'CFG Shift Feature'")
> > Reported-by: Maciej W. Rozycki <macro@orcam.me.uk>
> > Closes: https://lore.kernel.org/all/alpine.DEB.2.21.2511280256260.36486@angie.orcam.me.uk/
> > Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> > Co-developed-by: Niklas Cassel <cassel@kernel.org>
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> 
> It looks like this patch depends on patch 3, which does not have a Fixes tag. So
> why not squash together patches 3 and 4 ?

I think it would be wrong to squash the patches.

This patch is mostly written by Krishna, and I think it is wrong to squash
a cleanup patch with a fix patch.

It is okay to have a fix patch that is done on top of a cleanup patch.
(It would require a lot more effort to write a fix without the cleanup
having been done first.)

Therefore, I will simply add:
Cc: stable+noautosel@kernel.org # depends on Clean up iATU index usage in dw_pcie_iatu_setup()

Such that stable will see that this patch requires a small dependency.


Kind regards,
Niklas

      reply	other threads:[~2026-01-27 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 18:28 [PATCH v4 0/4] PCI: dwc: Clean up iATU index mess Niklas Cassel
2026-01-23 18:28 ` [PATCH v4 1/4] PCI: dwc: Fix msg_atu_index assignment Niklas Cassel
2026-01-23 18:46   ` Damien Le Moal
2026-01-23 18:28 ` [PATCH v4 2/4] PCI: dwc: Improve msg_atu_index error handling Niklas Cassel
2026-01-23 18:50   ` Damien Le Moal
2026-01-27 15:03     ` Niklas Cassel
2026-01-23 18:28 ` [PATCH v4 3/4] PCI: dwc: Clean up iATU index usage in dw_pcie_iatu_setup() Niklas Cassel
2026-01-23 18:28 ` [PATCH v4 4/4] PCI: dwc: Fix missing iATU setup when ECAM is enabled Niklas Cassel
2026-01-23 18:53   ` Damien Le Moal
2026-01-27 15:02     ` Niklas Cassel [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=aXjTmX6R2f4bZNgN@fedora \
    --to=cassel@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=cmirabil@redhat.com \
    --cc=dlemoal@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mani@kernel.org \
    --cc=randolph@andestech.com \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tim609@andestech.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.