linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Rob Herring <robh@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
	linux-omap@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] PCI: dwc: fix two MSI issues
Date: Fri, 9 Oct 2020 15:10:06 +0800	[thread overview]
Message-ID: <20201009151006.38b3811b@xhacker.debian> (raw)
In-Reply-To: <20201008113614.GA1226@e121166-lin.cambridge.arm.com>

On Thu, 8 Oct 2020 12:36:14 +0100 Lorenzo Pieralisi wrote:

> 
> On Wed, Sep 30, 2020 at 09:12:05AM +0800, Jisheng Zhang wrote:
> > Fix two MSI issues. One to skip PCIE_MSI_INTR0* programming if MSI is
> > disabled, another to use an address in the driver data for MSI address,
> > to fix the MSI page leakage during suspend/resume.
> >
> > Since v4:
> >   - fix pci-dra7xx.c
> >
> > Since v3:
> >   - add Acked-by tag
> >   - change patch2 commit msg to make it clear
> >   - map the MSI msg with dma_map_single_attrs() for some platforms
> >     which either has seperate addrs for dma and phy or has mem access
> >     limitation for the PCIe.
> >
> > Since v2:
> >   - add Acked-by tag
> >   - use an address in the driver data for MSI address. Thank Ard and Rob
> >     for pointing out this correct direction.
> >   - Since the MSI page has gone, the leak issue doesn't exist anymore,
> >     remove unnecessary patches.
> >   - Remove dw_pcie_free_msi rename and the last patch. They could be
> >     targeted to next. So will send out patches in a separate series.
> >
> > Since v1:
> >   - add proper error handling patches.
> >   - solve the msi page leakage by moving dw_pcie_msi_init() from each
> >     users to designware host
> >
> >
> > Jisheng Zhang (2):
> >   PCI: dwc: Skip PCIE_MSI_INTR0* programming if MSI is disabled
> >   PCI: dwc: Fix MSI page leakage in suspend/resume
> >
> >  drivers/pci/controller/dwc/pci-dra7xx.c       | 18 +++++++++-
> >  .../pci/controller/dwc/pcie-designware-host.c | 34 +++++++++----------
> >  drivers/pci/controller/dwc/pcie-designware.h  |  2 +-
> >  3 files changed, 35 insertions(+), 19 deletions(-)  
> 
> Hi,
> 
> can you rebase this series against my pci/dwc branch please ?
> 

Done in v6.

Thanks

      reply	other threads:[~2020-10-09  7:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  1:12 Jisheng Zhang
2020-09-30  1:12 ` [PATCH v5 1/2] PCI: dwc: Skip PCIE_MSI_INTR0* programming if MSI is disabled Jisheng Zhang
2020-09-30  1:15 ` [PATCH v5 2/2] PCI: dwc: Fix MSI page leakage in suspend/resume Jisheng Zhang
2020-10-07 17:41   ` Rob Herring
2020-10-08 11:36 ` [PATCH v5 0/2] PCI: dwc: fix two MSI issues Lorenzo Pieralisi
2020-10-09  7:10   ` Jisheng Zhang [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=20201009151006.38b3811b@xhacker.debian \
    --to=jisheng.zhang@synaptics.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh@kernel.org \
    --subject='Re: [PATCH v5 0/2] PCI: dwc: fix two MSI issues' \
    /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

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).