public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, "Daniel Vetter" <daniel@ffwll.ch>,
	"David Airlie" <airlied@gmail.com>,
	"Dennis Dalessandro" <dennis.dalessandro@cornelisnetworks.com>,
	dri-devel@lists.freedesktop.org, "Jason Gunthorpe" <jgg@ziepe.ca>,
	"Leon Romanovsky" <leon@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rdma@vger.kernel.org, "Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Dean Luick" <dean.luick@cornelisnetworks.com>
Subject: Re: [PATCH 3/3] RDMA/hfi1: Use RMW accessors for changing LNKCTL2
Date: Fri, 3 May 2024 13:18:35 +0300 (EEST)	[thread overview]
Message-ID: <26be3948-e687-f510-0612-abcac5d919af@linux.intel.com> (raw)
In-Reply-To: <20240215133155.9198-4-ilpo.jarvinen@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3472 bytes --]

On Thu, 15 Feb 2024, Ilpo Järvinen wrote:

> Convert open coded RMW accesses for LNKCTL2 to use
> pcie_capability_clear_and_set_word() which makes its easier to
> understand what the code tries to do.
> 
> LNKCTL2 is not really owned by any driver because it is a collection of
> control bits that PCI core might need to touch. RMW accessors already
> have support for proper locking for a selected set of registers
> (LNKCTL2 is not yet among them but likely will be in the future) to
> avoid losing concurrent updates.
> 
> Suggested-by: Lukas Wunner <lukas@wunner.de>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Reviewed-by: Dean Luick <dean.luick@cornelisnetworks.com>

I found out from Linux RDMA and InfiniBand patchwork that this patch had 
been silently closed as "Not Applicable". Is there some reason for that?

I was sending this change independently out (among 2 similar ones that 
already got applied) so I wouldn't need to keep carrying it within my PCIe 
bandwidth controller series. It seemed useful enough as cleanups to stand 
on its own legs w/o requiring it to be part of PCIe bw controller series.

Should I resend the patch or do RDMA/IB maintainers prefer it to remain 
as a part of PCIe BW controller series?

-- 
 i.

> ---
>  drivers/infiniband/hw/hfi1/pcie.c | 30 ++++++++----------------------
>  1 file changed, 8 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/infiniband/hw/hfi1/pcie.c b/drivers/infiniband/hw/hfi1/pcie.c
> index 119ec2f1382b..7133964749f8 100644
> --- a/drivers/infiniband/hw/hfi1/pcie.c
> +++ b/drivers/infiniband/hw/hfi1/pcie.c
> @@ -1207,14 +1207,11 @@ int do_pcie_gen3_transition(struct hfi1_devdata *dd)
>  		    (u32)lnkctl2);
>  	/* only write to parent if target is not as high as ours */
>  	if ((lnkctl2 & PCI_EXP_LNKCTL2_TLS) < target_vector) {
> -		lnkctl2 &= ~PCI_EXP_LNKCTL2_TLS;
> -		lnkctl2 |= target_vector;
> -		dd_dev_info(dd, "%s: ..new link control2: 0x%x\n", __func__,
> -			    (u32)lnkctl2);
> -		ret = pcie_capability_write_word(parent,
> -						 PCI_EXP_LNKCTL2, lnkctl2);
> +		ret = pcie_capability_clear_and_set_word(parent, PCI_EXP_LNKCTL2,
> +							 PCI_EXP_LNKCTL2_TLS,
> +							 target_vector);
>  		if (ret) {
> -			dd_dev_err(dd, "Unable to write to PCI config\n");
> +			dd_dev_err(dd, "Unable to change parent PCI target speed\n");
>  			return_error = 1;
>  			goto done;
>  		}
> @@ -1223,22 +1220,11 @@ int do_pcie_gen3_transition(struct hfi1_devdata *dd)
>  	}
>  
>  	dd_dev_info(dd, "%s: setting target link speed\n", __func__);
> -	ret = pcie_capability_read_word(dd->pcidev, PCI_EXP_LNKCTL2, &lnkctl2);
> +	ret = pcie_capability_clear_and_set_word(dd->pcidev, PCI_EXP_LNKCTL2,
> +						 PCI_EXP_LNKCTL2_TLS,
> +						 target_vector);
>  	if (ret) {
> -		dd_dev_err(dd, "Unable to read from PCI config\n");
> -		return_error = 1;
> -		goto done;
> -	}
> -
> -	dd_dev_info(dd, "%s: ..old link control2: 0x%x\n", __func__,
> -		    (u32)lnkctl2);
> -	lnkctl2 &= ~PCI_EXP_LNKCTL2_TLS;
> -	lnkctl2 |= target_vector;
> -	dd_dev_info(dd, "%s: ..new link control2: 0x%x\n", __func__,
> -		    (u32)lnkctl2);
> -	ret = pcie_capability_write_word(dd->pcidev, PCI_EXP_LNKCTL2, lnkctl2);
> -	if (ret) {
> -		dd_dev_err(dd, "Unable to write to PCI config\n");
> +		dd_dev_err(dd, "Unable to change device PCI target speed\n");
>  		return_error = 1;
>  		goto done;
>  	}
> 

  reply	other threads:[~2024-05-03 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 13:31 [PATCH 0/3] PCI LNKCTL2 RMW Accessor Cleanup Ilpo Järvinen
2024-02-15 13:31 ` [PATCH 1/3] drm/radeon: Use RMW accessors for changing LNKCTL2 Ilpo Järvinen
2024-02-15 17:32   ` Deucher, Alexander
2024-02-16  9:22     ` Ilpo Järvinen
2024-02-16 16:59       ` Alex Deucher
2024-02-15 13:31 ` [PATCH 2/3] drm/amdgpu: " Ilpo Järvinen
2024-02-15 13:31 ` [PATCH 3/3] RDMA/hfi1: " Ilpo Järvinen
2024-05-03 10:18   ` Ilpo Järvinen [this message]
2024-05-03 13:04     ` Jason Gunthorpe
2024-05-05 13:09       ` Leon Romanovsky

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=26be3948-e687-f510-0612-abcac5d919af@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dean.luick@cornelisnetworks.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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