Hi Johan On Tue, Feb 7, 2023 at 3:54 PM Johan Jonker <jbx6...@gmail.com> wrote: > > 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 <jbx6...@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));
Is phy_read_addr_ptr() family supposed to be used in this case? Michael > if (IS_ERR(nfc->regs)) { > ret = PTR_ERR(nfc->regs); > goto release_nfc; > -- > 2.20.1 > -- Michael Nazzareno Trimarchi Co-Founder & Chief Executive Officer M. +39 347 913 2170 mich...@amarulasolutions.com __________________________________ Amarula Solutions BV Joop Geesinkweg 125, 1114 AB, Amsterdam, NL T. +31 (0)85 111 9172 i...@amarulasolutions.com www.amarulasolutions.com