netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ariel Elior <aelior@marvell.com>, Manish Chopra <manishc@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	linux-rdma@vger.kernel.org, Ram.Amrani@caviumnetworks.com,
	Michal.Kalderon@caviumnetworks.com, dledford@redhat.com,
	linux-pci@vger.kernel.org,
	Yuval Mintz <Yuval.Mintz@caviumnetworks.com>
Subject: Re: [PATCH net-next 3/7] qed: Add support for RoCE hw init
Date: Mon, 10 Oct 2022 16:44:40 -0500	[thread overview]
Message-ID: <20221010214440.GA2940104@bhelgaas> (raw)
In-Reply-To: <20221007154830.GA2630865@bhelgaas>

[ping, updated Ariel's address]

On Fri, Oct 07, 2022 at 10:48:32AM -0500, Bjorn Helgaas wrote:
> On Sat, Oct 01, 2016 at 09:59:57PM +0300, Yuval Mintz wrote:
> > From: Ram Amrani <Ram.Amrani@caviumnetworks.com>
> > 
> > This adds the backbone required for the various HW initalizations
> > which are necessary for the qedr driver - FW notification, resource
> > initializations, etc.
> > ...
> 
> > diff --git a/drivers/net/ethernet/qlogic/qed/qed_roce.c b/drivers/net/ethernet/qlogic/qed/qed_roce.c
> > ...
> > +	/* Check atomic operations support in PCI configuration space. */
> > +	pci_read_config_dword(cdev->pdev,
> > +			      cdev->pdev->pcie_cap + PCI_EXP_DEVCTL2,
> > +			      &pci_status_control);
> > +
> > +	if (pci_status_control & PCI_EXP_DEVCTL2_LTR_EN)
> > +		SET_FIELD(dev->dev_caps, QED_RDMA_DEV_CAP_ATOMIC_OP, 1);
> 
> I don't understand this.
> 
>   1) PCI_EXP_DEVCTL2 is a 16-bit register ("word"), not a 32-bit one
>   ("dword").
> 
>   2) QED_RDMA_DEV_CAP_ATOMIC_OP is set here but is not read anywhere
>   in this patch.  Is it used by the qed device itself?
> 
>   3) PCI_EXP_DEVCTL2_LTR_EN is for Latency Tolerance Reporting and is
>   not related to atomic ops.  I don't know what
>   QED_RDMA_DEV_CAP_ATOMIC_OP means, but possibly one of these was
>   intended instead?
> 
>     - PCI_EXP_DEVCAP2_ATOMIC_COMP32 means the device supports 32-bit
>       AtomicOps as a completer.
>     - PCI_EXP_DEVCAP2_ATOMIC_COMP64 means the device supports 64-bit
>       AtomicOps as a completer.
>     - PCI_EXP_DEVCAP2_ATOMIC_COMP128 means the device supports 128-bit
>       AtomicOps as a completer.
>     - PCI_EXP_DEVCTL2_ATOMIC_REQ means the device is allowed to
>       initiate AtomicOps.
> 
> (This code is now in qed_rdma.c)

  reply	other threads:[~2022-10-10 21:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 18:59 [PATCH net-next 0/7] qed*: Add qedr infrastructure support Yuval Mintz
2016-10-01 18:59 ` [PATCH net-next 1/7] qed: Add Light L2 support Yuval Mintz
2016-10-01 18:59 ` [PATCH net-next 2/7] qede: Add qedr framework Yuval Mintz
2016-10-01 18:59 ` [PATCH net-next 3/7] qed: Add support for RoCE hw init Yuval Mintz
2022-10-07 15:48   ` Bjorn Helgaas
2022-10-10 21:44     ` Bjorn Helgaas [this message]
2022-10-18 10:10       ` Michal Kalderon
     [not found] ` <1475348401-31392-1-git-send-email-Yuval.Mintz-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-10-01 18:59   ` [PATCH net-next 4/7] qed: PD,PKEY and CQ verb support Yuval Mintz
2016-10-01 18:59 ` [PATCH net-next 5/7] qed: Add support for QP verbs Yuval Mintz
2016-10-01 19:00 ` [PATCH net-next 6/7] qed: Add support for memory registeration verbs Yuval Mintz
2016-10-01 19:00 ` [PATCH net-next 7/7] qed: Add RoCE ll2 & GSI support Yuval Mintz
2016-10-04  3:24 ` [PATCH net-next 0/7] qed*: Add qedr infrastructure support David Miller
2016-10-04 12:04   ` Doug Ledford
     [not found]     ` <ad89ec53-2355-e466-0ceb-92da51cc2a62-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-04 23:59       ` [PATCH net-next 0/7] qed*: Add qedr infrastructure support,Re: " David Miller
2016-10-05  3:09         ` Doug Ledford

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=20221010214440.GA2940104@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Michal.Kalderon@caviumnetworks.com \
    --cc=Ram.Amrani@caviumnetworks.com \
    --cc=Yuval.Mintz@caviumnetworks.com \
    --cc=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).