Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: [PATCH] PCI: Add #defines for max payload size options
Date: Mon, 24 Aug 2020 11:59:33 -0500	[thread overview]
Message-ID: <20200824165933.GA1852309@bjorn-Precision-5520> (raw)
In-Reply-To: <DM5PR12MB1276C8F286C45A96656A7A87DA560@DM5PR12MB1276.namprd12.prod.outlook.com>

On Mon, Aug 24, 2020 at 04:49:27PM +0000, Gustavo Pimentel wrote:
> On Thu, Aug 20, 2020 at 21:59:42, Bjorn Helgaas <helgaas@kernel.org> 
> wrote:
> 
> > On Thu, Aug 13, 2020 at 04:08:50PM +0200, Gustavo Pimentel wrote:
> > > Add #defines for the max payload size options. No functional change
> > > intended.
> > > 
> > > Cc: Joao Pinto <jpinto@synopsys.com>
> > > Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
> > > ---
> > >  include/uapi/linux/pci_regs.h | 6 ++++++
> > >  1 file changed, 6 insertions(+)
> > > 
> > > diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> > > index f970141..db625bd 100644
> > > --- a/include/uapi/linux/pci_regs.h
> > > +++ b/include/uapi/linux/pci_regs.h
> > > @@ -503,6 +503,12 @@
> > >  #define  PCI_EXP_DEVCTL_URRE	0x0008	/* Unsupported Request Reporting En. */
> > >  #define  PCI_EXP_DEVCTL_RELAX_EN 0x0010 /* Enable relaxed ordering */
> > >  #define  PCI_EXP_DEVCTL_PAYLOAD	0x00e0	/* Max_Payload_Size */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_128B  0x0000 /* 128 Bytes */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_256B  0x0020 /* 256 Bytes */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_512B  0x0040 /* 512 Bytes */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_1024B 0x0060 /* 1024 Bytes */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_2048B 0x0080 /* 2048 Bytes */
> > > +#define  PCI_EXP_DEVCTL_PAYLOAD_4096B 0x00a0 /* 4096 Bytes */
> > 
> > I would apply this if we actually *used* these anywhere, but I'm not
> > sure it's worth adding them just as documentation.
> 
> Hi Bjorn,
> 
> I'll be using that with a driver that I developed. I didn't send the 
> driver yet, because I'm still waiting for a final validation from a 
> colleague that is on vacation. If you want I can include this patch with 
> the driver patch set.

Yes, please include it with the driver.  Thanks!

Bjorn

      reply	other threads:[~2020-08-24 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 14:08 [PATCH] PCI: Add #defines for max payload size options Gustavo Pimentel
2020-08-20 20:59 ` Bjorn Helgaas
2020-08-24 16:49   ` Gustavo Pimentel
2020-08-24 16:59     ` 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=20200824165933.GA1852309@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=Gustavo.Pimentel@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox