All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Bras <leobras.c@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	aik@ozlabs.ru
Cc: Leonardo Bras <leobras.c@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] of/pci: Add IORESOURCE_MEM_64 to resource flags for 64-bit memory addresses
Date: Thu, 15 Apr 2021 15:00:51 -0300	[thread overview]
Message-ID: <20210415180050.373791-1-leobras.c@gmail.com> (raw)

Many other resource flag parsers already add this flag when the input
has bits 24 & 25 set, so update this one to do the same.

Some devices (like virtio-net) have more than one memory resource
(like MMIO32 and MMIO64) and without this flag it would be needed to
verify the address range to know which one is which.

Signed-off-by: Leonardo Bras <leobras.c@gmail.com>
---
 drivers/of/address.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/of/address.c b/drivers/of/address.c
index 73ddf2540f3f..dc7147843783 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -116,9 +116,12 @@ static unsigned int of_bus_pci_get_flags(const __be32 *addr)
 		flags |= IORESOURCE_IO;
 		break;
 	case 0x02: /* 32 bits */
-	case 0x03: /* 64 bits */
 		flags |= IORESOURCE_MEM;
 		break;
+
+	case 0x03: /* 64 bits */
+		flags |= IORESOURCE_MEM | IORESOURCE_MEM_64;
+		break;
 	}
 	if (w & 0x40000000)
 		flags |= IORESOURCE_PREFETCH;
-- 
2.30.2


             reply	other threads:[~2021-04-15 18:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 18:00 Leonardo Bras [this message]
2021-04-15 18:59 ` [PATCH 1/1] of/pci: Add IORESOURCE_MEM_64 to resource flags for 64-bit memory addresses Rob Herring
2021-04-15 18:59   ` Rob Herring
2021-04-16 20:57   ` Leonardo Bras
2021-04-16 20:57     ` Leonardo Bras
2021-04-19 15:44     ` Rob Herring
2021-04-19 15:44       ` Rob Herring
2021-04-20  0:35       ` Leonardo Bras
2021-04-20  0:35         ` Leonardo Bras
2021-04-20  1:39         ` Rob Herring
2021-04-20  1:39           ` Rob Herring
2021-04-20  2:02           ` Leonardo Bras
2021-04-20  2:02             ` Leonardo Bras
2021-04-20 22:34             ` Rob Herring
2021-04-20 22:34               ` Rob Herring
2021-04-21 14:14               ` Leonardo Bras
2021-04-21 14:14                 ` Leonardo Bras
2021-04-16 21:27   ` Leonardo Bras
2021-04-16 21:27     ` Leonardo Bras
2021-06-09 18:50   ` Bjorn Helgaas
2021-06-09 18:50     ` Bjorn Helgaas
2021-04-21 12:51 ` Rob Herring

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=20210415180050.373791-1-leobras.c@gmail.com \
    --to=leobras.c@gmail.com \
    --cc=aik@ozlabs.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.