All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: frank.li@nxp.com, l.stach@pengutronix.de, lpieralisi@kernel.org,
	kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
	bhelgaas@google.com, shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] PCI: imx6: Correct the epc_features of i.MX8M EPs
Date: Tue, 15 Jul 2025 12:07:11 -0500	[thread overview]
Message-ID: <20250715170711.GA2467369@bhelgaas> (raw)
In-Reply-To: <20250708091003.2582846-1-hongxing.zhu@nxp.com>

On Tue, Jul 08, 2025 at 05:10:01PM +0800, Richard Zhu wrote:
> IMX8MQ_EP has three 64-bit BAR0/2/4 capable and programmable BARs. For
> IMX8MQ_EP, use imx8q_pcie_epc_features (64-bit BARs 0, 2, 4) instead
> of imx8m_pcie_epc_features (64-bit BARs 0, 2).
> 
> For IMX8MM_EP and IMX8MP_EP, add fixed 256-byte BAR 4 and reserved BAR 5
> in imx8m_pcie_epc_features.
> 
> Main changes in v3:
> Seperate the patch into two commits and update the commit logs refer to
> Bjorn's suggestions.
> v2: https://lkml.org/lkml/2025/6/17/267
> 
> [PATCH v3 1/2] PCI: imx6: Correct the epc_features of IMX8MQ_EP
> [PATCH v3 2/2] PCI: imx6: Correct the epc_features of IMX8MM_EP and
> 
> drivers/pci/controller/dwc/pci-imx6.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)

Thanks, Richard, I updated pci/controller/imx6 with these patches.

      parent reply	other threads:[~2025-07-15 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  9:10 [PATCH v3 0/2] PCI: imx6: Correct the epc_features of i.MX8M EPs Richard Zhu
2025-07-08  9:10 ` [PATCH v3 1/2] PCI: imx6: Correct the epc_features of IMX8MQ_EP Richard Zhu
2025-07-08  9:10 ` [PATCH v3 2/2] PCI: imx6: Correct the epc_features of IMX8MM_EP and IMX8MP_EP Richard Zhu
2025-07-15 17:07 ` Bjorn Helgaas [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=20250715170711.GA2467369@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=festevam@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kwilczynski@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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.