Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sumit Saxena <sumit.saxena@broadcom.com>
To: saxenasumit87m@gmail.com
Cc: Chandrakanth Patil <chandrakanth.patil@broadcom.com>,
	stable@vger.kernel.org
Subject: RE: [PATCH] PCI: set BAR size bits correctly in Resize BAR control register
Date: Thu, 25 Jul 2019 16:50:44 +0530	[thread overview]
Message-ID: <23f7699adcf7046058f8b5a9214313d0@mail.gmail.com> (raw)
In-Reply-To: <20190725191758.23462-1-sumit.saxena@broadcom.com>

Please ignore this.. it was mistakenly sent.

-----Original Message-----
From: Sumit Saxena <sumit.saxena@broadcom.com>
Sent: Friday, July 26, 2019 12:48 AM
To: saxenasumit87m@gmail.com
Cc: chandrakanth.patil@broadcom.com; stable@vger.kernel.org; Sumit Saxena
<sumit.saxena@broadcom.com>
Subject: [PATCH] PCI: set BAR size bits correctly in Resize BAR control
register

In Resize BAR control register, bits[8:12] represents size of BAR.
As per PCIe specification, below is encoded values in register bits to
actual BAR size table:

Bits  BAR size
0     1 MB
1     2 MB
2     4 MB
3     8 MB
--

For 1 MB BAR size, BAR size bits should be set to 0 but incorrectly these
bits are set to "1f".
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR with
1 MB BAR size fails to initialize during system resume from S3 sleep.

Fix: Correctly set BAR size bits to "0" for 1MB BAR size.

CC: stable@vger.kernel.org # v4.16+
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203939
Fixes: d3252ace0bc652a1a244455556b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
---
 drivers/pci/pci.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index 8abc843..b651f32
100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -1417,12 +1417,13 @@ static void pci_restore_rebar_state(struct pci_dev
*pdev)

 	for (i = 0; i < nbars; i++, pos += 8) {
 		struct resource *res;
-		int bar_idx, size;
+		int bar_idx, size, order;

 		pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL, &ctrl);
 		bar_idx = ctrl & PCI_REBAR_CTRL_BAR_IDX;
 		res = pdev->resource + bar_idx;
-		size = order_base_2((resource_size(res) >> 20) | 1) - 1;
+		order = order_base_2((resource_size(res) >> 20) | 1);
+		size = order ? order - 1 : 0;
 		ctrl &= ~PCI_REBAR_CTRL_BAR_SIZE;
 		ctrl |= size << PCI_REBAR_CTRL_BAR_SHIFT;
 		pci_write_config_dword(pdev, pos + PCI_REBAR_CTRL, ctrl);
--
1.8.3.1

  reply	other threads:[~2019-07-25 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 19:17 [PATCH] PCI: set BAR size bits correctly in Resize BAR control register Sumit Saxena
2019-07-25 11:20 ` Sumit Saxena [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-16 18:09 Sumit Saxena
2019-07-19 17:56 ` Sumit Saxena
2019-07-21 14:47   ` Koenig, Christian
2019-07-21 15:09     ` Sumit Saxena

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=23f7699adcf7046058f8b5a9214313d0@mail.gmail.com \
    --to=sumit.saxena@broadcom.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=saxenasumit87m@gmail.com \
    --cc=stable@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