linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com
To: linux-pci@vger.kernel.org
Cc: Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Phil Edworthy <phil.edworthy@renesas.com>,
	Simon Horman <horms+renesas@verge.net.au>,
	Wolfram Sang <wsa@the-dreams.de>,
	linux-renesas-soc@vger.kernel.org
Subject: [PATCH V2 2/6] PCI: rcar: Replace unsigned long with u32 in register accessors
Date: Fri, 22 Mar 2019 03:38:40 +0100	[thread overview]
Message-ID: <20190322023844.18574-2-marek.vasut@gmail.com> (raw)
In-Reply-To: <20190322023844.18574-1-marek.vasut@gmail.com>

From: Marek Vasut <marek.vasut+renesas@gmail.com>

Replace unsigned long with u32 in register accessor functions,
since they access 32bit registers.

Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-renesas-soc@vger.kernel.org
To: linux-pci@vger.kernel.org
---
V2: Bundle this patch with other cleanups before resending
---
 drivers/pci/controller/pcie-rcar.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/drivers/pci/controller/pcie-rcar.c b/drivers/pci/controller/pcie-rcar.c
index 5b8736f0cd6b..1408c8aa758b 100644
--- a/drivers/pci/controller/pcie-rcar.c
+++ b/drivers/pci/controller/pcie-rcar.c
@@ -152,14 +152,12 @@ struct rcar_pcie {
 	struct			rcar_msi msi;
 };
 
-static void rcar_pci_write_reg(struct rcar_pcie *pcie, unsigned long val,
-			       unsigned long reg)
+static void rcar_pci_write_reg(struct rcar_pcie *pcie, u32 val, u32 reg)
 {
 	writel(val, pcie->base + reg);
 }
 
-static unsigned long rcar_pci_read_reg(struct rcar_pcie *pcie,
-				       unsigned long reg)
+static u32 rcar_pci_read_reg(struct rcar_pcie *pcie, u32 reg)
 {
 	return readl(pcie->base + reg);
 }
-- 
2.20.1


  reply	other threads:[~2019-03-22  2:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  2:38 [PATCH V2 1/6] PCI: rcar: Clean up remaining macros defining bits marek.vasut
2019-03-22  2:38 ` marek.vasut [this message]
2019-03-22  8:20   ` [PATCH V2 2/6] PCI: rcar: Replace unsigned long with u32 in register accessors Wolfram Sang
2019-03-22  2:38 ` [PATCH V2 3/6] PCI: rcar: Replace various variable types with unsigned ones for register values marek.vasut
2019-03-22  8:22   ` Wolfram Sang
2019-03-22  8:41   ` Wolfram Sang
2019-03-23  1:28     ` Marek Vasut
2019-03-22  2:38 ` [PATCH V2 4/6] PCI: rcar: Replace (8 * n) with (n << 3) marek.vasut
2019-03-22  8:32   ` Wolfram Sang
2019-03-22  2:38 ` [PATCH V2 5/6] PCI: rcar: Clean up debug messages marek.vasut
2019-03-22  8:32   ` Wolfram Sang
2019-03-22  2:38 ` [PATCH V2 6/6] PCI: rcar: Allow 64bit MSI addresses marek.vasut
2019-03-22  8:34   ` Wolfram Sang
2019-03-23  1:52     ` Marek Vasut
2019-03-22  8:20 ` [PATCH V2 1/6] PCI: rcar: Clean up remaining macros defining bits Wolfram Sang

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=20190322023844.18574-2-marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=phil.edworthy@renesas.com \
    --cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).