From: Johan Jonker <jbx6244@gmail.com>
To: dario.binacchi@amarulasolutions.com,
michael@amarulasolutions.com, sjg@chromium.org
Cc: philipp.tomsich@vrull.eu, kever.yang@rock-chips.com,
u-boot@lists.denx.de, yifeng.zhao@rock-chips.com
Subject: [PATCH v2 06/10] rockchip: mtd: raw: rockchip_nfc convert dev_read_addr output to phys_addr_t
Date: Tue, 7 Feb 2023 15:54:00 +0100 [thread overview]
Message-ID: <324ed752-4aed-6f95-7395-04850c507f02@gmail.com> (raw)
In-Reply-To: <241e9e7b-58d6-dfa5-fcb5-5660e6402021@gmail.com>
The fdt_addr_t and phys_addr_t size have been decoupled.
A 32bit CPU can expext 64-bit data from the device tree parser,
so convert dev_read_addr output to phys_addr_t in the
rockchip_nfc.c file.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
drivers/mtd/nand/raw/rockchip_nfc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/raw/rockchip_nfc.c b/drivers/mtd/nand/raw/rockchip_nfc.c
index d016d255..78e2a691 100644
--- a/drivers/mtd/nand/raw/rockchip_nfc.c
+++ b/drivers/mtd/nand/raw/rockchip_nfc.c
@@ -1180,7 +1180,7 @@ static int rk_nfc_probe(struct udevice *dev)
nfc->cfg = (void *)dev_get_driver_data(dev);
nfc->dev = dev;
- nfc->regs = (void *)dev_read_addr(dev);
+ nfc->regs = (void *)((phys_addr_t)dev_read_addr(dev));
if (IS_ERR(nfc->regs)) {
ret = PTR_ERR(nfc->regs);
goto release_nfc;
--
2.20.1
next prev parent reply other threads:[~2023-02-07 14:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:49 [PATCH v2 00/10] Fixes for Rockchip NFC driver part 1 Johan Jonker
2023-02-07 14:51 ` [PATCH v2 01/10] include: fdtdec: decouple fdt_addr_t and phys_addr_t size Johan Jonker
2023-02-16 7:41 ` Kever Yang
2023-02-07 14:52 ` [PATCH v2 02/10] include: dm: ofnode: fix headers Johan Jonker
2023-02-16 7:41 ` Kever Yang
2023-02-07 14:52 ` [PATCH v2 03/10] core: remap: convert regmap_init_mem_plat() input to phys_addr_t Johan Jonker
2023-02-16 7:41 ` Kever Yang
2023-02-07 14:53 ` [PATCH v2 04/10] rockchip: adc: rockchip-saradc: convert dev_read_addr output " Johan Jonker
2023-02-16 7:42 ` Kever Yang
2023-02-07 14:53 ` [PATCH v2 05/10] rockchip: timer: dw-apb-timer: " Johan Jonker
2023-02-16 7:42 ` Kever Yang
2023-02-07 14:54 ` Johan Jonker [this message]
2023-02-16 7:34 ` [PATCH v2 06/10] rockchip: mtd: raw: rockchip_nfc " Michael Nazzareno Trimarchi
2023-02-16 7:43 ` Kever Yang
2023-02-07 14:54 ` [PATCH v2 07/10] mtd: nand: raw: rockchip_nfc: remove the compatible string "rockchip,rk3308-nfc" Johan Jonker
2023-02-16 7:29 ` Michael Nazzareno Trimarchi
2023-02-16 7:42 ` Kever Yang
2023-02-07 14:54 ` [PATCH v2 08/10] mtd: nand: raw: rockchip_nfc: add layout structure Johan Jonker
2023-02-16 7:26 ` Michael Nazzareno Trimarchi
2023-02-16 7:43 ` Kever Yang
2023-02-07 14:55 ` [PATCH v2 09/10] mtd: nand: raw: rockchip_nfc: add flash_node to chip stucture Johan Jonker
2023-02-16 7:24 ` Michael Nazzareno Trimarchi
2023-02-16 7:43 ` Kever Yang
2023-02-07 14:56 ` [PATCH v2 10/10] mtd: nand: add support for the Sandisk SDTNQGAMA chip Johan Jonker
2023-02-16 7:43 ` Kever Yang
2023-02-13 14:18 ` [PATCH v1] mtd: nand: raw: rockchip_nfc: fix oobfree offset and description Johan Jonker
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=324ed752-4aed-6f95-7395-04850c507f02@gmail.com \
--to=jbx6244@gmail.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=michael@amarulasolutions.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=yifeng.zhao@rock-chips.com \
/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