public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Zhi Li <lznuaa@gmail.com>
Cc: Frank Li <Frank.Li@nxp.com>,
	linux-pci@vger.kernel.org, kishon@ti.com,
	lorenzo.pieralisi@arm.com, kw@linux.com, jingoohan1@gmail.com,
	gustavo.pimentel@synopsys.com, hongxing.zhu@nxp.com,
	Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
	Allen Hubbe <allenbh@gmail.com>,
	linux-ntb@googlegroups.com
Subject: Re: [RFC PATCH 2/4] NTB: epf: Added more flexible memory map method
Date: Thu, 17 Feb 2022 16:43:38 -0600	[thread overview]
Message-ID: <20220217224338.GA311331@bhelgaas> (raw)
In-Reply-To: <CAHrpEqSWZaLan18+s_h2fLeKxqOv3yM2Zo7hr_P03bBBKvMYVA@mail.gmail.com>

On Thu, Feb 17, 2022 at 04:24:56PM -0600, Zhi Li wrote:
> On Thu, Feb 17, 2022 at 3:59 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > [+cc Jon, Dave, Allen, linux-ntb, since you need at least an ack from
> > the NTB folks; beginning of thread:
> > https://lore.kernel.org/r/20220215053844.7119-1-Frank.Li@nxp.com]
> >
> > In subject, s/Added/Add/.
> >
> > But I don't think it's quite right yet, because this doesn't actually add
> > any functions.
> 
> How about "Allow more flexibility in the memory bar map method"?

s/bar/BAR/

Are you saying that the BAR numbers were fixed before, and you're
adding the ability to change the BAR numbers?  It would be useful to
know what sort of flexibility you're adding.

> > On Mon, Feb 14, 2022 at 11:38:42PM -0600, Frank Li wrote:
> > > Supported below memory map method
> > >
> > > bar 0: config and spad data
> > > bar 2: door bell
> > > bar 4: memory map windows
> >
> > s/bar/BAR/
> > s/spad/?/ (I don't know what this is)
> 
> SCRATCHPAD REGION
> https://www.kernel.org/doc/html/latest/driver-api/ntb.html

Just spelling out "scrachpad" is probably enough.

And s/door bell/doorbell/ to match your usage elsewhere.

> > Please make the commit log say what this patch does.
> 
> Does it help if attach ASCII diagram in patch 3/4 or cover letter one

The diagram is nice, but doesn't need to be replicated everywhere.  A
description of what the patch does would be better.

Bjorn

  reply	other threads:[~2022-02-17 22:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  5:38 [RFC PATCH 0/4] NTB function for PCIe RC to EP connection Frank Li
2022-02-15  5:38 ` [RFC PATCH 1/4] PCI: designware-ep: Allow pcie_ep_set_bar change inbound map address Frank Li
2022-02-17 21:53   ` Bjorn Helgaas
2022-02-17 22:13     ` Zhi Li
2022-02-15  5:38 ` [RFC PATCH 2/4] NTB: epf: Added more flexible memory map method Frank Li
2022-02-17 21:59   ` Bjorn Helgaas
2022-02-17 22:24     ` Zhi Li
2022-02-17 22:43       ` Bjorn Helgaas [this message]
2022-02-15  5:38 ` [RFC PATCH 3/4] NTB: EPF: support NTB transfer between PCI RC and EP connection Frank Li
2022-02-17 22:38   ` Bjorn Helgaas
2022-02-17 22:59     ` Zhi Li
2022-02-15  5:38 ` [RFC PATCH 4/4] Documentation: PCI: Add specification for the PCI vNTB function device Frank Li

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=20220217224338.GA311331@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=allenbh@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=jdmason@kudzu.us \
    --cc=jingoohan1@gmail.com \
    --cc=kishon@ti.com \
    --cc=kw@linux.com \
    --cc=linux-ntb@googlegroups.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lznuaa@gmail.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